<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: CIPE-Win32 routing
From: Scott Herscher <scott,AT,swampwolf,DOT,com>
Date: Sat, 30 Mar 2002 00:32:14 +0100
In-reply-to: <000a01c1d774$395d5280$0300a8c0@falcon>

 Okay, just to make sure  I got everything straight...

Private Network A
---------------
Cable/DSL Router  Internal IP: 192.168.123.254
                            External IP: 63.299.240.33

CIPE Gateway A:    IP Address: 192.168.123.110
                        PTP Addr:  192.168.20.1

Machine A:  IP Address:  192.168.123.20

Private Network B
---------------
Cable/DSL Router  Internal IP: 192.168.1.254
                            External IP: 24.250.63.66

CIPE Gateway B:    IP Address: 192.168.1.20
                        PTP Addr:  192.168.20.2

Machine B:  IP Address:  192.168.1.70

I can ping from CIPE Gateway on Private Network A to CIPE Gateway  on
Private Network B.

Now to allow CIPE Gateway A to ping Machine B, I have to add a route on CIPE
Gateway A that looks like this:

route add 192.168.1.0 mask 255.255.255.0 192.168.20.1

and on the machine in network B

route add 192.168.123.0 mask 255.255.255.0 192.168.1.20

Is that right?  Finally, did you mean that I should set the gateway address
for Machine A to be the IP Address of the CIPE Gateway (192.168.123.110)???
And do the corresponding thing for the Machine B in private network B???

Thanks much!!!

Scotto

On 3/29/02 2:51 PM, "Yves Smolders" <yves.smolders,AT,pandora,DOT,be> wrote:

>> 192.168.20.1 is CIPE Gateway A PTP addr
>> 192.168.1.* is private network B's address range.
> 
> I presume you have Cipe gateway B PTP in the same range?  if B range is 1.*
> your route add should have netmask 255.255.255.0
> 
> The machines on your network A should have as gateway the internal IP of the
> cipe gateway A (I presume that would be 192.168.0.x or something)  if you
> have another router (e.g. internet access router is not cipe gateway) you
> should point the gateway of the net to the router and add a static route to
> the router for 192.168.1.* to the cipe IP.  quite a few hops, but if your
> router sends ICMP redirects back, all your machines will learn to route 1.*
> traffic to cipe directly.
> 
> Alternative is adding both routes, internet & cipe to each machine, or use
> RIP
> 
> Also what is almost always forgotten in routing is the route back!  Make
> routes at gateway B back to the other net - if you don't your pings don't
> get back.
> 
> And of course first of all try pinging 192.168.20.1 to gateway b
> 192.168.20.x - if that doesn't work, nothing will :-)
> 
>> I thought that this should route any traffic on CIPE Gateway A targeted
> for
>> private network B through the CIPE tunnel.  But it just screws things up.
> 
> Probably the route back.  My customers forget it all the time with port
> forwarding on their adsl routers:  they open a port up to an internal server
> and it doesn't work because gateway on the internal machine is not set to
> the router's address.
> 
>> This is possible right?  I'm not insane, right?
> 
> Nope :-)
> 
>> Please help,
>> 
>> Scotto
>> 
>> 
>> --
>> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
>> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
>> Other commands available with "help" in body to the same address.
>> CIPE info and list archive:
> <URL:http://sites.inka.de/~bigred/devel/cipe.html>
>> 
>> 
> 
> 
> --
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: 
><URL:http://sites.inka.de/~bigred/devel/cipe.html>
> 





<< | Thread Index | >> ]    [ << | Date Index | >> ]