Mailing List Archive

What does the log file say?
Does netstat show an eth0?

Also try using vtysh and if your not running 0.94 I would also suggest
you upgrade.

Ted

On Mon, 2003-11-17 at 04:59, uwe.schmeling@t-online.de wrote:
> Hi all,
> just trying to migrate from zebra -> quagga (forced by SUSE 9.0
> update). Using my recently running configuration
> I get the above message:
> show ip ospf interface
> eth0 is down
> OSPF not enabled on this interface
>
> show running-config:
>
> Current configuration:
> !
> hostname vngw
> password xxxxxx
> enable password yyyyyy
> log file /var/log/quagga/ospfd.log
> !
> debug ospf ism
> debug ospf zebra
> debug ospf event
> debug ospf packet all
> !
> !
> interface eth0
> !
> router ospf
> ospf router-id 192.168.200.3
> redistribute kernel metric 20
> redistribute connected metric 20
> redistribute static metric 20
> network 192.168.200.0/24 area 0.0.0.0
> !
> line vty
> !
> end
>
> Searched the docu and google for a solution but without any success
> regards Uwe
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users

Andrew J. Schorr wrote:
> On Thu, Apr 06, 2006 at 06:54:50AM +0000, Dmitriy Gorbenko wrote:
>
>> pegas# show ip ospf interface fxp0
>> fxp0 is down
>> ifindex 0, MTU 0 bytes, BW 0 Kbit <>
>> OSPF not enabled on this interface
>> -----------------------------------------------------------------------------------------
>> And I have reasonable question: Why OSPF not enabled on fxp0 interface ?
>> Thanks for helping me.
>>
>
> It seems that ospfd believes the interface is down.
>
> What is the output from "ifconfig fxp0"? And please post the
> output from the zebra command "show interface fxp0".
>
> Regards,
> Andy
here whey are:

root@pegas# ifconfig fxp0
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
inet6 fe80::2a0:c9ff:fe42:b8e9%fxp0 prefixlen 64 scopeid 0x1
inet 192.168.5.251 netmask 0xffffff00 broadcast 192.168.5.255
ether 00:a0:c9:42:b8:e9
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
root@pegas# telnet localhost zebra
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Hello, this is Quagga (version 0.99.3).
Copyright 1996-2005 Kunihiro Ishiguro, et al.


User Access Verification

Password:
pegas> show interface fxp0
Interface fxp0 is up, line protocol detection is disabled
index 1 metric 0 mtu 1500 <UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
inet 192.168.5.251/24 broadcast 192.168.5.255
input packets 464433, bytes 37492869, dropped 0, multicast packets
410990
input errors 0
output packets 44704, bytes 8968151, multicast packets 5
output errors 0
collisions 0
pegas>

So, as I see, "line protocol detection is disabled" cause ospfd daemon
to think that "fxp0 is down" ?

Regards,
Dmitriy

Andrew J. Schorr wrote:
> On Thu, Apr 06, 2006 at 12:10:29PM +0000, Dmitriy Gorbenko wrote:
>
>> Yes ), I also see it, but I compiled quagga from source code
>> (./configure --disable-ipv6),and daemons tries to create such vty-files
>> in "/var/run" directory.
>> So, I have to make the daemons create files in /var/run/quagga directory.
>> Can you tell me, how to tell to daemons to create such files in
>> different directory.
>> Or I need to correct source code ? (Because, I don't seen such options
>> in "./configure" util or in quagga.pdf document)
>> Thanks.
>>
>
> This is a site/platform-specific issue. On my linux box, I call configure
> as follows:
>
> ./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc/quagga --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib/quagga --libexecdir=/usr/libexec/quagga --localstatedir=/var/run/quagga --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --enable-ipv6 --enable-snmp --enable-multipath=64 --enable-nssa --enable-opaque-lsa --enable-ospf-te --enable-vtysh --enable-ospfclient=yes --enable-ospfapi=yes --enable-irdp=yes --disable-isisd --with-libpam --enable-user=quagga --enable-group=quagga --enable-vty-group=quaggavty --enable-netlink --enable-gcc-ultra-verbose --enable-gcc-rdynamic
>
> Some or all of this may not be appropriate for your platform.
>
> Regards,
> Andy
>
> P.S. Please CC the mailing list on all messages so that others may help.
>
>
Yes, right !
I use "--localstatedir=/var/run/quagga" option of "configure" script and
ospfd begin work fine.
Very thanks.

