On Wed, 2005-07-20 at 19:33 +0200, Anders Johansson wrote:
On Wednesday 20 July 2005 19:30, James Wright wrote:
Ok, I go my MTU reset and am back on the network. I checked to see that I was on the right domain and I am. ifconfig shows:
black-kdavzbpz3:/home/james # ifconfig eth0 Link encap:Ethernet HWaddr 00:01:6C:3B:85:07 inet addr:192.168.1.123 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::201:6cff:fe3b:8507/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:206501 errors:0 dropped:0 overruns:0 frame:0 TX packets:147063 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:36522235 (34.8 Mb) TX bytes:112697672 (107.4 Mb) Interrupt:11 Base address:0xc000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:22859 errors:0 dropped:0 overruns:0 frame:0 TX packets:22859 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:101776601 (97.0 Mb) TX bytes:101776601 (97.0 Mb)
If you're using bridging, why aren't you seeing the vmware interfaces? Please show the output of ifconfig when vmware is running.
I have always used bridged networking with vmware and never see any vmware interface when typing ifconfig. Perhaps it is the way you have your vmware setup. As I recall I used to have one but changed the network setup as I saw no reason for an interface to be configured under ifconfig. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge