?? 9.6.2006 23:02 Peter Stuge ??????:
: Hi,
:
: On Fri, Jun 09, 2006 at 06:51:53PM +0300, Svetoslav wrote:
: [ with 2.6.16.14 ]
:
: > After reboot the system everything seems to be normal, but after
: > restarting network service
: > "ip" shows interesting sequences of devices:
: > # ip addr ls
: > 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 host lo
: > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc pfifo_fast qlen 1000
: > link/ether 00:50:45:bb:d6:d4 brd ff:ff:ff:ff:ff:ff
: > inet 169.254.100.105/24 brd 169.254.100.255 scope global eth0
: > 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
: > link/ether 00:50:45:bb:d6:d5 brd ff:ff:ff:ff:ff:ff
: > inet 192.168.21.2/24 brd 192.168.21.255 scope global eth1
: > 874: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
: > link/ether 00:50:45:bb:d6:d4 brd ff:ff:ff:ff:ff:ff
: > inet 192.168.23.250/30 brd 192.168.23.251 scope global vlan135
: > 937: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
: > link/ether 00:50:45:bb:d6:d4 brd ff:ff:ff:ff:ff:ff
: > inet 192.168.151.130/30 brd 192.168.151.131 scope global vlan905
:
: What exactly is the problem with the above? It looks good to me. But
: see note below on name-type. (The naming scheme for VLAN interfaces.)
:
: On Fri, Jun 09, 2006 at 09:03:19PM +0300, Svetoslav wrote:
: > # ip addr ls
: > 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 host lo
: > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc pfifo_fast qlen 1000
: > link/ether 00:50:45:bb:d6:d4 brd ff:ff:ff:ff:ff:ff
: > inet 169.254.100.105/24 brd 169.254.100.255 scope global eth0
: > 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
: > link/ether 00:50:45:bb:d6:d5 brd ff:ff:ff:ff:ff:ff
: > inet 192.168.21.2/24 brd 192.168.21.255 scope global eth1
:
: Ok, this is different output, and the VLAN interfaces are missing.
: It may not matter, but please try running just:
: ip addr show
: or
: ip a s
ok
# ip addr show
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 host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc pfifo_fast qlen 1000
link/ether 00:50:45:bb:d6:d4 brd ff:ff:ff:ff:ff:ff
inet 169.254.100.105/24 brd 169.254.100.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:45:bb:d6:d5 brd ff:ff:ff:ff:ff:ff
inet 192.168.21.2/24 brd 193.151.21.255 scope global eth1
The output is the same
:
: (ip addr has no sub-command beginning with l, and some versions of
: the ip command have buggy argument parsing)
:
: > # dmesg
: > vlan135: add 01:00:5e:00:00:01 mcast address to master interface
: > register_vlan_device: ALREADY had VLAN registered
: > vlan135: del 01:00:5e:00:00:01 mcast address from master interface
: > vlan135: add 01:00:5e:00:00:01 mcast address to master interface
: > register_vlan_device: ALREADY had VLAN registered
: > register_vlan_device: ALREADY had VLAN registered
: > vlan905: add 01:00:5e:00:00:01 mcast address to master interface
: > register_vlan_device: ALREADY had VLAN registered
: > vlan135: del 01:00:5e:00:00:01 mcast address from master interface
: > vlan905: del 01:00:5e:00:00:01 mcast address from master interface
: > e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
: > e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
: > *******************
: > This is the full dmesg after restarting network service...
:
: Right, this looks fine. The VLAN interfaces are created already.
No, it is not look fine:
# dmesg -c; sleep 10; dmesg -c
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
#
:
: On Fri, Jun 09, 2006 at 09:19:22PM +0300, Svetoslav wrote:
: > Svetoslav wrote:
: > >Now I am with 2.6.16.19.
: > >The thing what is happen is, that vlans are showed as up interfaces,
: > >but they are not.
: > ># rcnetwork restart
: > > vlan135
: > > vlan135 IP address: 192.168.23.250/30
: > > done vlan905
: > > vlan905 IP address: 192.168.151.130/30
: > >done
: > > Setting up service network . . . . . . . . . .
: > >. . . . done
: >
: > May be this will be interesting:
: > Machine:~ # vconfig add eth0 135
: > Added VLAN with VID == 135 to IF -:eth0:-
: > Machine:~ # vconfig rem vlan135
: > ERROR: trying to remove VLAN -:vlan135:- error: Invalid argument
: > Machine:~ #
:
: Perhaps the name-type is set to something else than the networking
: scripts expect? The default changed from VLAN_PLUS_VID_NO_PAD to
: DEV_PLUS_VID_NO_PAD (aka RAW_PLUS_VID_NO_PAD) some time ago.
: Your scripts assume the old setting, VLAN_PLUS_VID_NO_PAD.
:
: What does
:
: cat /proc/net/vlan/config
# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_PLUS_VID_NO_PAD
I don't think that the problem is in name.
:
: say, after boot and after network restart?
after boot:
Machine:~ # cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_PLUS_VID_NO_PAD
vlan135 | 135 | eth0
vlan905 | 905 | eth0
Machine:~ # cat /proc/net/vlan/vlan135
vlan135 VID: 135 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 21
total bytes transmitted 882
total headroom inc 0
total encap on xmit 0
Device: eth0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:
Machine:~ # cat /proc/net/vlan/vlan905
vlan905 VID: 905 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 21
total bytes transmitted 882
total headroom inc 0
total encap on xmit 0
Device: eth0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:
Machine:~# ip addr show
4: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
5: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
*************************
After network restart:
8: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
9: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
Look at the sequence. After another restart:
Machine:~# ip addr show
10: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
11: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
And dmesg from reboot to now:
802.1Q VLAN Support v1.8 Ben Greear <greearb@xxxxxxxxxxxxxxx>
All bugs added by David S. Miller <davem@xxxxxxxxxx>
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
ip_tables: (C) 2000-2006 Netfilter Core Team
register_vlan_device: ALREADY had VLAN registered
register_vlan_device: ALREADY had VLAN registered
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (4093 buckets, 32744 max) - 312 bytes per conntrack
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
register_vlan_device: ALREADY had VLAN registered
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
register_vlan_device: ALREADY had VLAN registered
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
register_vlan_device: ALREADY had VLAN registered
register_vlan_device: ALREADY had VLAN registered
********************************************
And /proc:
Machine:~ # cat /proc/net/vlan/*
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_PLUS_VID_NO_PAD
vlan135 | 135 | eth0
vlan905 | 905 | eth0
vlan135 VID: 135 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 3
total bytes transmitted 126
total headroom inc 0
total encap on xmit 0
Device: eth0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:
vlan905 VID: 905 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 3
total bytes transmitted 126
total headroom inc 0
total encap on xmit 0
Device: eth0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:
******************************************************
Another restart:
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
14: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
As you see the vlan905 already missing!
Dmesg says that vlans are added and the immediately deleted:
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
************
And then vlan905 missing too...
Machine:~ # ip addr sh
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc pfifo_fast qlen 1000
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
Another network restart:
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
79: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
Vlan905 is here, but vlan135 is missing... A few seconds after that listing:
# ip addr sh
vlans are misiing completely. dmesg says that they are added and deleted:
# dmesg
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
vlan135: del 01:00:5e:00:00:01 mcast address from master interface
vlan905: add 01:00:5e:00:00:01 mcast address to master interface
vlan905: del 01:00:5e:00:00:01 mcast address from master interface
vlan135: add 01:00:5e:00:00:01 mcast address to master interface
register_vlan_device: ALREADY had VLAN registered
register_vlan_device: ALREADY had VLAN registered
# ip addr list
116: vlan135: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
This is without restart!
# ip addr list (4 times)
141: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
# ip addr list (19 times)
159: vlan905: <BROADCAST,MULTICAST,UP> mtu 1504 qdisc noqueue
And thats is what happen.
Can you understand?
:
: //Peter
Best regards
--
In God we Trust (all others must submit a X.509 certificate)
