bugzilla-daemon at mindrot.org
2006-Sep-18 12:17 UTC
[Bug 1232] "LocalCommand" is executed before "Tunnel" is set up
bugzilla.mindrot.org/show_bug.cgi?id=1232 Summary: "LocalCommand" is executed before "Tunnel" is set up Product: Portable OpenSSH Version: 4.3p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: h.goebel at goebel-consult.de "LocalCommand" is documented as being executed _after_ the local machine after successfully connecting to the server. But as it's implemented now, this is done _before_ "Tunnel" is set up. Thus the tunnel device is not present at the time when "LocalCommand" is executed. Thus "LocalCommand" can not be used to configure the tunnel device. Here is some debugging output debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] Device tap7 does not seem to be present, delaying initialization. debug1: Entering interactive session. debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting tun. debug1: sys_tun_open: tap7 mode 2 fd 7 debug1: channel 1: new [tun] The "Device tap7 does not seem ..." message is from the LocalCommand. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Maybe Matching Threads
- [Bug 1231] "Tunnel ethernet" always uses next tap-device
- [Bug 1233] "Tunnel" should pass device-name to "LocalCommand"
- [Bug 2365] New: openssh client ignores -o Tunnel=ethernet option, creating an IP tunnel device instead of an ethernet tap device
- [Bug 1280] LocalCommand and variables
- RFC: non-root ssh tun access