Mailing List Archive: config used to wrk in 0.93b doesnt in 0.94-20030807

config used to wrk in 0.93b doesnt in 0.94-20030807

Aug 7, 2003, 7:09 AM

Post #1 of 6 (2174 views)

got:

saias12 / 147# ip addr show
1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
qlen 100
link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1

wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1 via ripv2.

got:

saias12 / 148# cat /etc/zebra.conf

log file /var/log/zebra.log
debug zebra events
debug zebra kernel
password password

# static route for VIP out all ints

ip route 172.31.254.254/32 eth0
ip route 172.31.254.254/32 eth1

saias12 / 149# cat /etc/ripd.conf

log file /var/log/ripd.log
password password
debug rip zebra
interface eth0
interface eth1

router rip
timers basic 20 40 60
redistribute static
redistribute connected
network eth0
network eth1
distribute-list in in eth0
distribute-list out out eth0
distribute-list in in eth1
distribute-list out out eth1

access-list in deny any
access-list out permit 172.31.254.254/32
access-list out deny any

line vty

any help is appreciated.

--
Cheers,
Anthony

Re: config used to wrk in 0.93b doesnt in 0.94-20030807 [ In reply to ]

tedm at toybox

Aug 7, 2003, 9:42 PM

Post #2 of 6 (2156 views)

Permalink

I've run into this same problem with the routed under FreeBSD,
it doesen't want to advertise routes using a /32 subnet either.
Cisco IOS does advertise such routes. Perhaps this is a
non-standard change to the RIP standard?

Ted

>-----Original Message-----
>From: quagga-users-bounces@lists.quagga.net
>[mailto:quagga-users-bounces@lists.quagga.net]On Behalf Of
>Anthony.Golia@morganstanley.com
>Sent: Thursday, August 07, 2003 7:09 AM
>To: quagga-users@lists.quagga.net
>Subject: [quagga-users 93] config used to wrk in 0.93b doesnt in
>0.94-20030807
>
>
>got:
>
>saias12 / 147# ip addr show
>1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
> inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
>2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
>qlen 100
> link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
> inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
>3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
> inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1
>
>wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1 via ripv2.
>
>got:
>
>saias12 / 148# cat /etc/zebra.conf
>
>log file /var/log/zebra.log
>debug zebra events
>debug zebra kernel
>password password
>
># static route for VIP out all ints
>
>ip route 172.31.254.254/32 eth0
>ip route 172.31.254.254/32 eth1
>
>saias12 / 149# cat /etc/ripd.conf
>
>log file /var/log/ripd.log
>password password
>debug rip zebra
>interface eth0
>interface eth1
>
>router rip
> timers basic 20 40 60
> redistribute static
> redistribute connected
> network eth0
> network eth1
> distribute-list in in eth0
> distribute-list out out eth0
> distribute-list in in eth1
> distribute-list out out eth1
>
>access-list in deny any
>access-list out permit 172.31.254.254/32
>access-list out deny any
>
>line vty
>
>any help is appreciated.
>
>
>--
>Cheers,
>Anthony
>
>_______________________________________________
>Quagga-users mailing list
>Quagga-users@lists.quagga.net
>http://lists.quagga.net/mailman/listinfo/quagga-users
>

Re: config used to wrk in 0.93b doesnt in 0.94-20030807 [ In reply to ]

Anthony.Golia at morganstanley

Aug 8, 2003, 11:28 AM

Post #3 of 6 (2147 views)

Permalink

I hope not, it's a cool concept and i need it.

