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 (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. 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 say, after boot and after network restart? //Peter
