- Bird-users - Mailing Lists

Want to Join Bird users mailing group
by Ashish 08 May '06

08 May '06

Want to Join Bird users mailing group With Regards, Ashish __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

BIRD at Interop (is this list still alive?)
by Hege Trosvik 19 Apr '06

19 Apr '06

Hi, the iLabs open source software area is planning to demonstrate BIRD as one of our open source routing stacks at Interop, where our demo includes an infrastructure entirely based on open source, and routing is one part of it. First, I'm not sure if the BIRD project is even alive, since the last piece of news I see on the web page is from 2/21/2005. But, hopefully somebody is still working on this project and reading this alias. My BGP peering between BIRD and it's peer (currently testing with a Cisco catalyst3550) keeps going down. Not only does the peering go down, but it seems that bird stops receiving anything on it's interface. However if I leave an ssh session with the box running bird open, the interface (and peering) comes up again as soon as I touch ssh session. Leaving a ping running in the window with my ssh session also will keep the interface from going down. This could of course mean I have bad hardware, but I seem to recall running into a similar problem with bird before and wanted to check if this is a known problem. Regards, Hege

3 3

OSPF Flags mismatch
by Paul P Komkoff Jr 23 Mar '06

23 Mar '06

Hi. What's the purpose of this exact check? if (ps->options != ifa->oa->opt.byte) { log(L_ERR "%s%I%soptions mismatch (0x%x).", beg, faddr, rec, ps->options); return; } Cisco router want to set EA in it's options. I don't know for sure but I think it is valid for us to just accept this hello (they want EAL but we won't send them) Am I right? -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head

1 0

deleting direct route from kernel routing table
by Martin Kraus 07 Feb '06

07 Feb '06

hello, just a quick question. i deleted an ip adress from an interface, bird noticed it, deleted the associated network route from it's routing table, but didn't delete it from the kernel routing table. the kernel route for that network was put there by bird, so i would guess it should clean it up, or am i mistaken? thanks martin

2 1

Where can I get some help?
by bird＠richins.org 07 Feb '06

07 Feb '06

Seriously, is this list used for anything other than spam? I subscribed because I needed a little support. If no one other than spammers use this list, it is useless. If I have come to the wrong place, and you happen to know where the corect place is, please let me know. Also, be aware that this is an aliased account that can (and will) be deleted if abused. If you've got this far, I must assume that either you have a morbid sense of curiosity, or you actually care. Either case, here is my problem: I am currently using Debian Woody and routed as a firewall. I wish to upgrade to Debian Sarge (which comes with bird) From what I have read, it is an impressive project, and definately diserves to be included in the distro. My problem is that bind is having issues when used through a PPPoE connection (or possibly I just don't know how to set it up for one) It seems to recognize the interface with the tunnel endpoint address, and not the actual public IP that I am assigned through the tunnel. Using a DSL-Modem as a PPPoE end point is not an option for me as I do not have a DSL connection. I am subscribed to a FTTP solution (Fiber to the Premise) wherein my provider offers me a 100Mbit ehternet conenction. I must then use a router that supports PPPoE for conneciton. I refuse to use their provided D-Link router as it lacks way too many features. I'm sure that there is additional information that I could give to help troubleshoot this but I am unsure what to give. Thanks in advance for any help.

2 1

Is BIRD alive ? (was Re: La página de internet)
by Xavier Beaudouin 31 Jan '06

31 Jan '06

Hello, I am asking myself if BIRD is still alive, because the spam there is getting more traffic than replys to question asked here... Is there anybody here that have being successfull working bird in production environment ? Thanks. /Xavier

7 11

Bird on FreeBSD ?
by Xavier Beaudouin 30 Nov '05

30 Nov '05