Ted Mittelstaedt wrote:
> I've run into this same problem with the routed under FreeBSD,
> it doesen't want to advertise routes using a /32 subnet either.
> Cisco IOS does advertise such routes. Perhaps this is a
> non-standard change to the RIP standard?
>
> Ted
>
>
>>-----Original Message-----
>>From: quagga-users-bounces@lists.quagga.net
>>[mailto:quagga-users-bounces@lists.quagga.net]On Behalf Of
>>Anthony.Golia@morganstanley.com
>>Sent: Thursday, August 07, 2003 7:09 AM
>>To: quagga-users@lists.quagga.net
>>Subject: [quagga-users 93] config used to wrk in 0.93b doesnt in
>>0.94-20030807
>>
>>
>>got:
>>
>>saias12 / 147# ip addr show
>>1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
>> inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
>>2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
>>qlen 100
>> link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
>> inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
>>3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>> link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
>> inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1
>>
>>wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1 via ripv2.
>>
>>got:
>>
>>saias12 / 148# cat /etc/zebra.conf
>>
>>log file /var/log/zebra.log
>>debug zebra events
>>debug zebra kernel
>>password password
>>
>># static route for VIP out all ints
>>
>>ip route 172.31.254.254/32 eth0
>>ip route 172.31.254.254/32 eth1
>>
>>saias12 / 149# cat /etc/ripd.conf
>>
>>log file /var/log/ripd.log
>>password password
>>debug rip zebra
>>interface eth0
>>interface eth1
>>
>>router rip
>> timers basic 20 40 60
>> redistribute static
>> redistribute connected
>> network eth0
>> network eth1
>> distribute-list in in eth0
>> distribute-list out out eth0
>> distribute-list in in eth1
>> distribute-list out out eth1
>>
>>access-list in deny any
>>access-list out permit 172.31.254.254/32
>>access-list out deny any
>>
>>line vty
>>
>>any help is appreciated.
>>
>>
>>--
>>Cheers,
>>Anthony
>>
>>_______________________________________________
>>Quagga-users mailing list
>>Quagga-users@lists.quagga.net
>>http://lists.quagga.net/mailman/listinfo/quagga-users
>>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users
>
>

--
Cheers,
Anthony

Re: config used to wrk in 0.93b doesnt in 0.94-20030807 [ In reply to ]

tedm at toybox

Aug 9, 2003, 12:53 AM

Post #4 of 6 (2143 views)

Permalink

We use this as well, with a terminal server but I would hardly
call it a cool concept. It's actually ugly IMHO because the
terminal server is too stupid to drop an incoming packet directed
to an IP number that is no longer in service.

Ted

>-----Original Message-----
>From: Anthony.Golia@morganstanley.com
>[mailto:Anthony.Golia@morganstanley.com]
>Sent: Friday, August 08, 2003 11:29 AM
>To: Ted Mittelstaedt
>Cc: quagga-users@lists.quagga.net
>Subject: Re: [quagga-users 105] Re: config used to wrk in 0.93b doesnt
>in 0.94-20030807
>
>
>I hope not, it's a cool concept and i need it.
>
>Ted Mittelstaedt wrote:
>> I've run into this same problem with the routed under FreeBSD,
>> it doesen't want to advertise routes using a /32 subnet either.
>> Cisco IOS does advertise such routes. Perhaps this is a
>> non-standard change to the RIP standard?
>>
>> Ted
>>
>>
>>>-----Original Message-----
>>>From: quagga-users-bounces@lists.quagga.net
>>>[mailto:quagga-users-bounces@lists.quagga.net]On Behalf Of
>>>Anthony.Golia@morganstanley.com
>>>Sent: Thursday, August 07, 2003 7:09 AM
>>>To: quagga-users@lists.quagga.net
>>>Subject: [quagga-users 93] config used to wrk in 0.93b doesnt in
>>>0.94-20030807
>>>
>>>
>>>got:
>>>
>>>saias12 / 147# ip addr show
>>>1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
>>> inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
>>>2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
>>>qlen 100
>>> link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
>>> inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
>>>3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>>> link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
>>> inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1
>>>
>>>wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1
>via ripv2.
>>>
>>>got:
>>>
>>>saias12 / 148# cat /etc/zebra.conf
>>>
>>>log file /var/log/zebra.log
>>>debug zebra events
>>>debug zebra kernel
>>>password password
>>>
>>># static route for VIP out all ints
>>>
>>>ip route 172.31.254.254/32 eth0
>>>ip route 172.31.254.254/32 eth1
>>>
>>>saias12 / 149# cat /etc/ripd.conf
>>>
>>>log file /var/log/ripd.log
>>>password password
>>>debug rip zebra
>>>interface eth0
>>>interface eth1
>>>
>>>router rip
>>> timers basic 20 40 60
>>> redistribute static
>>> redistribute connected
>>> network eth0
>>> network eth1
>>> distribute-list in in eth0
>>> distribute-list out out eth0
>>> distribute-list in in eth1
>>> distribute-list out out eth1
>>>
>>>access-list in deny any
>>>access-list out permit 172.31.254.254/32
>>>access-list out deny any
>>>
>>>line vty
>>>
>>>any help is appreciated.
>>>
>>>
>>>--
>>>Cheers,
>>>Anthony
>>>
>>>_______________________________________________
>>>Quagga-users mailing list
>>>Quagga-users@lists.quagga.net
>>>http://lists.quagga.net/mailman/listinfo/quagga-users
>>>
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users@lists.quagga.net
>> http://lists.quagga.net/mailman/listinfo/quagga-users
>>
>>
>
>
>--
>Cheers,
>Anthony
>
>

