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

mikeliu mikeliu at nmi.iii.org.tw
Tue Jul 13 05:05:53 BST 2004


----- Original Message -----
From: "Paul Jakma" <paul at clubi.ie>
To: "mikeliu" <mikeliu at nmi.iii.org.tw>
Cc: <quagga-dev at lists.quagga.net>
Sent: Monday, July 12, 2004 9:59 PM
Subject: [quagga-dev 1349] Re: 802.1q vlan questions


> On Mon, 12 Jul 2004, mikeliu wrote:
>
> > VLAN layer seems correct because "ifconfig" shows interface info
correctly.
>
> what does the 'ip' utility say? 'ip address'.


'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

> > Before configuring ip info on a newly created vlan interface,
> > switching among different vlans works fine. It possibly means
> > if_lookup_by_name is okey. However, after configuing ip info on
> > vlan 2, "show interface" shows 2 interface sw0 as follows and zlog
>
> How did you compile Quagga btw?

use mips_fp_be-gcc cross compiler for IDT32332 CPU.

> > shows "000/01/01 00:01:58 ZEBRA: interface sw0.2 is still created
> > by netlink!". This log info is really stange since interface sw0.2
> > should already exist.
>
> Ah..
>
> > Any other clues are highly appreciated!
>
> Dont have any really.
>
> Can you enable 'debug zebra kernel' and get output of what netlink is
> sending for these interfaces?

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.
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.
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: netlink_parse_info: netlink-listen type
RTM_NEWADDR(2
0), seq=0, pid=0
2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-listen type
RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:08:07 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel
2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-listen type
RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:08:07 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel
2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-listen type
RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:08:07 ZEBRA: RTM_NEWROUTE ipv4 unicast proto kernel
2000/01/01 00:08:07 ZEBRA: netlink_parse_info: netlink-listen type
RTM_NEWROUTE(
24), seq=0, pid=0
2000/01/01 00:08:07 ZEBRA: RTM_NEWROUTE ipv4 multicast proto kernel


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

Thank you so much for your kindly assistance!


Mike






More information about the Quagga-dev mailing list