[quagga-dev 1353] Re: 802.1q vlan questions

mikeliu mikeliu at nmi.iii.org.tw
Wed Jul 14 12:07:23 BST 2004


On Tue, 13 Jul 2004, mikeliu wrote:

> 'ip address' says,
>
> 1: lo: <LOOPBACK,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 scope global lo
> 2: sw0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>    link/ether 00:90:27:57:1b:00 brd ff:ff:ff:ff:ff:ff
>    inet 192.168.8.120/25 brd 192.168.8.127 scope global sw0
> 3: sw0.2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>    link/ether 00:90:27:57:1b:00 brd ff:ff:ff:ff:ff:ff
>    inet 130.233.235.1/24 brd 130.233.235.255 scope global sw0.2

Ok..

>> How did you compile Quagga btw?
>
> use mips_fp_be-gcc cross compiler for IDT32332 CPU.

Unusual :)

With what configure options though?

./configure --build=i686-pc-linux-gnu --host=mips-unknown-linux-gnu --disable-ipv6 --disable-bgpd --enable-vtysh

> Enable 'debug zebra kernel',  then create a new vlan interface(vlan 2) and
> configure ip info(130.233.235.1/24) on it.
> zlog says,
>
> 2000/01/01 00:00:18 ZEBRA: ip:0 netmask:0 next_hop:c0a80801 ifindex:0 type:1
> 2000/01/01 00:08:02 ZEBRA: interface sw0.2 index 0 becomes active.
                                        ^^^^^^^^^^^^^

sw0.2 index 0? What were the logs immediately before this? Can you 
post all relevant logs pertaining to both sw0 and sw0.2?


Turn on both 'debug zebra kernel' and 'debug zebra event', then create a new vlan 2 and configuer ip info on it. All of the zlogs are as follows.

------------------------------------------------------------------------------------------------------------------------------------------------------
2000/01/01 00:00:18 ZEBRA: ip:0 netmask:0 next_hop:c0a80801 ifindex:0 type:1
2000/01/01 00:00:37 ZEBRA: MESSAGE: ZEBRA_INTERFACE_ADD sw0.2
2000/01/01 00:00:37 ZEBRA: interface sw0.2 index 0 becomes active.
2000/01/01 00:00:37 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(1
6), seq=0, pid=0

2000/01/01 00:00:42 ZEBRA: MESSAGE: ZEBRA_INTERFACE_UP sw0.2
2000/01/01 00:00:42 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWADDR(20), seq=7

2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=RTM_NEWADDR
(20), seq=7, pid=0
2000/01/01 00:00:42 ZEBRA: MESSAGE: ZEBRA_INTERFACE_ADDRESS_ADD 130.233.235.1/24
 on sw0
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(1
6), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: interface sw0.2 is still created by netlink!
2000/01/01 00:00:42 ZEBRA: MESSAGE: ZEBRA_INTERFACE_ADD sw0.2
2000/01/01 00:00:42 ZEBRA: interface sw0.2 index 3 becomes active.
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(1
6), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWADDR(2
0), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:00:42 ZEBRA: RTM_NEWROUTE ipv4 unicast proto kernel
2000/01/01 00:00:42 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:00:43 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel
---------------------------------------------------------------------------------------------------------------------------------------------------------

> 2000/01/01 00:08:02 ZEBRA: netlink_parse_info: netlink-listen type
> RTM_NEWLINK(1
> 6), seq=0, pid=0
>
> 2000/01/01 00:08:07 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWADDR(20),
> seq=7
>
> 2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-cmd ACK:
> type=RTM_NEWADDR
> (20), seq=7, pid=0
> 2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-listen type
> RTM_NEWLINK(1
> 6), seq=0, pid=0
> 2000/01/01 00:08:07 ZEBRA: interface sw0.2 is still created by netlink!
> 2000/01/01 00:08:07 ZEBRA: interface sw0.2 index 3 becomes active.

and then RTM_NEWLINK _again_, presumably above there was already an 
RTM_NEWLINK for sw0.2 shortly before the first log message, for 
sw0.2?

Don't know why it has 2 RTM_NEWLINK and the log "2000/01/01 00:00:42 ZEBRA: MESSAGE: ZEBRA_INTERFACE_ADDRESS_ADD 130.233.235.1/24 on sw0" is unusual.


Thanks again!


Mike

> Really don't know why interface sw0.2 can be created by netlink 
> since if_lookup_by_name seems works fine.

My bets are still on a mistake in the sw or else vlan driver you are 
using. Afaik, regular Linux ethX drivers and the vlan layer work 
fine.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20040714/93d138aa/attachment-0001.html>


More information about the Quagga-dev mailing list