Re: config used to wrk in 0.93b doesnt in 0.94-20030807 [ In reply to ]

paul at clubi

Aug 9, 2003, 7:59 PM

Post #5 of 6 (2135 views)

Permalink

On Thu, 7 Aug 2003 Anthony.Golia@morganstanley.com wrote:

> got:
>
> saias12 / 147# ip addr show
> 1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
> inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
> 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
> qlen 100
> link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
> inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
> 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
> inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1
>
> wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1 via ripv2.
>
> got:
>
> saias12 / 148# cat /etc/zebra.conf
>
> log file /var/log/zebra.log
> debug zebra events
> debug zebra kernel
> password password
>
> # static route for VIP out all ints
>
> ip route 172.31.254.254/32 eth0
> ip route 172.31.254.254/32 eth1
>
> saias12 / 149# cat /etc/ripd.conf
>
> log file /var/log/ripd.log
> password password
> debug rip zebra
> interface eth0
> interface eth1
>
> router rip
> timers basic 20 40 60
> redistribute static
> redistribute connected
> network eth0
> network eth1
> distribute-list in in eth0
> distribute-list out out eth0
> distribute-list in in eth1
> distribute-list out out eth1
>
> access-list in deny any
> access-list out permit 172.31.254.254/32
> access-list out deny any
>
> line vty
>
> any help is appreciated.

can you give more details? what happens?

and the access-list? is that right? should it not be a prefix-list?
(never used ripd - but generally prefix-list's filter routes,
access-list filter connections to the router).

regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
warning: do not ever send email to spam@dishone.st
Fortune:
He who renders warfare fatal to all engaged in it will be the greatest
benefactor the world has yet known.
-- Sir Richard Burton

Re: config used to wrk in 0.93b doesnt in 0.94-20030807 [ In reply to ]

Anthony.Golia at morganstanley

Aug 11, 2003, 6:58 AM

Post #6 of 6 (2141 views)

Permalink

Paul Jakma wrote:
> On Thu, 7 Aug 2003 Anthony.Golia@morganstanley.com wrote:
>
>
>>got:
>>
>>saias12 / 147# ip addr show
>>1: lo: <LOOPBACK,NOARP,UP> mtu 16436 qdisc noqueue
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
>> inet 172.31.254.254/32 brd 127.255.255.255 scope global lo:1
>>2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
>>qlen 100
>> link/ether 00:50:8b:75:f7:58 brd ff:ff:ff:ff:ff:ff
>> inet 172.31.245.41/24 brd 172.31.245.255 scope global eth0
>>3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>> link/ether 00:50:8b:75:f7:57 brd ff:ff:ff:ff:ff:ff
>> inet 172.31.246.41/24 brd 172.31.246.255 scope global eth1
>>
>>wanna advertise just 172.31.254.254/32 out *both* eth0 and eth1 via ripv2.
>>
>>got:
>>
>>saias12 / 148# cat /etc/zebra.conf
>>
>>log file /var/log/zebra.log
>>debug zebra events
>>debug zebra kernel
>>password password
>>
>># static route for VIP out all ints
>>
>>ip route 172.31.254.254/32 eth0
>>ip route 172.31.254.254/32 eth1
>>
>>saias12 / 149# cat /etc/ripd.conf
>>
>>log file /var/log/ripd.log
>>password password
>>debug rip zebra
>>interface eth0
>>interface eth1
>>
>>router rip
>> timers basic 20 40 60
>> redistribute static
>> redistribute connected
>> network eth0
>> network eth1
>> distribute-list in in eth0
>> distribute-list out out eth0
>> distribute-list in in eth1
>> distribute-list out out eth1
>>
>>access-list in deny any
>>access-list out permit 172.31.254.254/32
>>access-list out deny any
>>
>>line vty
>>
>>any help is appreciated.
>
>
> can you give more details? what happens?
>
> and the access-list? is that right? should it not be a prefix-list?
> (never used ripd - but generally prefix-list's filter routes,
> access-list filter connections to the router).
>
> regards,

thx for the response. i want to filter routes, i guess i'll look into
prefix-list, anyway, it just doesn't advert any routes, even if i remove
the access-list/ distribute-list lines. the same config averts the /32
IP RIP route out eth0 and eth1.

--
Cheers,
Anthony