I have a working wireless connection to an access point with an internet connection (where my IP is Over this wireless connection I am able to ping internet addresses (e.g. as well as other machines on the wifi network (e.g. I leave those ping processes running in the background. Now I plug in an ethernet cable, which goes to a LAN on which there is a DHCP server but no internet access. That DHCP server assigns my ethernet adapter an IP ( and I am now also able to ping addresses on that LAN (e.g. All three pings run concurrently for a few seconds to a few minutes, when suddenly the ping to does this:

64 bytes from icmp_seq=1629 ttl=55 time=8.376 ms
64 bytes from icmp_seq=1630 ttl=55 time=14.247 ms
64 bytes from icmp_seq=1631 ttl=55 time=18.024 ms
Request timeout for icmp_seq 1632
Request timeout for icmp_seq 1633
Request timeout for icmp_seq 1634
ping: sendto: No route to host
Request timeout for icmp_seq 1635
ping: sendto: No route to host

It stays that way, with me having no internet access, until I unplug the ethernet cable. While this is going on I still have access to 172.17.30.x and 10.35.1.x. When I unplug the ethernet cable the ping to starts timing out and the ping to starts working again within a couple of seconds.

What causes this? How can I fix it? Would it be helpful if I include copies of my routing table at various points in the process? How do I get that?

2 Answers 2


You can adjust the order of your network interfaces in the Network panel of System Preferences. This allows you to set the primary adaptor for your network location, which in your case should be the Wi-Fi adaptor, since that provides the actual correct default route to the Internet.

The re-ordering UI is accessible by clicking on the 'gear' icon below the list of Network Adaptors on the left side of the Network Panel, and choosing "Set Service Order...".

You'll probably want to make & use a new Network Location for this setup, because in general (where either Ethernet or Wi-Fi provide valid default routes to the Internet), the Ethernet will be the better preference.

The same re-ordering can be useful for slightly unusual network setups, or VPNs where you may actually want all traffic to go through the VPN route (ie it should be the first service in the list) or maybe you only want the local subnet traffic on the VPN (ie your standard ethernet/wi-fi connections should precede it).


The problem turned out to be the existence of two default routes, one of which was not valid. I reconfigured my LAN DHCP server to not specify a router and now my second default route is created pointing at simply "link#4" instead of at an IP on the LAN.

I am hopeful of a solution whereby the state of the LAN's routing configuration would not impair other functionality in OSX.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .