Many months ago, I posted here about problems I was having getting
VPC's virtual switch networking to work.
The problem appears to have been the Broadcom B57 GbE NIC driver for
OS/2; it doesn't seem to support the necessary functionality.
My motherboard happens to have two GbE NICs built in: the Broadcom,
and an NVidia nForce4 (with Marvell controller).
I thought people might be interested to know that I finally got
around to trying out GenMAC wrapper (v2.00), using the nForce
driver. I switched the VSWITCH driver over to use that interface,
and now I have virtual switch working in VPC at long last!
In short, my NIC configuration is now:
Broadcom Ethernet
0 - TCP/IP
0 - NETBIOS
GenMac Wrapper nForce 4
0 - InnoTek Virtual Switch Protocol
InnoTek Virtual Switch Switch MAC
1 - TCP/IP
Both NETBIOS and TCP/IP work perfectly from VPC now, and I can
finally communicate with other boxes on my LAN (which is VERY
welcome, esp. when "additions" are not/can't be installed).
So, thank you Willibald and NetLabs!
--
Alex Taylor
http://www.cs-club.org/~alex
|
On Sat, 28 Apr 2007 19:01:06 UTC, "Alex Taylor"
<mail.me@reply.to.address> wrote:
> Many months ago, I posted here about problems I was having getting
> VPC's virtual switch networking to work.
>
> The problem appears to have been the Broadcom B57 GbE NIC driver for
> OS/2; it doesn't seem to support the necessary functionality.
>
> My motherboard happens to have two GbE NICs built in: the Broadcom,
> and an NVidia nForce4 (with Marvell controller).
>
> I thought people might be interested to know that I finally got
> around to trying out GenMAC wrapper (v2.00), using the nForce
> driver. I switched the VSWITCH driver over to use that interface,
> and now I have virtual switch working in VPC at long last!
>
> In short, my NIC configuration is now:
>
> Broadcom Ethernet
> 0 - TCP/IP
> 0 - NETBIOS
> GenMac Wrapper nForce 4
> 0 - InnoTek Virtual Switch Protocol
> InnoTek Virtual Switch Switch MAC
> 1 - TCP/IP
>
> Both NETBIOS and TCP/IP work perfectly from VPC now, and I can
> finally communicate with other boxes on my LAN (which is VERY
> welcome, esp. when "additions" are not/can't be installed).
>
>
> So, thank you Willibald and NetLabs!
Yes, GENMAC is progressing nicely, if at a snail's pace. It would be
better, if Willibald would release his work, to allow others to help
in the development. It seems that he doesn't have the time, or the
hardware, to do enough development to satisfy the demand. If more
people were able to work on it, more could be done, and some
"problems", that have no solutions (so far), may be solved, by new
ideas, that others may introduce.
I have:
Intel(R) PRO/100 Network connection.......
0 - SVista Virtual Protocol
GenMac Wrapper nForce4 10/100/1000 [10DE:0057]......
1 - Innotek Virtual Switch Protocol
Innotek Virtual Switch MAC......
1 - IBM TCP/IP (192.168.0.7)
Serenity Virtual Net Driver
0 - IBM OS/2 NETBIOS OVER TCP/IP
0 - IBM TCP/IP (192.168.200.107)
My normal system communications is through the Intel, via Serenity
Virtual Net Driver. My SVista systems also communicate through that
interface. The VPC systems communicate through the Virtual Switch, on
the GENMAC interface, but they don't use the 192.168.0.x series of
addresses. I plugged the GENMAC interface into my hub, which is
connected to my router (which, in turn, is connected to my ADSL
modem). The router serves up addresses for everything, except the
192.168.0.7 address. The vitual machines (both SVista, and VPC), get
addresses in the 192.168.200.1xx range, so all systems are in the same
address group.
I did it that way, because the GENMAC driver doesn't support the
SVista stuff, while the Intel driver does. I also couldn't find a way
to attach both the SVista stuff, and the VPC stuff, on the same
interface. I can use the 192.168.0.7 address, to communicate with my
ASUS Wl-330g, and my Belkin Travel router, if I want to.
Hope this helps someone...
--
From the eComStation 1.2 of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
|