can't access some internet servers after upgrading client to ubuntu 11.10

Bug #894194 reported by James Crowther
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

I recently upgraded my ubuntu desktop pc from 11.04 to 11.10, upon completing the update I tried to ssh into one of my servers on the internet (a vps, its address is vps.p-s-e.tk) however I got the message 'no route to host'.

I then tested the connection by pinging the vps.p-s-e.tk and all pings came back perfectly not one packet lost, I then tried nmap

sudo nmap vps.p-s-e.tk which came back with the expected ports (including 22) marked as open

I then tried telneting to port 22 and got the same response 'Unable to connect to remote host: No route to host'
'
thinking this may have been a problem with just this pc I installed ubuntu 11.10 on a separate pc and with a fresh install got the exact same response

note, the access problem occurs for all attempts to connect to the server ie imap smtp http https etc

the client can connect to other servers / sites on the web ie google

(note I can still access/ ssh into the server (vps.p-s-e.tk) via other linux/windows/android pcs/devices on the same lan segment ie 10.6.111.*)

having searched around the web for a fix for this problem I came across a series of threads that in the end lead me to totally remove apparmor from the pc (I don't know why it had come back as I had totally removed it long before the update to 11.10)

however this did not solve the problem

also of note is that I host a web page off my home internet connection and it cant access that from the pc either, again nmap shows the port as open but nothing can seem to get to it ie telnet returns 'Unable to connect to remote host: No route to host'

-------------------

notes
the client pc address is 10.6.111.238
other pcs can ssh into the client pc (Im sshd in from my mac right now)
this problem affects all user accounts on the pc inc root
ipv6 has been disabled

---------------------
root@xr34lind2:/home/james# lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10
----------------------

root@xr34lind2:/home/james# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.6.111.254 0.0.0.0 UG 0 0 0 eth0
10.6.111.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0

----------------------
ping examples

root@xr34lind2:/home/james# ping vps.p-s-e.tk
PING vps.p-s-e.tk (98.126.57.67) 56(84) bytes of data.
64 bytes from 98.126.57.67.static.customer.krypt.com (98.126.57.67): icmp_req=1 ttl=54 time=140 ms
From brd4-vlan399.**************** (************): icmp_seq=2 Redirect Host(New nexthop: brd3-vlan399.************* (**********))

root@xr34lind2:/home/james# ping www.google.com
PING www.l.google.com (173.194.65.147) 56(84) bytes of data.
64 bytes from ee-in-f147.1e100.net (173.194.65.147): icmp_req=1 ttl=50 time=18.3 ms
From brd4-vlan399.*********** (**************): icmp_seq=2 Redirect Host(New nexthop: brd3-vlan399.****************(***********))

some parts redacted for security reasons

----------------------

examples

>>telneting google on port 80
james@xr34lind2:~$ telnet www.google.com 80
Trying 173.194.65.104...
Connected to www.l.google.com.
Escape character is '^]'.
^]

telnet> quit
Connection closed.

>>telneting my server on port 80
james@xr34lind2:~$ telnet vps.p-s-e.tk 80
Trying 98.126.57.67...
telnet: Unable to connect to remote host: No route to host

>>telneting my server on port 22
james@xr34lind2:~$ telnet vps.p-s-e.tk 22
Trying 98.126.57.67...
telnet: Unable to connect to remote host: No route to host

>>telneting one of my other linux boxes on the local (non internet lan, it still has several vlans to it ie 10.6.111.* 10.6.112.* etc)
james@xr34lind2:~$ telnet 10.6.111.230 22
Trying 10.6.111.230...
Connected to 10.6.111.230.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.5p1 Debian-4ubuntu4
^]

telnet> quit
Connection closed.

>>telneting one of the other boxes (in this case a network printer) on the local lan on port 80 (non internet lan, it still has several vlans to it ie 10.6.111.* 10.6.112.* etc)
james@xr34lind2:~$ telnet 10.6.112.243 80
Trying 10.6.112.243...
Connected to 10.6.112.243.
Escape character is '^]'.
^]

telnet> quit

Connection closed.

>>telneting my hosted web servise on port 80 (freewebs host this page set)
james@xr34lind2:~$ telnet www.p-s-e.tk 80
Trying 216.98.141.250...
Connected to wfb.zoneedit.com.
Escape character is '^]'.
^]

telnet> quit
Connection closed.

james@xr34lind2:~$

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/894194/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Please attach the log files contained in "/var/log/dist-upgrade/".

affects: ubuntu → update-manager (Ubuntu)
Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
James Crowther (j1aks) wrote :

as requested attached are the files you wanted

note these are the files from the system I updated from 11.04 to 11.10.

do you need the same files for the fresh install system that experienced the same problem (note this system had a static IP configured during the install process)?

also note, that I did some further tests and tried removing the the network settings completely and then re adding them

first as just a exact copy (ie re entering the settings via the network manager app as a static address) - this had no effect on the problem

then secondly I tried removing the settings and, via the network manager app, re adding the connection as a DHCP acquired one, this, after a reboot caused the problem to go away. I then tried putting the pc back on a static address and the problem remained gone (even after multipal reboots)

Changed in update-manager (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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