Date: Wed, 31 Mar 1999 16:21:30 -0800 (PST) From: Jaye Mathisen <mrcpu@internetcds.com> To: hackers@freebsd.org Subject: Weird psychotic bizarro routing problem... Message-ID: <Pine.BSF.4.05.9903311455320.5545-100000@schizo.cdsnet.net>
next in thread | raw e-mail | index | archive | help
I'm running 3.1, supped from appx 3/9/99.
I installed the gated from ports.
I have some network gear at a remote POP, where router B is.
My gated.conf is trivial:
ospf yes {
backbone {
interface eth0 cost 99;
interface eth1 cost 99;
interface ethz0 cost 1;
interface xl0;
};
};
export proto ospfase
{
proto direct;
proto kernel;
proto static;
};
Basically I have 2 T1's muxed via an ETINC card. eth0, eth1 are the
individual T1's, ethz0 is the bundled/muxed pair.
I have the following routes added statically, and they get propogated via
OSPF just fine:
route add -net 208.26.133.224 -netmask 255.255.255.224 204.238.16.89
route add -net 208.26.133.128 -netmask 255.255.255.192 204.238.16.73
route add -net 208.26.133.0 -netmask 255.255.255.128 204.238.16.71
route add -net 208.26.132.128 -netmask 255.255.255.128 204.238.16.69
route add -net 208.26.132.0 -netmask 255.255.255.128 204.238.16.67
Everything works fine. Traceroutes to 133.1, etc work just as expected.
So now I moved in some more gear, and added another route:
route add -net 208.26.136.192 -netmask 255.255.255.192 204.238.16.87
route add -net 208.26.136.128 -netmask 255.255.255.192 204.238.16.85
route add -net 208.26.136.64 -netmask 255.255.255.192 204.238.16.83
route add -net 208.26.136.0 -netmask 255.255.255.192 204.238.16.81
The routes are propagated just fine, but traceroutes *stop* at router B.
I do not see any packets generated out xl0 towards any of these hosts.
If I logon to routerB and try the traceroute, a tcpdump on another box
doesn't see them going out either. But pings to the 204.238.16.*
addresses go out, and telnet and other TCP/IP things work.
It's weird. It's only happening at the one site, and only with a few
blocks of IP's.
I have shut off gated and restarted, and it doesn't work with just a plain
static route.
But it gets weirder...
if I delete the above routes, then re-add them, but point them at an IP
that has a route to it already, (like the 132.0 net points to), then
I get the expected results of the host being unreachable...
It's like FreeBSD is just sucking in the packets, and eating them. I have
no firewall rules configured, and quite frankly, not a single thing I can
think of...
If anybody has any ideas, I'd love to here them. If anybody has any gated
experience, I'd love to chat briefly about maybe you doing some
consulting...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9903311455320.5545-100000>