Ubuntu
openssh package

ssh tunnel dies unexpectedly several times a day

Bug #185524 reported by Oleksiy Kokachev
4
Affects Status Importance Assigned to Milestone
openssh (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Dear all.
I have a problem: my ssh tunnel works fine for a while (this time varies from minutes to hours) and then just stops to forward packets in one direction.
I tried to google this problem, but didn't find the solution.
Detailed description:
I have Gutsy on both machines. Machine A - is client, machine B - server. My /etc/network/interfaces files looks like this:
Machine A:
iface tun0 inet static
        pre-up echo 1 > /proc/sys/net/ipv4/ip_forward
        pre-up ssh -f -w 0:0 machine_b_ip_address 'ifdown tun0; ifup tun0'
        pre-up sleep 5
        address 10.0.0.1
        pointopoint 10.0.0.2
        netmask 255.255.255.0
        up route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.0.0.2 tun0
        down route del -net 192.168.1.0 netmask 255.255.255.0 gw 10.0.0.2 tun0
Machine B:
iface tun0 inet static
        pre-up echo 1 > /proc/sys/net/ipv4/ip_forward
        pre-up sleep 5
        address 10.0.0.2
        pointopoint 10.0.0.1
        netmask 255.255.255.0
        up route add -net 10.88.171.0 netmask 255.255.255.0 gw 10.0.0.1 tun0
        down route del -net 10.88.171.0 netmask 255.255.255.0 gw 10.0.0.1 tun0
I start tunnel using "sudo ifup tun0". Then everything is working for some time.
When it stops to work, I found out, that tunnel does not forward traffic from machine B to machine A, while traffic from machine A to machine B
is forwarded correctly. Network device tun0 on machine B just stops transmitting the data.
Also I noted, that it happens more frequently, while transmitting big amount of data.
Please, help me to fix that. It's really borring to restart tunnel so often.

Revision history for this message
Nicolas Valcarcel (nvalcarcel) wrote :

Does this bug is still present?

Revision history for this message
Oleksiy Kokachev (lelikv) wrote : Re: [Bug 185524] Re: ssh tunnel dies unexpectedly several times a day

yes. It's still there.
How can I resolve that?
Now I temporary switched to using ssh -L portforwarding (and it's
working good), because it's really frustrating
to restart tunnel 5-6 times a day.

On Tue, Feb 19, 2008 at 6:56 AM, Nicolas Valcárcel (nxvl)
<email address hidden> wrote:
> Does this bug is still present?
>
>
>
> --
> ssh tunnel dies unexpectedly several times a day
> https://bugs.launchpad.net/bugs/185524
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Rolf Leggewie (r0lf) wrote :

What kind of internet connection? DSL, dynIP?

Revision history for this message
Oleksiy Kokachev (lelikv) wrote :

Ethernet on both ends.
If I use port forwarding using -L option - connection does not die.
It happens only when I use ssh tunnel.

On Tue, Apr 22, 2008 at 12:03 AM, Rolf Leggewie
<email address hidden> wrote:
> What kind of internet connection? DSL, dynIP?
>
>
>
> --
> ssh tunnel dies unexpectedly several times a day
> https://bugs.launchpad.net/bugs/185524
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

You can use -vvv option to ssh to log more verbosely. Would be
interesting to capture the message that occur when your tunneled
connection breaks.

:-Dustin

Revision history for this message
Oleksiy Kokachev (lelikv) wrote :

Dear Dustin.
Thanks for note.
This happened in Gutsy. I'll check it in Hardy soon and I'll post here
messages from ssh with -vvv option.

On Wed, Apr 23, 2008 at 5:55 AM, Dustin Kirkland <email address hidden> wrote:
> You can use -vvv option to ssh to log more verbosely. Would be
> interesting to capture the message that occur when your tunneled
> connection breaks.
>
>
> :-Dustin
>
> --
>
>
> ssh tunnel dies unexpectedly several times a day
> https://bugs.launchpad.net/bugs/185524
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Tarnay Kálmán (tarnay-kalman) wrote :

It appears that it has something to do with the remote endpoint being an older version of openssh-server...
http://readlist.com/lists/openbsd.org/misc/12/62220.html

Revision history for this message
Tarnay Kálmán (tarnay-kalman) wrote :

Hardy->Etch - tunnel dies often...
Hardy->Hardy - all fine...

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thank you for updating this report frequently. I'll close it as wontfix now, edgy is no longer supported. I'm glad that you are seeing no trouble for hardy on both ends.

Changed in openssh:
status: New → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Oleksiy, please excuse me closing this ticket possibly prematurely. I was not aware that Kalman was not the original reporter.

You said you were still seeing this in gutsy which is still supported. Reopening the ticket and setting to incomplete to give you the chance for supplying the log as per comment 6.

Changed in openssh:
status: Won't Fix → Incomplete
Revision history for this message
ryan.catherman (ryan-cathermans) wrote :

I've seen the same behavior. For me, it was always gutsy on both ends, but I also see it with hardy on both ends. Same behavior as posted. After some time, for me usually either large amounts of consistent data or long periods of idle time, network dumping shows that traffic one direction stops working, but continues to work in the other direction.

I don't have any other data or logging to offer, but thought I'd chime in that I have seen it before and could never find anyone else who had posted the problem. I always assumed it was because most people are satisfied with -L support and don't take advantage of -w support.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

resetting to new. Will confirm once another report from hardy or later comes in.

Changed in openssh:
status: Incomplete → New
Revision history for this message
Jeff Enns (cyberpenguinks) wrote :

I'm just checking to see if this is still a problem. I noticed this hasn't been touched for a long time. Let me know if you are still having problems and I can try to help you out. Thank you.

Changed in openssh (Ubuntu):
status: New → Invalid
Revision history for this message
Colin Watson (cjwatson) wrote :

Jeff, please do not close bugs as Invalid for that reason. See https://wiki.ubuntu.com/Bugs/Status for what Invalid means.

Changed in openssh (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Oleksiy Kokachev (lelikv) wrote :

Dear Chuck.Almost 2 years have passed and now I'm on Jaunty and I don't use
tunnels anymore. When I reported this bug, I've done some research of the
problem and at that time I was ready to provide any information requested.
But now I cannot help anyhow to fix this bug.
Anyway, thanks for your effort.
If nobody else has the same problem, then I suppose it's reasonable to close
this bug.
Regards.

On Thu, Oct 15, 2009 at 1:57 AM, Chuck Short <email address hidden>wrote:

> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> --
> ssh tunnel dies unexpectedly several times a day
> https://bugs.launchpad.net/bugs/185524
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Chuck Short (zulcss)
Changed in openssh (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.