Bug 1932 - Bridging over eth0 and tap0 (via tun driver)
Summary: Bridging over eth0 and tap0 (via tun driver)
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Arnaldo Carvalho de Melo
Depends on:
Reported: 2004-01-22 01:51 UTC by Stanislav Opichal
Modified: 2006-11-21 12:10 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.4.20, 2.4.22, 2.4.22-ac4
Regression: ---
Bisected commit-id:


Description Stanislav Opichal 2004-01-22 01:51:12 UTC

RedHat 9.0
Hardware Environment:

ThinkPad R40, 
eth0 device
  bus: PCI
  driver: e100
  desc: "Intel Corp.|82801BD PRO/100 VE (MOB) Ethernet Controller"
  vendorId: 8086
  deviceId: 103d
  subVendorId: 1014
  subDeviceId: 0522
  pciType: 1

Software Environment:

2.4.x, lately tested in 2.4.22-ac4, also the RedHat's kernels suffer from this

Problem Description:

When a bridge is build over the eth0 and tap0 (driven by tun module) everything
works well until the eth0 cabel is physicaly plugged into the hub. After that I
get kernel panic (the blinking capslock LED).

Steps to reproduce:

Get tun driver using software (creating the tap0 nif - I use this
http://aranym.sf.net) and create a bridge over the real eth0 you are using to go
out and the tap0. Plug the eth0 cabel into the hub. You should get kernel panic.
Comment 1 Stephen Hemminger 2006-07-25 16:31:05 UTC
Does this still happen with 2.6 kernel?
Comment 2 Adrian Bunk 2006-11-21 12:10:17 UTC
Please reopen this bug if it's still present in kernel 2.6.18.

Note You need to log in before you can comment on or make changes to this bug.