Bug 1231 - "Tunnel ethernet" always uses next tap-device
Summary: "Tunnel ethernet" always uses next tap-device
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 4.3p2
Hardware: ix86 Linux
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords: help-wanted
Depends on:
Blocks:
 
Reported: 2006-09-18 22:08 AEST by h.goebel
Modified: 2008-04-04 09:56 AEDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description h.goebel 2006-09-18 22:08:31 AEST 
When using "Tunnel ethernet", the client always uses the next available device number. Options like "-w 11" or "-w 11:any" are ignored.

This makes "Tunnel ethernet" unusable.

Debug-output seam okay:

  debug1: Requesting tun.
  debug1: sys_tun_open: tap7 mode 2 fd 7
  debug1: channel 1: new [tun]

but 'ifconfig -a' reports:
  tap11   Link encap:Ethernet  Hardware Adresse ....
          BROADCAST MULTICAST  MTU:1500  Metric:1
          ...
Comment 1 Damien Miller 2007-06-22 14:36:30 AEST 
I can't recreate this using either -current or "OpenSSH_4.3p2 Debian-8ubuntu1" on the server end - the tap devices are created as requested and their numbers are correct.

Linux kernel in this case was 2.6.20-16-generic (i686).

If you are still experiencing this problem, please attach a full client and server log.
Comment 2 Damien Miller 2008-01-20 11:44:16 AEDT 
no reply and couldn't reproduce - closing
Comment 3 Damien Miller 2008-04-04 09:56:11 AEDT 
Close resolved bugs after release.