| To: | cipe-l,AT,inka,DOT,de |
| Subject: | RE: Routing across CIPE adpaters. |
| From: | Doug Johnson <doug.johnson,AT,vifanusa,DOT,com> |
| Date: | Fri, 8 Aug 2003 08:30:02 -0400 |
Correction for the record and archives. The problem was not the metric. After further playing with the route statements there was an entry missing on the 1.0 net. Destination Gateway Genmask Flags Metric Ref Use Iface 10.1.0.0 10.1.0.11 255.255.255.0 UG 0 0 0 cipcb0 It was the return traffic that was not making the route back. The only difference in the original posting and and where it is now is the above statement on the CIPE machine on the 1.0 subnet, and now everything works ok. Again, thanks for all of the help and advice. It is much appreciated (expecialy when the error is my stupidity). Thanks again, Doug -----Original Message----- From: Doug Johnson [mailto:doug.johnson,AT,vifanusa,DOT,com Sent: Thursday, August 07, 2003 2:41 PM To: cipe-l,AT,inka,DOT,de Subject: RE: Routing across CIPE adpaters. Thanks for all of the help gang. I think I need to look at my metric entry in my route statements a little closer. Doug -----Original Message----- From: Doug Johnson [mailto:doug.johnson,AT,vifanusa,DOT,com Sent: Thursday, August 07, 2003 1:55 PM To: cipe-l,AT,inka,DOT,de Subject: RE: Routing across CIPE adpaters. My first thoughts were that all of the subnets should be different between the CIPE tunnels. In the snip below there is another subnet that is not part of the CIPE scheme. It looks like this: 192.168.3.0 <-Cisco-> 192.168.1.0 <-CIPE-> 192.168.4.0 <-CIPE-> 192.168.0.0 ^Cisco between these two^ So, the 10.1.0.12 interface is the only interface to hit both 3.0 and 1.0 nets. Doug -----Original Message----- From: Mark Smith [mailto:mark.smith,AT,avcosystems,DOT,co,DOT,uk Sent: Thursday, August 07, 2003 12:27 PM To: cipe-l,AT,inka,DOT,de Subject: RE: Routing across CIPE adpaters. My setup is multiple tunnels to one server, but in my case the endpoint masquerades all traffic. Even if that were not the case, I can still access the cipe address of one tunnel from another. My setup is admittedly evil, however, as I run a single subnet and make the cipe addresses part of it. This only works because of proxy arp, but it does indeed seem to work. [snip] > 192.168.3.0 10.1.0.12 255.255.255.0 UG 0 0 0 cipcb5 > 192.168.1.0 10.1.0.12 255.255.255.0 UG 0 0 0 cipcb5 I'm thinking that the gateway should be different for these two subnets... -- Mark Smith - Avco Systems Ltd email: mark.smith,AT,avcosystems,DOT,co,DOT,uk Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078 -- 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> -- 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>