FS#42772 - [netctl] Lost routes on an unstable wlan connection
Attached to Project:
Arch Linux
Opened by Boy van Duuren (boyvanduuren) - Thursday, 13 November 2014, 11:16 GMT
Last edited by Jouke Witteveen (jouke) - Sunday, 08 October 2017, 08:00 GMT
Opened by Boy van Duuren (boyvanduuren) - Thursday, 13 November 2014, 11:16 GMT
Last edited by Jouke Witteveen (jouke) - Sunday, 08 October 2017, 08:00 GMT
|
Details
Description:
I use Routes=('') to configure a default route to work around a misconfigured DHCP server. There are also some issues with my wireless driver, which cause the carrier to get lost a couple times a day. When this happens, all my routes get deleted. When the carrier gets reacquired, the only routes that get configured are the ones specified by the DHCP options. The extra routes in my profile get ignored. Additional info: netctl 1.9-1 dhcpcd 6.6.1-1 $lspci | grep "Network controller" 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) $ uname -a Linux stratholme 3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014 x86_64 GNU/Linux Steps to reproduce: 1. Start netctl profile that configures routes 2. `sudo rfkill block wlan` 3. `sudo rfkill unblock wlan` 4. Wait for connection 5. `ip r` shows the profile routes missing |
This task depends upon
Closed by Jouke Witteveen (jouke)
Sunday, 08 October 2017, 08:00 GMT
Reason for closing: No response
Additional comments about closing: Looks like it could be a bug in netctl. Please reopen if this is still an issue.
Closing now because it is over 2.5 years old.
Sunday, 08 October 2017, 08:00 GMT
Reason for closing: No response
Additional comments about closing: Looks like it could be a bug in netctl. Please reopen if this is still an issue.
Closing now because it is over 2.5 years old.
Comment by
Boy van Duuren (boyvanduuren) -
Thursday, 13 November 2014, 11:41 GMT
Comment by Jouke Witteveen (jouke) -
Tuesday, 06 January 2015, 10:55 GMT
I think adding the routes with a dhcpcd hook in stead of doing it
from /usr/lib/network/ip should fix this issue, btw.
Could this be a bug in dhcpcd or our usage of dhcpcd? There might
be a switch to dhcpcd to prevent it from setting the routes. If
so, you could set it in DhcpcdOptions= until we find a solution.