[quagga-users 1722] Re: ospfd pointopoint configuration

PC Drew drewpc at ibsncentral.com
Mon Apr 19 15:26:14 IST 2004


Did you do the following:

- do a 'no shut' on the interface
- clear the OSPF process

after changing the netmasks?

On Apr 19, 2004, at 2:11 PM, Andrew J. Schorr wrote:

> In private mail, Paul Cammidge wrote:
>
>> the extra route is because it is learning the route from the other
>> peer.  i am sure that mine has the same route, and it has been working
>> fine for years.
>>
>> this is a symptom of using /255 addresses on the interfaces, so cisco
>> doesnt have that problem.  i havent tried the new versions of quagga,
>> which allow /252 netmasks.  that would possibly solve the problem, 
>> but i
>> havent tried.
>
> I reconfigured the T3 interfaces to use a /30 (.252) netmask:
>
> [hero at ti62 /]$ ip -f inet addr show wan0
> 5: wan0: <POINTOPOINT,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     inet 192.168.161.1 peer 192.168.161.2/30 brd 192.168.161.3 scope 
> global wan0
>
> But this seems even worse.  We still get the bogus route to the
> local interface:
>
> ti62-ospfd> sh ip ospf route
> ============ OSPF network routing table ============
> N    10.147.33.224/27      [32] area: 0.0.0.0
>                            via 192.168.161.2, wan0
> N    192.168.11.0/24       [10] area: 0.0.0.0
>                            directly attached to eth0.11
> N    192.168.161.1/32      [44] area: 0.0.0.0
>                            via 192.168.161.2, wan0
> N    192.168.161.2/32      [22] area: 0.0.0.0
>                            directly attached to wan0
>
>
> This looks the same as before, but for some reason most of the routes 
> are
> marked as inactive and not put in the kernel routing table:
>
> [hero at ti62 /]$ ip route ls | grep zebra
> 192.168.161.2 dev wan0  proto zebra  metric 22 equalize
>
> And according to zebra:
>
> ti62-quagga> sh ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>        B - BGP, > - selected route, * - FIB route
>
> K>* 0.0.0.0/0 via 192.168.10.1, eth0
> O   10.147.33.224/27 [110/32] via 192.168.161.2 inactive, 00:02:02
> K * 127.0.0.0/8 is directly connected, lo
> C>* 127.0.0.0/8 is directly connected, lo
> O   192.168.11.0/24 [110/10] is directly connected, eth0.11, 00:02:07
> K * 192.168.11.0/24 is directly connected, eth0.11
> C>* 192.168.11.0/24 is directly connected, eth0.11
> C>* 192.168.161.0/30 is directly connected, wan0
> O   192.168.161.1/32 [110/44] via 192.168.161.2 inactive, 00:02:02
> O>* 192.168.161.2/32 [110/22] is directly connected, wan0, 00:02:07
>
>
> Any thoughts?
>
> Thanks,
> Andy
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users
>

--
PC Drew
Manager, Dominet

IBSN
1600 Broadway, Suite 400
Denver, CO 80202

Dominet: 1-866-366-4638
Phone: 303-984-4727 x107
Cell: 720-841-4543
Fax: 303-984-4730
Email: drewpc at ibsncentral.com



More information about the Quagga-users mailing list