|
| SVista: eCS 2.0rc4 Host - W2Ksp4 Guest |
 |
Sun, 20 Jan 2008 14:29:13 +000 |
I know this has been discussed a thousand times before but...
OK, I'm nearly there with the networking.
W2k guest on 192.168.124.2 can ping all locations in it's own subnet
192.168.124.xxx.
It can also ping all locations on the local net: 192.168.123.xxx
including the router on 192.168.123.254.
Additionally it can also ping the IP address of the cable box but not beyond
i.e. the internet.
Here is my setup.cmd:
REM llaecs
route -fh
arp -f
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.123.1 netmask 255.255.255.0 metric 1 mtu 1500
ifconfig lan1 192.168.124.1 netmask 255.255.255.0 metric 1 mtu 1500
REM ifconfig lan2 metric 1 mtu 1500
REM ifconfig lan3 metric 1 mtu 1500
REM ifconfig lan4 metric 1 mtu 1500
REM ifconfig lan5 metric 1 mtu 1500
REM ifconfig lan6 metric 1 mtu 1500
REM ifconfig lan7 metric 1 mtu 1500
REM ifconfig sl0
route add default 192.168.123.254 -hopcount 1
route add 192.168.124.1 192.168.123.1 -hopcount 1
ipgate on
lan0 is the physical network card - an RTL8169 with TCPIP, NETBOIS over TCPIP
and Serenity Virtual Protocol
lan1 is the virtual network - the Serenity Virtual Ethernet with TCPIP and
NETBIOS over TCPIP
and here are the results of "netstat -r" immediately after reboot:
destination router netmask metric flags intrf
default 192.168.123.254 0.0.0.0 1 UGSP lan0
127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo
192.168.123 192.168.123.1 255.255.255.0 0 UC lan0
192.168.124 192.168.124.1 255.255.255.0 0 UC lan1
194.168.4.100 192.168.123.254 255.255.255.255 1 UGHW3 lan0
194.168.8.100 192.168.123.254 255.255.255.255 1 UGHW lan0
What am I missing to allow the W2K guest to see the internet?
|
| Post Reply
|
| Re: SVista: eCS 2.0rc4 Host - W2Ksp4 Guest |
 |
Sun, 20 Jan 2008 16:49:18 GMT |
On Sun, 20 Jan 2008 14:29:13 UTC, Andy Staszko
<andy.staszko@ntlworld.com> wrote:
> I know this has been discussed a thousand times before but...
>
> OK, I'm nearly there with the networking.
>
> W2k guest on 192.168.124.2 can ping all locations in it's own subnet
192.168.124.xxx.
> It can also ping all locations on the local net: 192.168.123.xxx
> including the router on 192.168.123.254.
> Additionally it can also ping the IP address of the cable box but not
beyond i.e. the internet.
>
> Here is my setup.cmd:
>
> REM llaecs
> route -fh
> arp -f
> ifconfig lo 127.0.0.1
> ifconfig lan0 192.168.123.1 netmask 255.255.255.0 metric 1 mtu 1500
> ifconfig lan1 192.168.124.1 netmask 255.255.255.0 metric 1 mtu 1500
> REM ifconfig lan2 metric 1 mtu 1500
> REM ifconfig lan3 metric 1 mtu 1500
> REM ifconfig lan4 metric 1 mtu 1500
> REM ifconfig lan5 metric 1 mtu 1500
> REM ifconfig lan6 metric 1 mtu 1500
> REM ifconfig lan7 metric 1 mtu 1500
> REM ifconfig sl0
> route add default 192.168.123.254 -hopcount 1
> route add 192.168.124.1 192.168.123.1 -hopcount 1
> ipgate on
>
>
> lan0 is the physical network card - an RTL8169 with TCPIP, NETBOIS over
TCPIP and Serenity Virtual Protocol
> lan1 is the virtual network - the Serenity Virtual Ethernet with TCPIP and
NETBIOS over TCPIP
>
> and here are the results of "netstat -r" immediately after
reboot:
>
> destination router netmask metric flags
intrf
>
> default 192.168.123.254 0.0.0.0 1 UGSP
lan0
> 127.0.0.1 127.0.0.1 255.255.255.255 0 UH
lo
> 192.168.123 192.168.123.1 255.255.255.0 0 UC
lan0
> 192.168.124 192.168.124.1 255.255.255.0 0 UC
lan1
> 194.168.4.100 192.168.123.254 255.255.255.255 1 UGHW3
lan0
> 194.168.8.100 192.168.123.254 255.255.255.255 1 UGHW
lan0
>
> What am I missing to allow the W2K guest to see the internet?
>
> Andy Staszko
And the default route on the W2K guest is? You don't need the route
commands. I have often had machines with two NICs and have only ever
needed ipgate on.
However, consider. A packet leaves the W2K guest bound for the net, It
will have a 192.168,124 address. ipgate on the host pushes it on its
merry way. Assuming it gets to your router it will traverse NAT and go
to the net. The reply will come back to the router traverse NAT and
then the router will not know what to do with it. The *router* needs
to know that the path to the 124 subnet is via the 123 one.
--
Regards
Dave Saville
|
| Post Reply
|
| Re: SVista: eCS 2.0rc4 Host - W2Ksp4 Guest |
 |
