Bug 146147 - vlan disapears
Summary: vlan disapears
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Major
Target Milestone: ---
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-27 13:03 UTC by Subredu Manuel
Modified: 2006-02-27 12:03 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
strace log (6.36 KB, application/octet-stream)
2006-01-27 13:04 UTC, Subredu Manuel
Details
output of hwinfo (295.93 KB, application/octet-stream)
2006-01-27 14:01 UTC, Subredu Manuel
Details
output of cat /proc/net/dev/ (4.65 KB, application/octet-stream)
2006-01-27 14:01 UTC, Subredu Manuel
Details
strace of ifconfig vlan10 (8.09 KB, application/octet-stream)
2006-01-27 14:33 UTC, Subredu Manuel
Details
ltrace of ifconfig vlan10 (35.82 KB, application/octet-stream)
2006-01-27 14:33 UTC, Subredu Manuel
Details
ltrace of ifconfig vlan11 (17.62 KB, application/octet-stream)
2006-01-27 14:33 UTC, Subredu Manuel
Details
new ifconfig (58.74 KB, application/octet-stream)
2006-01-27 14:43 UTC, Karsten Keil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Subredu Manuel 2006-01-27 13:03:57 UTC
I have a OpenSuSE 10 installed on a intel server. The server has 6 network interfaces, 2 on board and 4 on PCI ports. 5 of the network interfaces have vlan on them. When the server is booted all works fine. After some undefined period of time the vlan interfaces cannot be accessed using ifconfig command.

ifconfig vlan201
: error fetching interface information: Device not found

The vlan still exists in the kernel. 

router:~ # find /sys -name vlan201
/sys/class/net/vlan201
router:~ # ls -l /sys/class/net/vlan201/
total 0
drwxr-xr-x   3 root root    0 2006-01-26 20:25 .
drwxr-xr-x  38 root root    0 2006-01-26 20:25 ..
-r--r--r--   1 root root 4096 2006-01-26 20:25 address
-r--r--r--   1 root root 4096 2006-01-27 14:55 addr_len
-r--r--r--   1 root root 4096 2006-01-27 14:55 broadcast
-r--r--r--   1 root root 4096 2006-01-27 14:55 carrier
-r--r--r--   1 root root 4096 2006-01-27 14:55 features
-rw-r--r--   1 root root 4096 2006-01-27 14:55 flags
-r--r--r--   1 root root 4096 2006-01-26 20:25 ifindex
-r--r--r--   1 root root 4096 2006-01-27 14:55 iflink
-rw-r--r--   1 root root 4096 2006-01-27 14:55 mtu
drwxr-xr-x   2 root root    0 2006-01-26 20:25 statistics
-rw-r--r--   1 root root 4096 2006-01-27 14:55 tx_queue_len
-r--r--r--   1 root root 4096 2006-01-27 14:55 type
-rw-r--r--   1 root root 4096 2006-01-27 14:55 weight

 I can use tcpdump -i vlan201 -n and I can see the traffic passing trough the vlan. The network traffic is working as expected, but any attempt to use ifconfig fails. From time to time, ifconfig segfaults.

ifconfig vlan201
Segmentation fault

The interesting part is that only the vlans passing trough the PCI connected network cards disapear. The ones passing trough the onboard network cards can be accessed by ifconfig command.
I'll attach the file created by strace -o log ifconfig vlan201 .
Comment 1 Subredu Manuel 2006-01-27 13:04:32 UTC
Created attachment 65392 [details]
strace log
Comment 2 Subredu Manuel 2006-01-27 13:05:38 UTC
I forgot to mention that the network driver is e1000 from the kernel that comes with the distro.
Comment 3 Karsten Keil 2006-01-27 13:53:21 UTC
Maybe a overflow in some internal buffer of ifconfig.
Can you attach the output of 'cat /proc/net/dev' in the failure state ?
And which vlan interface did still work ?
And please some more infos about the HW (maybe attach hwinfo).
Comment 4 Subredu Manuel 2006-01-27 14:01:22 UTC
Created attachment 65403 [details]
output of hwinfo
Comment 5 Subredu Manuel 2006-01-27 14:01:43 UTC
Created attachment 65405 [details]
output of cat /proc/net/dev/
Comment 6 Subredu Manuel 2006-01-27 14:04:02 UTC
All the vlan interfaces receive and transmit packets. At this moment I can use ifconfig only on vlan10.
Comment 7 Karsten Keil 2006-01-27 14:08:39 UTC
Also not vlan11 ,vlan12 ?
If vlan10 still works, please attach also a strace with this working device.
Comment 9 Subredu Manuel 2006-01-27 14:33:02 UTC
Created attachment 65408 [details]
strace of ifconfig vlan10
Comment 10 Subredu Manuel 2006-01-27 14:33:24 UTC
Created attachment 65409 [details]
ltrace of ifconfig vlan10
Comment 11 Subredu Manuel 2006-01-27 14:33:44 UTC
Created attachment 65411 [details]
ltrace of ifconfig vlan11
Comment 12 Subredu Manuel 2006-01-27 14:34:40 UTC
ifconfig vlan11 and ifconfig vlan12 worked 2 hours ago. Now the vlans are not accesible for ifconfig .
Comment 13 Karsten Keil 2006-01-27 14:43:30 UTC
Created attachment 65419 [details]
new ifconfig

Please test this ifconfig.
Comment 14 Subredu Manuel 2006-01-27 15:00:01 UTC
It works !!

 (old ifconfig)
router:~ # /sbin/ifconfig vlan11
: error fetching interface information: Device not found

 (new ifconfig)
router:~ # ./ifconfig vlan11
vlan11    Link encap:Ethernet  HWaddr 00:04:23:C3:34:E6  
          inet addr:x.x.x.x  Bcast:x.x.x.x  Mask:x.x.x.x
          inet6 addr: fe80::204:23ff:fec3:34e6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5006306 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5089087 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1583408129 (1510.0 Mb)  TX bytes:623049237 (594.1 Mb)

PS: I replaced the IP information with x.x.x.x from obvious reasons ;)
Comment 15 Karsten Keil 2006-01-27 15:34:03 UTC
OK, then the issue is already known and fixed for SUSE Linux 10.1 (you can fetch the sources for the fixed net-tools package from the OSS factory tree http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
Maybe we need an update for 10.0.
Comment 16 Subredu Manuel 2006-01-27 15:38:47 UTC
Let's suppose that I rebuild net-tools from the 10.1 sources. If something bad happend and you issue a update for net-tools from 10.0 what should I do ? Patch the file myself ? Make a mixed stuff ? 
 I think is better that you create a update for the package. Maybe there are more people in my situation.
Comment 18 Mads Martin Joergensen 2006-01-27 15:57:32 UTC
Andreas, can I please get a SWAMP ID for updating this for 9.1, 9.2, 9.3 and 10.0?
Comment 19 Andreas Jaeger 2006-01-29 06:43:20 UTC
Maintenance-Tracker-3442
Comment 20 Mads Martin Joergensen 2006-01-31 09:58:55 UTC
Updates submitted for all dists.
Comment 21 Hendrik Vogelsang 2006-02-06 11:01:48 UTC
resubmitted 9.1
Comment 22 Anja Stock 2006-02-27 12:03:19 UTC
released