mandiant/flare-fakenet-ng

Diverter failed calling GetBestInterface - error output not informative enough

Open

#138 opened on 2020年2月26日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)Python (1,626 stars) (359 forks)batch import
enhancementgood first issue

説明

This error message is very technically specific and not very helpful. It would be helpful to those who use FakeNet-NG to confirm one or more reasons why this error message can arise, and indicate that information in the error message along with suggested troubleshooting steps.

Upon starting up, FakeNet-NG may display this error:

02/26/20 11:49:52 AM [          Diverter] Failed calling GetBestInterface

This may mean that a network interface with a valid IP address could not be identified. Ensuring that the guest is at least attached to a host-only network and has valid settings from DHCP may resolve the error.

コントリビューターガイド

技術スタック
python
領域
backendsecurity
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
under 1 hour
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Pythonbasic understanding of networking
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
Locate the Diverter class in the source code, likely in a file named diverter.py. Find the method that calls GetBestInterface and produces the error message. Modify the error handling to catch specific exceptions and include reasons for failure, such as missing network interface or DHCP issues. Update the error message to suggest checking network configuration and ensure the change follows the existing logging style.