[quagga-users 12405] Re: Zebra & IRDP

Alexandru Coseru alex.coseru at gmail.com
Sun Aug 14 00:11:14 IST 2011


Dear Ingo,

Thanks for your help, I have found the problem..

The routes are advertised with src of the first alias of the interface, and
my host is on the 3nd network:


border-nx# sh interface eth0.1147
Interface eth0.1147 is up, line protocol detection is disabled
  index 26 metric 1 mtu 1500
  flags: <UP,BROADCAST,RUNNING,MULTICAST>
  HWaddr: 00:30:48:7e:b6:08
  inet 10.1.10.11/24 broadcast 10.1.10.255 eth0.1147:17
  inet 141.85.48.6/24 broadcast 141.85.48.255 eth0.1147:11
  inet 192.68.98.1/24 broadcast 192.68.98.255 eth0.1147:9
  inet 192.168.98.1/24 broadcast 192.168.98.255 eth0.1147:5
    30799637596 input packets (329848 multicast), 34400046181696 bytes, 0
dropped
    0 input errors, 0 length, 0 overrun, 0 CRC, 0 frame
    0 fifo, 0 missed
    20281109410 output packets, 10613354085691 bytes, 0 dropped
    0 output errors, 0 aborted, 0 carrier, 0 fifo, 0 heartbeat
    0 window, 0 collisions


I can see ICMP broadcasts from 10.1.10.11, but my host has 192.68.98.3  (the
3rd network), and will silently ignore the multicasts.
They are two problems:
	1) maybe we should send an advertise for each network with it's own
source ip.  (IE:  Sent advertises on 10.1.10.11/24 with src 10.1.10.11, sent
advertises on 192.68.98.1/24 with 192.68.98.1, etc..)
	2) is there a way to set the src of the packets ?

Best Regards,
	Alex

-----Original Message-----
From: Ingo Flaschberger [mailto:if at xip.at] 
Sent: Sunday, August 14, 2011 1:41 AM
To: Alexandru Coseru
Cc: quagga-users at lists.quagga.net
Subject: Re: [quagga-users 12403] Zebra & IRDP

Dear Alexandru,

> I?m trying to make zebra export static and default route via IRDP, but so
far I only got some networks of the connected interface:

ever read the RFC?
http://tools.ietf.org/html/rfc1256

I don't expect that this is possible or that irdp is designed for 
advertising "routes".

If you don't receive a default route at the host - than it seems its a 
host problem and not one from the advertising router "quagga".

Kind regards,
 	Ingo Flaschberger
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3831 - Release Date: 08/13/11



More information about the Quagga-users mailing list