Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'VPC 6.1 and OS X networking together on a PowerBook G4' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
VPC 6.1 and OS X networking together on a PowerBook G4
Authored by: inertia186 on Nov 08, '03 01:52:10PM

Well, it certainly seems to work while I'm on my Airport network connected to my Linksys router. Internet Sharing is happy to share the route over the Airport.

But what happens when there is no internet connection? Internet Sharing won't start share when there's nothing to share.

In other words, have you actually tried it on the interstate?



[ Reply to This | # ]
VPC 6.1 and OS X networking together on a PowerBook G4
Authored by: kdkinsey on Nov 08, '03 02:30:30PM

6 hours up the interstate, in fact (New Orleans to Atlanta). In Panther, internet sharing will apparently share an interface, regardless of whether or not an active connection exists. Turning the airport (interface) off will disable sharing of that interface. The fact a network is present or not seems to have no affect.

I found this curious, but advantageous. 'ifconfig' in the terminal will confirm this. To be on the safe side, I did assign the airport interface a static address even though there was no network present (192.168.1.2, gateway: 192.168.1.1) so Apache/Tomcat would have something to hold on to, although linkback(localhost) should have worked just as well.

After some additional experimentation, I have noticed that the reverse of what I describe does not work with VPC. If the Internet Sharing is setup such that the DHCP server is bound to the airport interface (share internet connection from built-in ethernet to airport), VPC will not see the DHCP server and will not get assigned an address. It works fine as described in the original post. It appears NAT works differently between the airport and built-in ethernet interfaces.

I haven't done much testing, but it also appears that after applying the latest airport update (3.2), VPC virtual switch isn't working quite right when pointed at the airport interface. Pointed at the built-in interface is okay. I haven't used the default option, so can't say much about that one.

K



[ Reply to This | # ]