Sun, 20 Jan 2008 19:06:30 +000 |
Dave Saville wrote:
> On Sun, 20 Jan 2008 14:29:13 UTC, Andy Staszko
> <andy.staszko@ntlworld.com> wrote:
>
>> I know this has been discussed a thousand times before but...
>>
>> OK, I'm nearly there with the networking.
>>
>> W2k guest on 192.168.124.2 can ping all locations in it's own subnet
192.168.124.xxx.
>> It can also ping all locations on the local net: 192.168.123.xxx
>> including the router on 192.168.123.254.
>> Additionally it can also ping the IP address of the cable box but not
beyond i.e. the internet.
>>
>> Here is my setup.cmd:
>>
>> REM llaecs
>> route -fh
>> arp -f
>> ifconfig lo 127.0.0.1
>> ifconfig lan0 192.168.123.1 netmask 255.255.255.0 metric 1 mtu 1500
>> ifconfig lan1 192.168.124.1 netmask 255.255.255.0 metric 1 mtu 1500
>> REM ifconfig lan2 metric 1 mtu 1500
>> REM ifconfig lan3 metric 1 mtu 1500
>> REM ifconfig lan4 metric 1 mtu 1500
>> REM ifconfig lan5 metric 1 mtu 1500
>> REM ifconfig lan6 metric 1 mtu 1500
>> REM ifconfig lan7 metric 1 mtu 1500
>> REM ifconfig sl0
>> route add default 192.168.123.254 -hopcount 1
>> route add 192.168.124.1 192.168.123.1 -hopcount 1
>> ipgate on
>>
>>
>> lan0 is the physical network card - an RTL8169 with TCPIP, NETBOIS over
TCPIP and Serenity Virtual Protocol
>> lan1 is the virtual network - the Serenity Virtual Ethernet with TCPIP
and NETBIOS over TCPIP
>>
>> and here are the results of "netstat -r" immediately after
reboot:
>>
>> destination router netmask metric
flags intrf
>>
>> default 192.168.123.254 0.0.0.0 1 UGSP
lan0
>> 127.0.0.1 127.0.0.1 255.255.255.255 0 UH
lo
>> 192.168.123 192.168.123.1 255.255.255.0 0 UC
lan0
>> 192.168.124 192.168.124.1 255.255.255.0 0 UC
lan1
>> 194.168.4.100 192.168.123.254 255.255.255.255 1 UGHW3
lan0
>> 194.168.8.100 192.168.123.254 255.255.255.255 1 UGHW
lan0
>>
>> What am I missing to allow the W2K guest to see the internet?
>>
>> Andy Staszko
>
> And the default route on the W2K guest is? You don't need the route
> commands. I have often had machines with two NICs and have only ever
> needed ipgate on.
>
> However, consider. A packet leaves the W2K guest bound for the net, It
> will have a 192.168,124 address. ipgate on the host pushes it on its
> merry way. Assuming it gets to your router it will traverse NAT and go
> to the net. The reply will come back to the router traverse NAT and
> then the router will not know what to do with it. The *router* needs
> to know that the path to the 124 subnet is via the 123 one.
>
I would have thought that the second "route add" in my setup.cmd file
would have done
that: it defines a route from lan0 to lan1.
|
| Post Reply
|
| Re: SVista: eCS 2.0rc4 Host - W2Ksp4 Guest |
 |
Sun, 20 Jan 2008 20:09:12 GMT |
On Sun, 20 Jan 2008 19:06:30 UTC, Andy Staszko
<andy.staszko@ntlworld.com> wrote:
>
> I would have thought that the second "route add" in my setup.cmd
file would have done
> that: it defines a route from lan0 to lan1.
And how does the *router* know to send it to the lan0 interface in the
first place?
--
Regards
Dave Saville
|
| Post Reply
|
| Re: SVista: eCS 2.0rc4 Host - W2Ksp4 Guest |
 |
Wed, 30 Jan 2008 09:00:10 +000 |
I am still in a quandary.
I should point out that the router can only be configured to sit
on the 192.168.123.xxx subnet and has address 192.168.123.254.
It may receive packets destined for the 192.168.124.xxx subnet which is
lan1 in the host.
All I would like is someone who has got this to work to spill the beans.
Please?
Andy Staszko
Dave Saville wrote:
> On Sun, 20 Jan 2008 19:06:30 UTC, Andy Staszko
> <andy.staszko@ntlworld.com> wrote:
>
>> I would have thought that the second "route add" in my
setup.cmd file would have done
>> that: it defines a route from lan0 to lan1.
>
> And how does the *router* know to send it to the lan0 interface in the
> first place?
|
| Post Reply
|
|
|
|
|
|
|
|
|
|