mandiant/flare-fakenet-ng

Diverter failed calling GetBestInterface - error output not informative enough

Open

#138 创建于 2020年2月26日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)Python (1,626 star) (359 fork)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
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.