lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 20 Nov 2008 09:24:45 -0500 (EST)
From:	Gerhard Mack <gmack@...erfire.net>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.26.x and 2.6.27.x 2.6.27-rc* regression: ssh and tun/tap
 problem.


I have a series of gateways using ssh tunnels and I have discovered that 
they stop working if I upgrade them past kernel 2.6.25.  This seems to 
happen regardless of the reciving end's kernel version.

About 20 to 30 seconds after the tunnel comes up the interface stops 
recieving packets with no errors show on the remote side and the local 
side showing a single dropped packet.  If I tcpdump a ping it shows that 
the remote side is getting packets and is replying but the local side is 
only sending.  This problem is only cleared by resetting the tunnel but 
then it only works for another 20 to 30 seconds.

None of the other interfaces show any errors and traffic flows over them 
without problem.

Anyone have any idea what has gone wrong?

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
           inet addr:172.16.1.2  P-t-P:172.16.1.1  Mask:255.255.255.252
           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:1 overruns:0 frame:0
           TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:500
           RX bytes:0 (0.0 B)  TX bytes:1884 (1.8 KiB)
 
--
Gerhard Mack

gmack@...erfire.net

<>< As a computer I find your faith in technology amusing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