Hi there, I am trying to make bird running (mostly on bgp first... other protocols will be used when I'll have finaly finished to it running... I currently running the FreeBSD port of bird : root@freebsd:/usr/local/etc# pkg_info | grep bird bird-1.0.11 Dynamic IP routing daemon But when trying to start it in order to make some testing with bgp I get the following error : root@freebsd:/usr/local/etc# bird -c /usr/local/etc/bird.conf -d bird: /usr/local/etc/bird.conf, line 77: parse error According to configuration file error is : protocol bgp { local as 65335; neighbor 192.168.0.9 as 65334; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ # multihop 40 via 192.168.0.254; hold time 240; startup hold time 240; connect retry time 120; (full configuration file is added in attachement in this mail). What is the problem ? Or did I have badly understood configuration file example given in the tarball ? Thanks, /Xavier -- Quand on essaye continuellement, on finit par y arriver. Donc, plus ca rate, plus on a de chance que ca marche... (Proverbe Shadok)

1 0

authentication message-digest ?
by Dmitry Melekhov 28 Nov '05

28 Nov '05

Hello! I have cisco with following config: router ospf 1 area 0 authentication message-digest ..... interface Fa 0/0 ip ospf message-digest-key 10 md5 .... I installed bird 1.0.11 on machine with linux 2.4.31 and wrote following in config: interface "eth0" { type broadcast; authentication cryptographic; password "pass"; }; And I get : Nov 26 12:09:19 vpn_22_203 bird: Bad OSPF packet from 192.168.22.253 - authentification failed Doesn it mean that bird doesn't support authentication message-digest? Thank you!

2 1

Bird/Cisco OSPF interaction
by Matthew V. Weigl 15 Nov '05

15 Nov '05

Found an interestnig issue running bird in Talisman code on a WRT54G router. I could not develop a neighbor relationship with my Catalyst 3560 running 12.2(25)SEC2 and then 12.2(25)SED advanced ip services code. An Ethereal trace revealed that the 3560 was sending EA options, while the WRT54G was sending E options. A further search revealed that Ethereal decode is incorrect and that the option is Local Link. A change to the config on the 3560 OSPF process (no capability local-link) resolved the issue. Just thought I'd post in case anyone else experiecnes the issue. -- Matt Weigl

1 0

Bird problem
by cavalbe＠inwind.it 15 Nov '05

15 Nov '05

Hi, i have a problem with bird daemon.... Reading the log file /val/log/birdlog i have read this message: messaggio Then i have tried to identify the reason and i have understood that these messages are printed when launch: ifup eth*. I use the last version of bird (1.0.11) but the same message was present in the preview version (1.0.10). The S.O. where bird is installed is debian with kernel 2.6.9 I tried to increase the level of debug editing the bird.conf and i have obtained this logs: 2005 18:36:04 MyOSPF: Initializing 15-11-2005 18:36:04 direct1: Starting 15-11-2005 18:36:04 direct1: State changed to feed 15-11-2005 18:36:04 kernel1: Starting 15-11-2005 18:36:04 kernel1: State changed to feed 15-11-2005 18:36:04 device1: Starting 15-11-2005 18:36:04 device1: Scanning interfaces 15-11-2005 18:36:04 Guessed router ID 192.168.1.6 according to interface eth1 15-11-2005 18:36:04 device1: State changed to feed 15-11-2005 18:36:04 static1: Starting 15-11-2005 18:36:04 static1: State changed to feed 15-11-2005 18:36:04 MyOSPF: Starting 15-11-2005 18:36:04 MyOSPF: State changed to feed 15-11-2005 18:36:04 direct1 < primary address 127.0.0.0/8 on interface lo added 15-11-2005 18:36:04 direct1 > added [best] 127.0.0.0/8 dev lo 15-11-2005 18:36:04 direct1 < primary address 192.168.1.32/30 on interface eth0 added 15-11-2005 18:36:04 direct1 > added [best] 192.168.1.32/30 dev eth0 15-11-2005 18:36:04 direct1 < primary address 192.168.1.4/30 on interface eth1 added 15-11-2005 18:36:04 direct1 > added [best] 192.168.1.4/30 dev eth1 15-11-2005 18:36:04 direct1 < primary address 192.168.2.0/24 on interface eth2 added 15-11-2005 18:36:04 direct1 > added [best] 192.168.2.0/24 dev eth2 15-11-2005 18:36:04 direct1 < primary address 192.168.1.48/28 on interface eth3 added 15-11-2005 18:36:04 direct1 > added [best] 192.168.1.48/28 dev eth3 15-11-2005 18:36:04 direct1: State changed to up 15-11-2005 18:36:04 kernel1: Connected to table master 15-11-2005 18:36:04 kernel1 < added 192.168.2.0/24 dev eth2 15-11-2005 18:36:04 kernel1 < added 192.168.1.4/30 dev eth1 15-11-2005 18:36:04 kernel1 < added 127.0.0.0/8 dev lo 15-11-2005 18:36:04 kernel1 < added 192.168.1.48/28 dev eth3 15-11-2005 18:36:04 kernel1 < added 192.168.1.32/30 dev eth0 15-11-2005 18:36:04 kernel1: State changed to up 15-11-2005 18:36:04 device1: State changed to up 15-11-2005 18:36:04 static1 < interface lo goes up 15-11-2005 18:36:04 static1 < interface eth0 goes up 15-11-2005 18:36:04 static1 < interface eth1 goes up 15-11-2005 18:36:04 static1 < interface eth2 goes up 15-11-2005 18:36:04 static1 < interface eth3 goes up 15-11-2005 18:36:04 static1: State changed to up 15-11-2005 18:36:04 MyOSPF: Connected to table master 15-11-2005 18:36:04 MyOSPF < interface lo goes up 15-11-2005 18:36:04 MyOSPF < interface eth0 goes up 15-11-2005 18:36:04 MyOSPF: Using interface eth0. 15-11-2005 18:36:04 MyOSPF < interface eth1 goes up 15-11-2005 18:36:04 MyOSPF: Using interface eth1. 15-11-2005 18:36:04 MyOSPF < interface eth2 goes up 15-11-2005 18:36:04 MyOSPF: Using interface eth2. 15-11-2005 18:36:04 MyOSPF < interface eth3 goes up 15-11-2005 18:36:04 MyOSPF: Using interface eth3. 15-11-2005 18:36:04 MyOSPF < filtered out 192.168.2.0/24 dev eth2 15-11-2005 18:36:04 MyOSPF < filtered out 192.168.1.4/30 dev eth1 15-11-2005 18:36:04 MyOSPF < out of scope 127.0.0.0/8 dev lo 15-11-2005 18:36:04 MyOSPF < filtered out 192.168.1.48/28 dev eth3 15-11-2005 18:36:04 MyOSPF < filtered out 192.168.1.32/30 dev eth0 15-11-2005 18:36:04 MyOSPF: State changed to up 15-11-2005 18:36:04 kernel1: Scanning routing table 15-11-2005 18:36:04 kernel1: 0.0.0.0/0: [alien] created 15-11-2005 18:36:04 kernel1: Pruning table master 15-11-2005 18:36:04 kernel1: Pruning inherited routes 15-11-2005 18:36:04 kernel1 > added [best] 0.0.0.0/0 via 192.168.2.1 on eth2 15-11-2005 18:36:04 kernel1 < added 0.0.0.0/0 via 192.168.2.1 on eth2 15-11-2005 18:36:04 MyOSPF < filtered out 0.0.0.0/0 via 192.168.2.1 on eth2 15-11-2005 18:36:04 MyOSPF: Changing state of iface: eth3 from "down" into "waiting". 15-11-2005 18:36:04 MyOSPF: Hello sent via eth3 15-11-2005 18:36:04 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:04 MyOSPF: Changing state of iface: eth2 from "down" into "waiting". 15-11-2005 18:36:04 MyOSPF: Hello sent via eth2 15-11-2005 18:36:04 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:04 MyOSPF: Changing state of iface: eth1 from "down" into "waiting". 15-11-2005 18:36:04 MyOSPF: Hello sent via eth1 15-11-2005 18:36:04 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:04 MyOSPF: Changing state of iface: eth0 from "down" into "waiting". 15-11-2005 18:36:04 MyOSPF: Hello sent via eth0 15-11-2005 18:36:04 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:05 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:05 MyOSPF: New neighbor found: 192.168.2.16 on eth2. 15-11-2005 18:36:05 MyOSPF: Neighbor 192.168.2.16 changes state from " down" to " init". 15-11-2005 18:36:05 MyOSPF: Neighbor 192.168.2.16 changes state from " init" to " 2way". 15-11-2005 18:36:05 MyOSPF: Changing state of iface: eth2 from "waiting" into "backup". 15-11-2005 18:36:05 MyOSPF: Originating RT_lsa for area "0.0.0.0". 15-11-2005 18:36:05 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:05 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:05 MyOSPF: Starting routing table calculation 15-11-2005 18:36:05 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:05 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:05 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:05 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:05 MyOSPF > added 192.168.2.0/24 dev eth2 15-11-2005 18:36:05 MyOSPF > added 192.168.1.4/30 dev eth1 15-11-2005 18:36:05 MyOSPF > added 192.168.1.48/28 dev eth3 15-11-2005 18:36:05 MyOSPF > added 192.168.1.32/30 dev eth0 15-11-2005 18:36:06 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:13 MyOSPF: Hello sent via eth0 15-11-2005 18:36:13 MyOSPF: Hello sent via eth1 15-11-2005 18:36:13 MyOSPF: Hello sent via eth2 15-11-2005 18:36:13 MyOSPF: Hello sent via eth3 15-11-2005 18:36:13 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:13 MyOSPF: Neighbor 192.168.2.16 changes state from " 2way" to " exstart". 15-11-2005 18:36:14 MyOSPF: DB_DES (I) sent to 192.168.2.16 via eth2. 15-11-2005 18:36:14 device1: Scanning interfaces 15-11-2005 18:36:17 MyOSPF: Received dbdes from 192.168.2.16 via eth2. 15-11-2005 18:36:17 MyOSPF: I'm slave to 192.168.2.16. 15-11-2005 18:36:17 MyOSPF: Neighbor 192.168.2.16 changes state from " exstart" to "exchange". 15-11-2005 18:36:17 MyOSPF: DB_DES (M) sent to 192.168.2.16 via eth2. 15-11-2005 18:36:17 MyOSPF: Received dbdes from 192.168.2.16 via eth2. 15-11-2005 18:36:17 MyOSPF: DB_DES (M) sent to 192.168.2.16 via eth2. 15-11-2005 18:36:17 MyOSPF: Neighbor 192.168.2.16 changes state from "exchange" to " loading". 15-11-2005 18:36:19 MyOSPF: LS request sent to: 192.168.2.16 15-11-2005 18:36:19 MyOSPF: Received LS upd from 192.168.2.16 15-11-2005 18:36:19 MyOSPF: Premature aging self originated lsa. 15-11-2005 18:36:19 MyOSPF: Type: 2, Id: 192.168.1.6, Rt: 192.168.1.6 15-11-2005 18:36:19 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:19 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:19 MyOSPF: Premature aging self originated lsa. 15-11-2005 18:36:19 MyOSPF: Type: 1, Id: 192.168.1.6, Rt: 192.168.1.6 15-11-2005 18:36:19 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:19 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:19 MyOSPF: Neighbor 192.168.2.16 changes state from " loading" to " full". 15-11-2005 18:36:19 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:20 MyOSPF: Originating RT_lsa for area "0.0.0.0". 15-11-2005 18:36:20 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:20 MyOSPF: Starting routing table calculation 15-11-2005 18:36:20 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:20 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:20 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:20 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:20 MyOSPF > removed 192.168.2.0/24 dev eth2 15-11-2005 18:36:20 MyOSPF: LS ack sent to 192.168.2.16 (delayed) 15-11-2005 18:36:20 MyOSPF: Received LS upd from 192.168.2.16 15-11-2005 18:36:20 MyOSPF: Received LS upd from 192.168.2.16 15-11-2005 18:36:20 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:20 MyOSPF: Received LS ack from 192.168.2.16 15-11-2005 18:36:20 MyOSPF: Strange LS acknoledgement from 192.168.2.16 15-11-2005 18:36:20 MyOSPF: Id: 192.168.1.6, Rt: 192.168.1.6, Type: 1 15-11-2005 18:36:20 MyOSPF: I have: Age: 0, Seqno: 0x80000002, Sum: 42999 15-11-2005 18:36:20 MyOSPF: He has: Age: 15, Seqno: 0x80000001, Sum: 12798 15-11-2005 18:36:21 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:21 MyOSPF: Starting routing table calculation 15-11-2005 18:36:21 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:21 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:21 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:21 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:21 MyOSPF > added 192.168.2.0/24 dev eth2 15-11-2005 18:36:22 MyOSPF: Received LS upd from 192.168.2.16 15-11-2005 18:36:22 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:22 MyOSPF: LS ack sent to 192.168.2.16 (direct) 15-11-2005 18:36:22 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:22 MyOSPF: Starting routing table calculation 15-11-2005 18:36:22 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:22 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:22 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:22 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:22 MyOSPF: LS ack sent to 192.168.2.16 (delayed) 15-11-2005 18:36:22 MyOSPF: Hello sent via eth3 15-11-2005 18:36:22 MyOSPF: Hello sent via eth2 15-11-2005 18:36:22 MyOSPF: Hello sent via eth1 15-11-2005 18:36:22 MyOSPF: Hello sent via eth0 15-11-2005 18:36:22 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:23 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:24 MyOSPF: LS upd sent to 192.168.2.16 (1 LSAs) 15-11-2005 18:36:24 device1: Scanning interfaces 15-11-2005 18:36:24 MyOSPF: Wait timer fired on interface eth0. 15-11-2005 18:36:24 MyOSPF: Changing state of iface: eth0 from "waiting" into "dr". 15-11-2005 18:36:24 MyOSPF: Wait timer fired on interface eth1. 15-11-2005 18:36:24 MyOSPF: Changing state of iface: eth1 from "waiting" into "dr". 15-11-2005 18:36:24 MyOSPF: Wait timer fired on interface eth2. 15-11-2005 18:36:24 MyOSPF: Wait timer fired on interface eth3. 15-11-2005 18:36:24 MyOSPF: Changing state of iface: eth3 from "waiting" into "dr". 15-11-2005 18:36:24 kernel1: Scanning routing table 15-11-2005 18:36:24 kernel1: 0.0.0.0/0: [alien] seen 15-11-2005 18:36:24 kernel1: Pruning table master 15-11-2005 18:36:24 kernel1: Pruning inherited routes 15-11-2005 18:36:26 MyOSPF: Received LS ack from 192.168.2.16 15-11-2005 18:36:31 MyOSPF: Hello sent via eth0 15-11-2005 18:36:31 MyOSPF: Hello sent via eth1 15-11-2005 18:36:31 MyOSPF: Hello sent via eth2 15-11-2005 18:36:31 MyOSPF: Hello sent via eth3 15-11-2005 18:36:31 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:31 direct1 < primary address 192.168.1.4/30 on interface eth1 removed 15-11-2005 18:36:31 kernel1 < replaced 192.168.1.4/30 dev eth1 15-11-2005 18:36:31 Netlink: Network is down 15-11-2005 18:36:31 MyOSPF < rejected by protocol 192.168.1.4/30 dev eth1 15-11-2005 18:36:31 direct1 > removed [replaced] 192.168.1.4/30 dev eth1 15-11-2005 18:36:31 static1 < interface eth1 goes down 15-11-2005 18:36:31 MyOSPF < interface eth1 goes down 15-11-2005 18:36:31 MyOSPF: Killing interface eth1. 15-11-2005 18:36:31 MyOSPF: Changing state of iface: eth1 from "dr" into "down". 15-11-2005 18:36:31 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:32 MyOSPF: Originating RT_lsa for area "0.0.0.0". 15-11-2005 18:36:32 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:32 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:32 MyOSPF: Starting routing table calculation 15-11-2005 18:36:32 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:32 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:32 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:32 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:32 kernel1 < removed 192.168.1.4/30 dev eth1 15-11-2005 18:36:32 MyOSPF > removed [sole] 192.168.1.4/30 dev eth1 15-11-2005 18:36:33 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:34 MyOSPF: Received LS ack from 192.168.2.16 15-11-2005 18:36:34 device1: Scanning interfaces 15-11-2005 18:36:40 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:40 MyOSPF: Hello sent via eth3 15-11-2005 18:36:40 MyOSPF: Hello sent via eth2 15-11-2005 18:36:40 MyOSPF: Hello sent via eth0 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:43 nl_parse_link: Malformed message received 15-11-2005 18:36:44 device1: Scanning interfaces 15-11-2005 18:36:44 static1 < interface eth1 goes up 15-11-2005 18:36:44 MyOSPF < interface eth1 goes up 15-11-2005 18:36:44 MyOSPF: Using interface eth1. 15-11-2005 18:36:44 direct1 < primary address 192.168.1.4/30 on interface eth1 added 15-11-2005 18:36:44 direct1 > added [best] 192.168.1.4/30 dev eth1 15-11-2005 18:36:44 kernel1 < added 192.168.1.4/30 dev eth1 15-11-2005 18:36:44 MyOSPF < filtered out 192.168.1.4/30 dev eth1 15-11-2005 18:36:44 kernel1: Scanning routing table 15-11-2005 18:36:44 kernel1: 0.0.0.0/0: [alien] seen 15-11-2005 18:36:44 kernel1: Pruning table master 15-11-2005 18:36:44 kernel1: Pruning inherited routes 15-11-2005 18:36:44 MyOSPF: Changing state of iface: eth1 from "down" into "waiting". 15-11-2005 18:36:44 MyOSPF: Hello sent via eth1 15-11-2005 18:36:44 MyOSPF: Scheduling RT lsa origination for area 0.0.0.0. 15-11-2005 18:36:45 MyOSPF: Originating RT_lsa for area "0.0.0.0". 15-11-2005 18:36:45 MyOSPF: Scheduling RT calculation. 15-11-2005 18:36:45 MyOSPF: LS upd flooded via eth2 15-11-2005 18:36:45 MyOSPF: Starting routing table calculation 15-11-2005 18:36:45 MyOSPF: Starting routing table calculation for area 0.0.0.0 15-11-2005 18:36:45 MyOSPF: Starting routing table calculation for inter-area (area 0.0.0.0) 15-11-2005 18:36:45 MyOSPF: Starting routing table calculation for ext routes 15-11-2005 18:36:45 MyOSPF: Starting routing table synchronisation 15-11-2005 18:36:45 MyOSPF > added 192.168.1.4/30 dev eth1 15-11-2005 18:36:46 nl_parse_link: Malformed message received 15-11-2005 18:36:46 MyOSPF: Running ospf_age cleanup 15-11-2005 18:36:46 MyOSPF: Received LS ack from 192.168.2.16 15-11-2005 18:36:49 MyOSPF: Hello sent via eth0 15-11-2005 18:36:49 MyOSPF: Hello sent via eth2 15-11-2005 18:36:49 MyOSPF: Hello sent via eth3 15-11-2005 18:36:49 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:36:53 MyOSPF: Hello sent via eth1 15-11-2005 18:36:54 device1: Scanning interfaces 15-11-2005 18:36:58 MyOSPF: Hello sent via eth3 15-11-2005 18:36:58 MyOSPF: Hello sent via eth2 15-11-2005 18:36:58 MyOSPF: Hello sent via eth0 15-11-2005 18:36:58 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:37:02 MyOSPF: Hello sent via eth1 15-11-2005 18:37:04 device1: Scanning interfaces 15-11-2005 18:37:04 MyOSPF: Wait timer fired on interface eth1. 15-11-2005 18:37:04 MyOSPF: Changing state of iface: eth1 from "waiting" into "dr". 15-11-2005 18:37:04 kernel1: Scanning routing table 15-11-2005 18:37:04 kernel1: 0.0.0.0/0: [alien] seen 15-11-2005 18:37:04 kernel1: Pruning table master 15-11-2005 18:37:04 kernel1: Pruning inherited routes 15-11-2005 18:37:07 MyOSPF: Hello sent via eth0 15-11-2005 18:37:07 MyOSPF: Hello sent via eth2 15-11-2005 18:37:07 MyOSPF: Hello sent via eth3 15-11-2005 18:37:07 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:37:11 MyOSPF: Hello sent via eth1 15-11-2005 18:37:14 device1: Scanning interfaces 15-11-2005 18:37:16 MyOSPF: Hello sent via eth3 15-11-2005 18:37:16 MyOSPF: Hello sent via eth2 15-11-2005 18:37:16 MyOSPF: Hello sent via eth0 15-11-2005 18:37:16 MyOSPF: Received hello from 192.168.2.16 via eth2 15-11-2005 18:37:20 MyOSPF: Hello sent via eth1 it's possible that the problem are my hw wifi, i have a 3 whifi card pci "artem"...mmm what is the problem? thank

1 0