FS#29466 - [netcfg] net-auto-wired should arping gateway after using static profile
Attached to Project:
Arch Linux
Opened by Jimmy Xu (jimmyxu) - Sunday, 15 April 2012, 10:34 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:06 GMT
Opened by Jimmy Xu (jimmyxu) - Sunday, 15 April 2012, 10:34 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:06 GMT
|
Details
Description:
If I have multiple IP=static profiles in my network.d/, then always the first one will be used when net-auto-wired is called. Ideally netcfg should be able to arping the gateway in the profile, to make sure that profile works on the link. After the patch: Apr 15 10:30:23 vangogh ifplugd(eth0)[7078]: client: :: 00-192.0.2.233 up ARPing gateway 192.0.2.254 failed Apr 15 10:30:23 vangogh ifplugd(eth0)[7078]: client: [fail] Apr 15 10:30:27 vangogh ifplugd(eth0)[7078]: client: :: 10-198.51.100.27 up [done] Apr 15 10:30:27 vangogh ifplugd(eth0)[7078]: Program executed successfully. Additional info: * package version(s) netcfg 2.8.0-1 * config and/or log files etc. N/A Steps to reproduce: Plug the computer into a network where the first profile net-auto-wired sees is not suitable. See net-auto-wired will still use that profile. |
This task depends upon
Closed by Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:06 GMT
Reason for closing: Won't fix
Additional comments about closing: netcfg has been moved to AUR
Tuesday, 30 April 2013, 01:06 GMT
Reason for closing: Won't fix
Additional comments about closing: netcfg has been moved to AUR
1) we don't depend on iputils, so arping needn't be installed
2) couldn't this break other scenarios using ethernet for their connection?