Hi, When bringing up eth0 via netifrc+dhcpcd other interfaces are also configured automatically with a persistent address that doesn't go away after stopping eth0, which does loose it's address correctly due to -x being used. Reproducible: Always Steps to Reproduce: 1. rc-service net.eth0 start 2. bring another network interface up Actual Results: the interface with no explicit config or symlink is configured Expected Results: the interface with no explicit config or symlink is not configured
That doesn't sound right. When invoked for a specific interface, dhcpcd should not alter the configuration for any other interface. Passing --allow-interfaces should be unnecessary.
I'm messing around with this system too much and shouldn't have been so hasty, sorry for wasting your time.
Morning, I found out what was happening. The problem was netmount starting dhcpcd when no interfaces are in any runlevel, I'll make a 'netifrc-dhcpcd' init script that runs with --inactive and see how that goes. Regards Jonathan
Eventually the problem seems to be down to dhcpcd providing net, without any condition for situations when it should provide dhcp instead. The combination of 'net.dhcp' that has '-qq --inactive' and changing dhcpcd's provides seems to work, but potentially I'm wasting lots of time (other than the learning) so just wanted to change the title and record thinking before moving on. Regards
