Date: Sun, 25 Oct 1998 13:17:24 -0700 From: Greg Skafte <skafte@worldgate.com> To: ratbert@phoenix.aye.net, Leif Neland <root@swimsuit.internet.dk> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: route changes erratically (routed) Message-ID: <19981025131724.A19988@worldgate.com> In-Reply-To: <Pine.BSF.3.96.981025135922.28835A-100000@phoenix.aye.net>; from ratbert@phoenix.aye.net on Sun, Oct 25, 1998 at 02:11:30PM -0500 References: <Pine.BSF.4.05.9810230024380.1409-100000@gina.swimsuit.internet.dk> <Pine.BSF.3.96.981025135922.28835A-100000@phoenix.aye.net>
next in thread | previous in thread | raw e-mail | index | archive | help
except that the portmaster is supposed to advertise /29 /30 ... etc. if that is the valid subnet of a current session. If you don't want to see routes other than the /28 you need to have the portmaster agregate the routes to the desired netmask .... this is the nature of vlsm routing ... you can have routes for most of any cidr block and still redirect smaller pieces to other places. Quoting ratbert@phoenix.aye.net (ratbert@phoenix.aye.net) On Subject: Re: route changes erratically (routed) Date: Sun, Oct 25, 1998 at 02:11:30PM -0500 > > We've had some similar problems with our portmasters, OSPF and rip2 both > seemed to be broken on them. We assigned an x.x.x.x/28 for the dialup > lines and the portmasters ended up broadcasting themselves as a route > to a x.x.x.x/28 and /29s, /30s, /31s and /32s within the /28. > Pretty much turned the routing tables of everything on our network to > complete garbage. > > What we did to solve it was add a static route on our servers and other > routers with the portmaster as a gateway to the dialup subnet assigned > to it. Have the static dialup ip addresses be on the same network with > the portmasters and servers and let the portmasters proxyarp for those > ip addresses. > > On Fri, 23 Oct 1998, Leif Neland wrote: > > > We have 2 portmasters (PM2), several servers, a cisco to the world, and a > > firewall to the internal network. > > > > The cisco is default gateway > > > > The servers and portmasters are on one class C, the dialins are on another > > class C. > > > > Because some users have fixed ip, but can dial in on either of the > > portmasters, I run routed on all servers, and the portmasters seem to > > announce on which portmaster the customer is, so the route gets changed to > > the right portmaster. > > > > The traceroute should then go from server to pm1 or pm2 to customer. > > > > However, often the route changes so it goes > > server->cisco->pm->client or > > server->firewall->pm->client or even > > server->cisco->(router at our uplink)->cisco->(router at our uplink) etc. > > > > If I constantly pings the client, I gets pauses where the pings are lost. > > > > What do I do wrong? Shouldn't I use routed on the servers, but only route > > default gateway to the cisco, and let it handle the pm1/pm2 route changes? > > Or should I have one server running routed? or gated? or what? > > > > Help!!! > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981025131724.A19988>