Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19763 - [dhcpd] Losing DHCP assignment from modem when DHCPD sets MTU
Attached to Project:
Arch Linux
Opened by FuKaS (FuKaS) - Thursday, 10 June 2010, 22:31 GMT
Last edited by Allan McRae (Allan) - Saturday, 28 April 2012, 11:51 GMT
Opened by FuKaS (FuKaS) - Thursday, 10 June 2010, 22:31 GMT
Last edited by Allan McRae (Allan) - Saturday, 28 April 2012, 11:51 GMT
|
DetailsDescription:
When the network daemon is started and your device (cable modem in this scenario) assigns your interface an ip address, DHCPD re-sets the MTU causing the interface to lose it's acquired information. The current (updated) DHCPD config has one change which has seemingly started the issue, the change is that the "interface_mtu" option has been uncommented. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: To reproduce this problem, open /etc/dhcpcd.conf and uncomment "option interface_mtu" followed by restarting the network daemon (/etc/rc.d/network restart). Issuing ifconfig you will notice your interface has no IP address, also if you instruct dhcpcd to run on your interface (dhcpcd eth0) it will tell you it's already running. Killing DHCPCD and reissuing the command still results in no IP address. |
This task depends upon
Comment by Gaetan Bisson (vesath) -
Saturday, 19 February 2011, 13:36 GMT
So this is just a matter of default configuration, right? Have you tried reporting this upstream?