Hmm... I haven't worked with tap devices before, but I remember seeing this in the kernel config:
Code:
Universal TUN/TAP device driver support (TUN)
TUN/TAP provides packet reception and transmission for user space
programs. It can be viewed as a simple Point-to-Point or Ethernet
device, which instead of receiving packets from a physical media,
receives them from user space program and instead of sending packets
via physical media writes them to the user space program.
When a program opens /dev/net/tun, driver creates and registers
corresponding net device tunX or tapX. After a program closed above
devices, driver will automatically delete tunXX or tapXX device and
all routes corresponding to it.
It's in the networking section of the kernel config - not sure if you've compiled kernels before - if not, take a look at
http://www.digitalhermit.com/linux/K...ild-HOWTO.html
I wouldn't know what it's like compiling for Suse though as I'd have thought it's quite a custom kernel. Check in /boot and /usr/src and see if there are any "config" files about (on the machine that works) and we can check if the tap support is compiled in (and deduce if that's the problem).