
bugzilla-daemon at allevil
May 18, 2008, 5:16 PM
Post #1 of 1
(2753 views)
Permalink
|
|
[Bug 454] New: OSPFd failed to reconize interface as being UP
|
|
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. http://bugzilla.quagga.net/show_bug.cgi?id=454 Summary: OSPFd failed to reconize interface as being UP Product: Quagga Version: 0.98.6 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: Low Component: ospfd AssignedTo: maintainers [at] quagga ReportedBy: lorenl [at] north-winds ospfd would not recognize the interface eth0 as being UP. eth0 is the primary interface attached to my private network. I installed and started ospfd and zebra remotely over an ssh connection using eth0. I attempted to remove and re-add the interface with the following commands: (config-router)# no network 192.168.1.6/24 area 0.0.0.0 (config-router)# network 192.168.1.0/24 area 0.0.0.0 (config-router)# no network 192.168.1.0/24 area 0.0.0.0 (config-router)# network 192.168.1.6/24 area 0.0.0.0 (config-router)# end # show ip ospf inter eth0 eth0 is down OSPF not enabled on this interface I was using an identical ospf configuration on two other routers minus router-id and ip address without problems. One peculiarity with the router that was not working was that it had a second ip subnet assigned to it that was 169.254.0.2/16. This subnet MAY have been assigned after I started ospfd, but it WAS before I configured ospfd (except for the password lines). Once I manually restarted ospfd with the same configuration, it came up correctly and found eth0 as being UP. Current configuration: ! hostname router.example.com password ****** enable password ****** log file /tmp/ospfd.log ! debug ospf ism debug ospf event ! ! interface eth0 ip ospf authentication-key ****** ! router ospf ospf router-id 192.168.1.6 redistribute connected redistribute static redistribute rip redistribute bgp network 192.168.1.6/24 area 0.0.0.0 ! line vty ! end ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ Quagga-bugs mailing list Quagga-bugs [at] lists http://lists.quagga.net/mailman/listinfo/quagga-bugs
|