Turns out that, for the time being, changing the nameserver in /etc/resolv.conf to a real world DNS solves the problem. I've yet to test out if AirportConfigurator.jar (from the ports collection) can handle the new Apple Airport 1.3 update. I hope it does or it can be updated to do so. The wireless LANs at work use Airport Base Stations, but are all Windows-based laptops with wireless PCMCIA cards. We are Macless, so I depend on that AirportConfiguator.jar utility. Thanks for the response. Tim On Sat, 24 Mar 2001, Brandon S. Allbery KF8NH wrote: > On Saturday, March 24, 2001 11:56:01 -0500, Tim Kellers > <[EMAIL PROTECTED]> wrote: > +----- > | their TCP/IP control panel (24.3.196.33, 24.3 196.34), but in > | /stand/sysinstall's network interface configuration (via dhcp) the > | nameserver address defaults to 10.0.1.1 which is the same address as the > | gateway. > +--->8 > > Some people here have complained about the new AirPort firmware doing that, > so I think you can rule out FreeBSD as the cause. > > -- > brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] > system administrator [WAY too many hats] [EMAIL PROTECTED] > electrical and computer engineering KF8NH > carnegie mellon university ["better check the oblivious first" -ke6sls] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