On Thu, Apr 06, 2006 at 11:19:44AM +0000, Dmitriy Gorbenko wrote:
> pegas> show interface fxp0
> Interface fxp0 is up, line protocol detection is disabled
> index 1 metric 0 mtu 1500 <UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> inet 192.168.5.251/24 broadcast 192.168.5.255
> input packets 464433, bytes 37492869, dropped 0, multicast packets
> 410990
> input errors 0
> output packets 44704, bytes 8968151, multicast packets 5
> output errors 0
> collisions 0
> pegas>
>
> So, as I see, "line protocol detection is disabled" cause ospfd daemon
> to think that "fxp0 is down" ?

Very strange. What's the full output from the zebra "show interface"
command? And can you please also post the output from
the ospfd "show ip ospf interface" command? I wonder if there
is a communication problem between zebra and ospfd, such that
ospfd is not getting the proper interface configuration information
from zebra. Are you sure the sockets are permissioned properly
for the two daemons to communicated?

Regards,
Andy
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users

On Thu, Apr 06, 2006 at 11:46:00AM +0000, Dmitriy Gorbenko wrote:
> hm... I think what problem exactly in communication between two
> daemons... Now 'll try to check it, and here are outputs:
...
> pegas> show ip ospf interface
> fxp0 is down
> ifindex 0, MTU 0 bytes, BW 0 Kbit <>
> OSPF not enabled on this interface
> fxp1 is down
> ifindex 0, MTU 0 bytes, BW 0 Kbit <>
> OSPF not enabled on this interface
> pegas>

Yes, it certainly seems that ospfd is not able to retrieve any of
the interface configuration information from zebra. Please check
the directory where the sockets should be. For example, on my
linux host, I have:

sh-2.05b# ls -l /var/run/quagga
total 12
-rw------- 1 quagga quagga 5 Aug 15 2005 ospfd.pid
srwxrwx--- 1 quagga quaggavty 0 Aug 15 2005 ospfd.vty
-rw------- 1 root root 5 Aug 15 2005 watchquagga.pid
-rw------- 1 quagga quagga 5 Aug 15 2005 zebra.pid
srwxrwx--- 1 quagga quaggavty 0 Aug 15 2005 zebra.vty
srwx------ 1 quagga quagga 0 Aug 15 2005 zserv.api

The ospfd daemon needs to connect to the zserv.api socket.

Regards,
Andy
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users

On Thu, Apr 06, 2006 at 12:10:29PM +0000, Dmitriy Gorbenko wrote:
> Yes ), I also see it, but I compiled quagga from source code
> (./configure --disable-ipv6),and daemons tries to create such vty-files
> in "/var/run" directory.
> So, I have to make the daemons create files in /var/run/quagga directory.
> Can you tell me, how to tell to daemons to create such files in
> different directory.
> Or I need to correct source code ? (Because, I don't seen such options
> in "./configure" util or in quagga.pdf document)
> Thanks.

This is a site/platform-specific issue. On my linux box, I call configure
as follows:

./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc/quagga --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib/quagga --libexecdir=/usr/libexec/quagga --localstatedir=/var/run/quagga --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --enable-ipv6 --enable-snmp --enable-multipath=64 --enable-nssa --enable-opaque-lsa --enable-ospf-te --enable-vtysh --enable-ospfclient=yes --enable-ospfapi=yes --enable-irdp=yes --disable-isisd --with-libpam --enable-user=quagga --enable-group=quagga --enable-vty-group=quaggavty --enable-netlink --enable-gcc-ultra-verbose --enable-gcc-rdynamic

Some or all of this may not be appropriate for your platform.

Regards,
Andy

P.S. Please CC the mailing list on all messages so that others may help.
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users

On Thu, 6 Apr 2006, Andrew J. Schorr wrote:

> The ospfd daemon needs to connect to the zserv.api socket.

We probably ought to give up on doing this via FS permissions and use
socket credentials instead.

Would be easier to configure (and impossible to configure
incorrectly).

regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
Fortune:
The only reason some people get lost in thought is because it's unfamiliar
territory.
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users