Feeder request
- Lenguaje dominante
- Java
- Estrellas
- 5.1k
- Forks
- 835
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
I have issues when I'm trying to scan a particular (private) subnet that I'm connected to; AngryIP has a tendency to utilize the primary NIC as the default. To work around this, I typically disable all but the necessary NIC, which limits external access.
**Describe the solution you'd like**
I would like to see if "netstat" could be run as part of startup of the application to identify the active network interfaces, then the appropriate interfaces be listed in a pull-down menu, possibly with a preference setting to allow for a default option. I'm not sure how the AngryIP fetcher works, but if the feeder NIC can be identified, is "ping -S " an option to provide results?
**Describe alternatives you've considered**
Haven't thought of any other ideas, this was a new concept that I picked up from reading this article to try and address my problem: https://serverfault.com/questions/273600/ping-from-specific-network-adapter-on-windows
**Additional context**
Add any other context or screenshots about the feature request here.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.