| Från: |
"Dave Saville" <os2-wireless_users@2rosenthals.com> |
Meddelandehuvud
Oavkodat meddelande |
| Ämne: |
Re: [OS2Wireless]More routing issues with two NICs |
| Datum: |
Mon, 14 Aug 2006 11:38:04 +0100 (BST) |
| Till: |
"OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com> |
|
|---|
On Mon, 14 Aug 2006 02:59:39 -0700 (PDT), Rick R. wrote:
>Now for the time being I'm back in OS/2 and thus got
>another routing issue of mine to deal with.
>I'm using VPC quite heavily, both for some Windoze
>stuff, but also for Linux & Solaris systems I need to
>emulate.
>Now from time to time I have to get those virtual
>boxes into the Internet, but the VPC driver can only
>work with NICs that run in promiscuous mode and then
>WiFi driver can't handle that.
>So I'm stuck with my VPC session on the LAN port.
>
Not exactly true. If the win programs don't need a "full" service they will
work in the pseudo NAT mode - ie without virtual switch. Server type progs need
the full switch.
>Now is there a way for me to route the traffic from
>the LAN port to my WiFi port and back, so that my VPCs
>can get onto the Net?
>
Yes, provided there is a somewhere on the network that you can route through
and set routes up.
Setup the laptop so that the wired NIC has virtual switch. Set it to a private
IP address that does not conflict with your "real" LAN.
Set up wifi as normal to your "real" LAN
Start VPC and start a win session. Set the win NIC to be another address on the
wired LAN's network. With that NIC as the default route.
set "ipgate on" on the laptop.
Let's see what we have so far
Real LAN 192.168.0.* netmask 255.255.255.0
Laptop wired 192.168.200.1 255.255.255.0
Win under VPC 192.168.200.2 255.255.255.0 Default route 192.168.200.1
On the machine that is the wifi's default router you need to add a route that
says to get to the 192.168.200 net you need to go through 192.168.0.x where x
is the wifi address.
SO:
Win wants to get to 12.34.56.78
He sends to 192.168.200.1 - his default router
Because the laptop has ipgate on it gets bounced out to the other NIC and sent
on its merry way. The reply comes back to whatever is doing your routing, sees
the route to the 192.168.200 net and sends it to the laptop, Laptop sends it
out the other NIC back to win.
Note the masking on the 192.168 net might need to be 255.255.0.0.
This *does* work and I have done it many times to get my win sessions out to
the net.
>Also, I can't use both interfaces if they are on the
>same network.
No. You need a smarter TCP/IP stack that OS/2 has.
--
Regards
Dave Saville
|