I'm able to use VMWare WS v. 6.x with no problems on kernel 2.6.20, but not with the current 2.6.22 kernel. I've applied the any-any patch build 112, which permitted me to compile all modules. VMWare loads and will boot my guest OS (Win2K Pro). All is fine with the guest -- but no Internet connection. If I revert to an older kernel and recompile modules, everything is hunky-dorey again.
Here's the pertinent info:
(1) Output from ifconfg -a on host:
eth0 Link encap:Ethernet HWaddr 00:15:58:2F:B2:AA
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
eth1 Link encap:Ethernet HWaddr 00:16:6F:BA:6E:5A
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:6fff:feba:6e5a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39303 errors:0 dropped:2 overruns:0 frame:0
TX packets:38288 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33077558 (31.5 Mb) TX bytes:8409858 (8.0 Mb)
Interrupt:22 Base address:0xe000 Memory:b4001000-b4001fff
irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
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:1711 errors:0 dropped:0 overruns:0 frame:0
TX packets:1711 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2344355 (2.2 Mb) TX bytes:2344355 (2.2 Mb)
(2) Using bridged networking.
(3) Output from psauwww | grep -i bridge:
username 16693 0.0 0.0 3176 768 pts/4 R+ 01:41 0:00 grep -i bridge
(4) .vmx file for virtual machine:
#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
memsize = "1024"
MemAllowAutoScaleDown = "FALSE"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Windows 2000 Professional.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-raw"
floppy0.startConnected = "FALSE"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "TRUE"
pciBridge0.present = "TRUE"
isolation.tools.hgfs.disable = "FALSE"
displayName = "Windows 2000 Professional"
guestOS = "win2000pro"
nvram = "Windows 2000 Professional.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
RemoteDisplay.vnc.port = "0"
tools.upgrade.policy = "useGlobal"
floppy0.fileName = "/dev/fd0"
ide1:0.startConnected = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d 8a 9a c8 f4 fd e6-37 23 07 ea 06 d6 b5 ee"
uuid.bios = "56 4d 8a 9a c8 f4 fd e6-37 23 07 ea 06 d6 b5 ee"
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:d6:b5:ee"
ethernet0.generatedAddressOffset = "0"
ide1:0.fileName = "auto detect"
tools.syncTime = "FALSE"
extendedConfigFile = "Windows 2000 Professional.vmxf"
sharedFolder.option = "alwaysEnabled"
sharedFolder.maxNum = "2"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "/home/claw/Docs"
sharedFolder0.guestName = "Home-Claw-Docs on Arch Linux"
sharedFolder0.expiration = "never"
ethernet0.connectionType = "bridged"
#ethernet0.vnet = "/dev/vmnet0"
ethernet0.startConnected = "TRUE"
sharedFolder1.present = "TRUE"
sharedFolder1.enabled = "TRUE"
sharedFolder1.readAccess = "TRUE"
sharedFolder1.writeAccess = "TRUE"
sharedFolder1.hostPath = "/home/ftp"
sharedFolder1.guestName = "Home-Ftp on Arch Linux"
sharedFolder1.expiration = "never"
(5) ipconfig /all on guest OS (Win2K Pro):
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : vmware-arch
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-D6-B5-EE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.47.239
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
Thanks for any advice. Meanwhile, it's not that big a deal to revert to an older kernel, but this is the sort of thing that I like to get to the bottom of if possible.
Thank you for this patch. Now bridged network is working with my kernel 2.6.23-rc8 with Wireless LAN.
I have updated the patch to also work when no wireless network is used. You can download it here:
http://www.hauke-m.de/fileadmin/vmware/vmware-wireless.patch
The patched vmnet.tar can be founfd here:
http://www.hauke-m.de/fileadmin/vmware/vmnet.tar (it is based on the vmnet out of the VMware Workstation 6.0.1)
Hi clawhead,
The output from " ps auwww | grep -i bridge " should have looked something like the following
root 6841 0.0 0.0 1504 160 pts/0 S 21:38 0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth1
In your case, vmnet0 is not Bridged to any interface on the host and this is why you have no networking.
Run vmware-config.pl script again and select the "Editor" option when making network changes. When prompted for the network # to change, select 0 (zero) and configure for "Bridged" using "eth1"
Thanks, KevinG, for the help with this. Unfortunately, I still don't have proper networking with a 2.6.22 kernel even after I ensure that vmnet0 is bridged to eth1.
As I said, when I use the same configuration but with a 2.6.20 kernel, all is well. Strangely, however, the output of "ps auwww | grep -i bridge" still doesn't display as you said it would, even though networking and Internet are working fine. Here's what I get from "ps auwww | grep -i bridge":
root 8024 0.0 0.0 3180 772 pts/2 R+ 11:04 0:00 grep -i bridge
I think I'll drop this for now and just wait for the community and/or the VMWare people to get things jiving again.
Regardless, I learned more about VMware's inner workings thanks to your suggestions.
Hi,
Without the /usr/bin/vmnet-bridge process running you will not be able to use Bridged networking. You may be able use NAT if that's an option for you.
It's possible that you had compile errors with vmnet module and this is why /usr/bin/vmnet-bridge is not running.
Have you tried Petr's any-any-update112 patch?
Hi,
Without the /usr/bin/vmnet-bridge process running you
will not be able to use Bridged networking. You may
be able use NAT if that's an option for you.
But I am able to use bridged networking with kerneal 2.6.20.
It's possible that you had compile errors with vmnet
module and this is why /usr/bin/vmnet-bridge is not
running.
Have you tried Petr's any-any-update112 patch?
Yes, that's what permitted me to compile modules against the 2.6.22 kernel. At least it appeared that the modules all compiled correctly. The compilation process appared to complete when I used the any-any-update112 patched kernel 2.6.22. But maybe I missed an error message.
I'll run the tests again later today and report back.
Thanks.
Hello,
I have the same problem here : bridged networking works perfectly with kernel <= 2.6.21, and not since 2.6.22.
Workstation build 45731 with any-any patch 112
Debian SID 32-bit, Kernel 2.6.23 rc1 git 5 (but same problem with 2.6.22)
Windows XP Home 32-bit
eth0 Link encap:Ethernet HWaddr 00:15:C5:4F:03:2B
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3028 (2.9 KiB) TX bytes:3028 (2.9 KiB)
wlan0 Link encap:Ethernet HWaddr 00:18:DE:6F:F1:FD
inet addr:192.168.1.34 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9871 errors:0 dropped:0 overruns:0 frame:0
TX packets:8140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8316260 (7.9 MiB) TX bytes:1241949 (1.1 MiB)
wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-6F-F1-FD-00-00-00-00-00-00-00-00-00 -00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Configuration IP de Windows
Nom de l'hôte . . . . . . . . . . : twinky
Suffixe DNS principal . . . . . . :
Type de noud . . . . . . . . . . : Inconnu
Routage IP activé . . . . . . . . : Non
Proxy WINS activé . . . . . . . . : Non
Carte Ethernet Connexion au réseau local 2:
Suffixe DNS propre à la connexion :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Adresse physique . . . . . . . . .: 00-0C-29-02-72-B1
DHCP activé. . . . . . . . . . . : Non
Adresse IP. . . . . . . . . . . . : 192.168.1.125
Masque de sous-réseau . . . . . . : 255.255.255.0
Passerelle par défaut . . . . . . : 192.168.1.1
Serveurs DNS . . . . . . . . . . : 195.186.1.162
195.186.4.162
Result of ps -ef | grep bridge[/b]
root 3198 1 0 13:18 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 wlan0
#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "6"
scsi0.present = "FALSE"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
ide0:0.present = "TRUE"
ide0:0.fileName = "Windows XP Home Edition-000002-cl1.vmdk"
ide0:0.writeThrough = "TRUE"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
ethernet0.present = "TRUE"
usb.present = "TRUE"
sound.present = "TRUE"
sound.virtualDev = "es1371"
displayName = "Win XP - Ludo"
guestOS = "winxphome"
nvram = "Win XP - Ludo.nvram"
numvcpus = "1"
floppy0.present = "FALSE"
ide0:0.redo = ""
ide1:0.startConnected = "FALSE"
ethernet0.addressType = "generated"
uuid.location = "56 4d 7b 2c 46 a2 fe 07-15 df ab 9e 12 02 72 b1"
uuid.bios = "56 4d 7b 2c 46 a2 fe 07-15 df ab 9e 12 02 72 b1"
ethernet0.generatedAddress = "00:0c:29:02:72:b1"
ethernet0.generatedAddressOffset = "0"
tools.syncTime = "TRUE"
virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"
checkpoint.vmState = ""
uuid.action = "create"
checkpoint.vmState.readOnly = "FALSE"
extendedConfigFile = "Win XP - Ludo.vmxf"
isolation.tools.hgfs.disable = "FALSE"
sharedFolder.option = "alwaysEnabled"
sharedFolder.maxNum = "1"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "/media/sda4"
sharedFolder0.guestName = "D"
sharedFolder0.expiration = "never"
pciBridge0.present = "TRUE"
ehci.present = "TRUE"
pciBridge0.pciSlotNumber = "17"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
usb.autoConnect.device0 = ""
usb.autoConnect.device1 = ""
usb.generic.autoconnect = "TRUE"
ide1:0.autodetect = "TRUE"
inVMTeam = "FALSE"
ethernet0.connectionType = "bridged"
ethernet0.vnet = "/dev/vmnet0"
[/b]
I can post more informations if needed. Thanks for your help.
edit : forgot to say that I have messages like :
Jul 30 13:18:17 twinky vmnet-detect\[3203]: Unable to initialize the daemon
in /var/log/syslog, don't know if it is "normal"...
Also tried with any-any patch 113, same results (compiles fine, but no network on XP guest...)
Really no idea ??? As clawhead, when I boot on a 2.6.21 kernel and reconfigure vmware (without changing network parameters), it works perfectly...
Also tried with any-any patch 113, same results
(compiles fine, but no network on XP guest...)
Really no idea ??? As clawhead, when I boot on a
2.6.21 kernel and reconfigure vmware (without
changing network parameters), it works perfectly...
Yep, I tried any-any patch 113 and still get exactly the same results as lbalogh.
Hi
I' m using VMware Player with vmware-any-any-update-113 and kernel 2.6.22.1. The Host is Ubuntu and Windows XP SP2 is running in the VM. The network is bridged to a Atheros Wifi card with madwifi driver svn r2625.
I have got the same problem with the bridged network, witch isn't working. I can ping host computer from the VM but I can't ping any other computer in the network. At first the ping to the host computer doesn't work either (the first packeges get lost) but ater some time every package gets to the host.
But pinging to or from an other client in the network to the VM wasn't working, I had a 100% package lose.
In dmesg I saw this:
\[ 33.728813] Capability LSM initialized
\[ 34.170709] ppdev: user-space parallel port driver
\[ 38.602161] /dev/vmmon\[4108]: VMCI: Driver initialized.
\[ 38.602377] /dev/vmmon\[4108]: Module vmmon: registered with major=10 minor=165
\[ 38.602511] /dev/vmmon\[4108]: Module vmmon: initialized
\[ 39.312700] /dev/vmnet: open called by PID 4155 (vmnet-bridge)
\[ 39.312706] /dev/vmnet: hub 0 does not exist, allocating memory.
\[ 39.312713] /dev/vmnet: port on hub 0 successfully opened
\[ 39.312718] bridge-ath0: enabling the bridge
\[ 39.312721] bridge-ath0: up
\[ 39.312722] bridge-ath0: already up
\[ 39.312724] bridge-ath0: attached
\[ 39.503973] /dev/vmnet: open called by PID 4171 (vmnet-dhcpd)
\[ 39.503981] /dev/vmnet: hub 1 does not exist, allocating memory.
\[ 39.503989] /dev/vmnet: port on hub 1 successfully opened
\[ 39.545852] /dev/vmnet: open called by PID 4182 (vmnet-dhcpd)
\[ 39.545861] /dev/vmnet: hub 8 does not exist, allocating memory.
\[ 39.545870] /dev/vmnet: port on hub 8 successfully opened
\[ 39.574474] /dev/vmnet: open called by PID 4187 (vmnet-natd)
\[ 39.574484] /dev/vmnet: port on hub 8 successfully opened
\[ 40.119746] ath0: no IPv6 routers present
\[ 49.382333] /dev/vmnet: open called by PID 4327 (vmnet-netifup)
\[ 49.382343] /dev/vmnet: port on hub 1 successfully opened
\[ 49.479258] /dev/vmnet: open called by PID 4338 (vmnet-netifup)
\[ 49.479351] /dev/vmnet: port on hub 8 successfully opened
\[ 60.285972] vmnet8: no IPv6 routers present
\[ 60.313897] vmnet1: no IPv6 routers present
\[ 179.153537] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
\[ 179.153545] PCI: Setting latency timer of device 0000:01:00.0 to 64
\[ 179.153917] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007
\[ 285.679408] PCI: Setting latency timer of device 0000:01:00.0 to 64
\[ 285.679854] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007
\[ 5144.265295] /dev/vmnet: open called by PID 7604 (vmware-vmx)
\[ 5144.265319] device ath0 entered promiscuous mode
\[ 5144.265325] audit(1186306837.941:2): dev=ath0 prom=256 old_prom=0 auid=4294967295
\[ 5144.265327] bridge-ath0: enabled promiscuous mode
\[ 5144.265328] /dev/vmnet: port on hub 0 successfully opened
\[ 5144.376053] /dev/vmmon\[7607]: host clock rate change request 0 -> 19
\[ 5148.506779] /dev/vmmon\[7607]: host clock rate change request 19 -> 83
\[ 5159.119272] device ath0 left promiscuous mode
\[ 5159.119280] audit(1186306852.941:3): dev=ath0 prom=0 old_prom=256 auid=4294967295
\[ 5159.119282] bridge-ath0: disabled promiscuous mode
\[ 5159.119324] /dev/vmnet: open called by PID 7607 (vmware-vmx)
\[ 5159.119339] device ath0 entered promiscuous mode
\[ 5159.119342] audit(1186306852.941:4): dev=ath0 prom=256 old_prom=0 auid=4294967295
\[ 5159.119344] bridge-ath0: enabled promiscuous mode
\[ 5159.119346] /dev/vmnet: port on hub 0 successfully opened
\[ 5363.546770] device eth0 entered promiscuous mode
\[ 5363.546779] audit(1186307057.936:5): dev=eth0 prom=256 old_prom=0 auid=4294967295
\[ 5363.606614] device eth1 entered promiscuous mode
\[ 5363.606624] audit(1186307057.936:6): dev=eth1 prom=256 old_prom=0 auid=4294967295
\[ 5363.622597] device vmnet1 entered promiscuous mode
\[ 5363.622605] audit(1186307057.936:7): dev=vmnet1 prom=256 old_prom=0 auid=4294967295
\[ 5363.638523] device vmnet8 entered promiscuous mode
\[ 5363.638531] audit(1186307057.936:8): dev=vmnet8 prom=256 old_prom=0 auid=4294967295
\[ 5363.654481] device lo entered promiscuous mode
\[ 5363.654488] audit(1186307057.936:9): dev=lo prom=256 old_prom=0 auid=4294967295
\[ 5402.988610] device eth0 left promiscuous mode
\[ 5402.988619] audit(1186307097.436:10): dev=eth0 prom=0 old_prom=256 auid=4294967295
\[ 5403.004574] device wifi0 left promiscuous mode
\[ 5403.004578] audit(1186307097.436:11): dev=wifi0 prom=0 old_prom=256 auid=4294967295
\[ 5403.036483] device eth1 left promiscuous mode
\[ 5403.036490] audit(1186307097.436:12): dev=eth1 prom=0 old_prom=256 auid=4294967295
\[ 5403.052439] device vmnet1 left promiscuous mode
\[ 5403.052445] audit(1186307097.436:13): dev=vmnet1 prom=0 old_prom=256 auid=4294967295
\[ 5403.068398] device vmnet8 left promiscuous mode
\[ 5403.068404] audit(1186307097.436:14): dev=vmnet8 prom=0 old_prom=256 auid=4294967295
\[ 5403.100316] device lo left promiscuous mode
\[ 5403.100325] audit(1186307097.436:15): dev=lo prom=0 old_prom=256 auid=4294967295
In Wireshark I saw that vmware is sending an arp request 3 times "Who has 192.168.0.1? Tell 192.168.0.113" (192.168.0.1 is the IP of my router with OpenWRT and 192.168.0.113 is the IP of the Windows in the VM) but he doesn't get an response. At the same time the ping to the host is running very well.
Is there any kernel configuration with witch vmware's bridged network isn't working?
The same problem with an rtl8187 based Wireless LAN Card with a mac80211 based driver.
wlan0 = rtl8187
ath0 = atheros (madwifi)
ifconfig -a
ath0 Protokoll:Ethernet Hardware Adresse 00:11:95:91:E4:C5
inet Adresse:192.168.0.2 Bcast:192.168.0.255 Maske:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:26788 errors:0 dropped:0 overruns:0 frame:0
TX packets:27677 errors:1 dropped:1 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:21942415 (20.9 MiB) TX bytes:4178869 (3.9 MiB)
eth0 Protokoll:Ethernet Hardware Adresse 00:17:31:68:7C:9B
inet Adresse:192.168.1.21 Bcast:192.168.1.255 Maske:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18
eth1 Protokoll:Ethernet Hardware Adresse 00:18:F3:2E:02:DA
inet Adresse:192.168.1.22 Bcast:192.168.1.255 Maske:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:158460 (154.7 KiB) TX bytes:158460 (154.7 KiB)
vmnet1 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:01
inet Adresse:172.16.104.1 Bcast:172.16.104.255 Maske:255.255.255.0
inet6 Adresse: fe80::250:56ff:fec0:1/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:08
inet Adresse:192.168.139.1 Bcast:192.168.139.255 Maske:255.255.255.0
inet6 Adresse: fe80::250:56ff:fec0:8/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wifi0 Protokoll:UNSPEC Hardware Adresse 00-11-95-91-E4-C5-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:148568 errors:112 dropped:1942 overruns:0 frame:110
TX packets:30326 errors:5778 dropped:1 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:199
RX bytes:35681373 (34.0 MiB) TX bytes:5504605 (5.2 MiB)
Interrupt:19
wlan0 Protokoll:Ethernet Hardware Adresse 00:15:AF:03:AB:79
inet Adresse:192.168.0.7 Bcast:192.168.0.255 Maske:255.255.255.0
inet6 Adresse: fe80::215:afff:fe03:ab79/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2125 errors:0 dropped:0 overruns:0 frame:0
TX packets:2599 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:1731552 (1.6 MiB) TX bytes:363285 (354.7 KiB)
wmaster0 Protokoll:UNSPEC Hardware Adresse 00-15-AF-03-AB-79-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Having also problems with:
Linux 2.6.22.1 for amd64 (SMP)
VMWare Workstation 6.0.
My problem is that, network (bridge) works fine, except betwen host and client machine. If i set an "static route" to the virtual machine via my router, it starts working, i mean:
Host IP: 192.168.0.50 (linux 2.6.22.1)
Client IP: 192.168.0.150 (another linux machine, or windows or whatever)
Host: route add 192.168.0.150 gw 192.168.0.1 (route through my firewall)
Client: route add 192.168.0.50 gw 192.168.0.1 (route through my firewall also)
If i setup this way, the net works fine.
Note: Ping always works fine
Any new ideas?
Has anybody got this problem solved, yet? I'm still holding off on a kernel upgrade until a solution appears.
Thanks.
I get same problem and a create a second network connection host only to comunicate with host until we have a fix to this issue.
davi
Does anyone know if Build 55017 takes care of this problem? I'm too lazy to install a new kernel to test it.
Thanks.
Does anyone know if Build 55017 takes care of this
problem? I'm too lazy to install a new kernel to test
it.
Thanks.
An answer to my own question: Yes, my initial installation and tests show that bridged networking is working properly with VMWare Workstation for Linux 6.01 (build 55017) running on a 2.6.22 kernel. I have a functioning Internet connection using the same VMWare bridged networking configuration that I had been using with kernel 2.6.20.
Others will want to verify.
Thanks.
I still have no internet from the guest OS with WS build 55017 on Fedora kernel 2.6.22.5-76.fc7. Note that my bridge is wireless, using madwifi 0.9.3.2. Perhaps ethernet bridges are working, but the wireless isn't.
Have you tried using the ath5k?
What exact physical wireless network adapter are you using? (make/model..etc)
Are you using WS 6.0.1?
Daguerre, you're right, at least according to my tests. Using kernel
2.6.22.6 (under Arch Linux) running WS for Linux 6.01 (build 55017) with a wired ethernet connection, I
get full networking, Internet included. When I have a wifi connection, I'm connected to
the LAN but not to the Internet.
My wifi adapter is Intel Corporation PRO/Wireless 2200BG internal. My machine is a Thinkpad T43.
Does this information lead us closer to a solution?
I also have a PCMCIA wifi adapter that I can test with to see if the problem is adapter-specific.
Note again that wifi and wireless work equally well with kernel 2.6.20 and WS for linux 6 as well as 6.01.
I'm using a Netgear WG311T. I just upgraded madwifi to the latest trunk, and no luck.
This is the first I've heard of ath5k! Sounds promising, but I could find any code. Is there an actual working development version for Linux?