bridged networking is definitely broken in 3170
I've got a wireless router set to a non-standard IP address. I want to configure a new router via the ethernet port, while remaining online via Airport, so that I can look at the router docs online and browse forums. Rather than having to deal with changing the order of the ports in the Network preferences panel every time I need to access the net or access the new router, I decided to disable the Mac's IP address on the built-in ethernet port, set Parallels for bridged networking on en0, and then use Windows inside Parallels to configure the router.
Here's my setup. In the Network preferences panel, I've set my Airport config to connect to the old router as usual. Also, I've set the built-in Ethernet to "Off". Then, I setup Parallels to use bridged networking on en0:Ethernet Adapter. When I setup Windows' Local Area Connection's TCP/IP settings to use DHCP, it gets an IP address from my old router connected via Airport! In other words, Parallels is acting as if I bridged to en1 instead of en0.
My old router is not using the standard IP address (192.168.1.1), but the new router is set to 192.168.1.1. I can easily tell that Windows is getting it's IP address via Airport because it gets an address in my old router's subnet rather than the 192.168.1 subnet. It's definitely not bridged to the built-in ethernet port. Furthermore, if I change Windows to use a manual IP address on the 192.168.1 subnet, I can't ping the new router. So, at the very least, Parallels' bridged networking is broken in that it doesn't bridge to the interface that I specify.
Last edited: Feb 19, 2007