[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
turns out this issue was a combination of the cisco VPN client and
10.2.4. the following fixes the issue:
sudo ifconfig en0 mtu 1500
On Friday, February 21, 2003, at 02:00 PM, Paul wrote:
You indicated that you're using the latest release of OS X, right?
This wouldn't be the first time a latest release came with a new bug.
Have you tried manually downing the interface before manually bringing
it up again?
Looking at my RH 8.0 PC... I know that bringing up an interface and
grabbing an IP are two seperate operations. There must be a script
which executes both procedures. I see a lot going on in
/etc/sysconfig/network-scripts/ifup, but I really don't want to read
through it. The point is that maybe a bug was introduced which
doesn't allow the DHCP client to run or otherwise grab an IP.
W. Chris Shank wrote:
But I also see this problem connecting to a Seimens SpeedStream
wireless
router and the windows laptops wakeup and get their IP address back
just
fine.
_______________________________________________________________________
__
Philadelphia Linux Users Group --
http://www.phillylinux.org
Announcements -
http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion --
http://lists.netisland.net/mailman/listinfo/plug
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|