Re: CIPE-Win32 routing|
"Yves Smolders" <yves.smolders,AT,pandora,DOT,be>|
Sat, 30 Mar 2002 13:15:52 +0100|
I forgot to tell you one thing: you need the cipe machines to forward IP
across network adapters. Win NT4 used to do that, for 2000 and XP it's a
registry tweak. Can't remember the right setting but try google.be you'll
find it (look for IP forwarding win 2000)
> Now to allow CIPE Gateway A to ping Machine B, I have to add a route on
> Gateway A that looks like this:
> route add 192.168.1.0 mask 255.255.255.0 192.168.20.1
That's right and use -p to make the route persistent or you lose it after
> and on the machine in network B
> route add 192.168.123.0 mask 255.255.255.0 192.168.1.20
Yes, if you were to ping from machine B to Cipe A (192.168.123.110), if you
do a traceroute you'll see that the ping goes from 192.168.1.70 to
192.168.1.20, according to the route. From there on the packet gets routed
to 192.168.20.1, the other cipe machine, where 123.110 is.
> Is that right? Finally, did you mean that I should set the gateway
> for Machine A to be the IP Address of the CIPE Gateway
> And do the corresponding thing for the Machine B in private network B???
Set either the default gateway to the cipe machine or add a specific route
to machine A to get there. imho best way to work is leave the default
gateway to the DSL router, and in the DSL router add a static route to cipe
for 192.168.1.0. That way, all traffic for internet and the other network
goes to the dsl router, and there all traffic for 1.0 goes to cipe.
Hard to grasp at first, all this routing stuff but once you get the hang of
> Thanks much!!!
> 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
> > your route add should have netmask 255.255.255.0
> > The machines on your network A should have as gateway the internal IP of
> > cipe gateway A (I presume that would be 192.168.0.x or something) if
> > have another router (e.g. internet access router is not cipe gateway)
> > should point the gateway of the net to the router and add a static route
> > the router for 192.168.1.* to the cipe IP. quite a few hops, but if
> > router sends ICMP redirects back, all your machines will learn to route
> > traffic to cipe directly.
> > Alternative is adding both routes, internet & cipe to each machine, or
> > 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
> > 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
> > 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
> > and it doesn't work because gateway on the internal machine is not set
> > 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: