netctl gives up if cable unplugged on boot

This forum is for topics dealing with problems with software specifically in the ARMv7h repo.

netctl gives up if cable unplugged on boot

Postby tal » Sat Sep 24, 2016 10:03 pm

I have a Raspberry Pi Arch router.
I configured 2 netctl profiles:

LAN:
$this->bbcode_second_pass_code('', '# vim /etc/netctl/lan0-profile

Description='LAN Profile'
Interface=lan0
Connection=ethernet
IP=static
Address=('192.168.1.1/24')')

WAN:
$this->bbcode_second_pass_code('', '# vim /etc/netctl/wan0-profile

Description='WAN Profile'
Interface=wan0
Connection=ethernet
IP=dhcp')

Enabled both:
$this->bbcode_second_pass_code('', '# netctl enable lan0-profile
# netctl enable wan0-profile')

This works great, as long as both the WAN and LAN cables are connected to the device on boot.
If an ethernet cable is not connected during boot, the interface never gets configured. Basically if I boot and then plug in the cables, the interfaces remain unconfigured.
For a router, that's obviously pretty bad.
Is there a way to make it keep trying?
tal
 
Posts: 2
Joined: Sat Sep 24, 2016 10:00 pm

Re: netctl gives up if cable unplugged on boot

Postby tal » Sun Sep 25, 2016 5:48 pm

I went on the #archlinux-arm irc channel, and the guys there told me:

1. Try Netctl-ifplugd
2. Use systemd-networkd instead of netctl

I never did try netctl-ifplugd - maybe that would have worked. systemd-networkd was really easy to configure, and seems to work great.

If anyone can confirm that netctl-ifplugd would have worked, or has a better solutions to make netctl work, it might help others facing a similar problem who cannot switch to systemd-networkd.
tal
 
Posts: 2
Joined: Sat Sep 24, 2016 10:00 pm


Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 13 guests