![](https://seccdn.libravatar.org/avatar/7dacfd4a91671317bdbde76fd5a668ec.jpg?s=120&d=mm&r=g)
3 Apr
2003
3 Apr
'03
18:28
the onboard interface is typically configured for DHCP, and it is started first. The consequence is that the DHCP client running for the WLAN device is considered "secondary" and it won't modify resolv.conf, nor set a default route.
Bingo, this is exactly the case. I had pretty much pieced this together through my trials, but I certainly appreciate the reply verifying it.
Solution: Either append DHCLIENT_PRIMARY_DEVICE=yes to each ifcfg-* file that is configured for DHCP,
Ah, that's a decent soluion. Didn't know I could do that. I assume this will have both interfaces update routing and resolv.conf? I actually took to setting eth0 to STARTMODE="manual" since I rarely use the onboard nic. Thanks a lot for the reply!