On Thu, Oct 05, 2006 at 10:58:50PM +0100, Jonathan McDowell wrote:
On Thu, Oct 05, 2006 at 10:46:29PM +0100, cl@isbd.net wrote:
I'm playing with a Suse 10.2 installation on my new hardware. It's all basically working locally but routing/DNS is broken.
I can traceroute to anywhere, I can ping anywhere but I can't actually communicate with anywhere - i.e. I can't connect Firefox to any web sites and I can't ssh to anywhere.
So what's set up wrong? /etc/resolv.conf has the right things in it (same as my other system anyway) and the default gateway is the same as my other system. I'm stumped.
You say routing/DNS is broken, but if you can traceroute/ping then routing sounds fine.
Well yes, I sort of realised that, but *something* is awry with routing as I have no useful internet access at all.
Are you tracerouting/pinging an IP or a hostname?
A hostname. E.g. I can 'traceroute shell.x-1.net' and I can 'ping shell.x-1.net' but I can't 'ssh shell.x-1.net'. The ssh just hangs for ever.
If an IP, can you ssh to an IP address?
No, I tried that anyway, ssh to an IP address just fails too.
Do you have any firewalling rules?
Possibly, but this is what I hate about modern distributions, it's all buried in the depths of GUI configuration utilities somewhere. I did try 'firewall off' in yast2 but that seemed to have no effect.
As you say it's not really a DNS problem, it's some sort of routing issue I think.
Do ping and traceroute use UDP? If so it would seem that UDP is working OK but that TCP isn't.