Sorry, been 'away' for a while, I tried a re-install of Fedora 7 to make sure I hadn't done anything wrong. This time I got it to believe I wanted a static IP address (there was a bit of the setup I hadn't noticed first time around) so it has done that right and all looks correct 'as installed' but I'm still getting exactly the same symptoms.

On Mon, Sep 24, 2007 at 01:01:35PM +0100, keith.jamieson@bt.com wrote:

What is your /etc/resolv.conf and /etc/nsswitch.conf files like?

[fedora@localhost ~]$ more /etc/resolv.conf nameserver 195.74.102.146 nameserver 195.74.102.147

and the uncommented parts of /etc/nsswitch.conf:-

passwd: files shadow: files group: files hosts: files dns

bootparams: nisplus [NOTFOUND=return] files

ethers: files netmasks: files networks: files protocols: files rpc: files services: files

netgroup: nisplus

Are they on FC anymore?

Can you go to 217.32.165.146 ( www.bt.com ) and get a web page?

Yes, the web sort of half works though it's a bit wierd. When I went to www.bt.com it produced the BT front page but if I navigate around to (for example) www.btplc.com it times out.

On 24-Sep-07 12:42:22, Brett Parker wrote:

On Mon, Sep 24, 2007 at 12:58:01PM +0100, Chris G wrote:

...

I can 'host xxx.yyy.zzz' and I get the right IP address back for
whatever I've asked for.

I can't ssh, ftp or anything to anywhere outside my local subnet.

All other systems on the subnet *can* talk various protocols to the outside world. The Fedora system can talk various protocols to other systems on the same subnet.

So can anyone offer any insight, I'm at the swearing at it stage!

I assume that the DNS in /etc/resolv.conf is pointing to a local caching proxy, so host and dig will work...

My guess is that you haven't got a default gateway set, so it doesn't know where to send packets to for the outside...

You can tell by running: /sbin/route -n

If you haven't got an entry with a Destination of 0.0.0.0 then you haven't set the default gateway, set that to the correct router and you should be ok.

That's what I was suspecting too! If (as you wrote earlier, Chris) your system had been getting its IPs by DHCP, it will probably have been setting the default route (and/or DNS)by DHCP as well. It may still be doing this. If that's the case, then you may have the kind of problem I've encountered in this sort of situation.

Specifically, I have a BT ADSL modem/router connected to my phone line. This has IP address 192.168.1.1 on my LAN. This is the default route for my machines.

Immediately on the LAN side of this, doing duty as a hub (because I had it to hand ... ) is another router (this time a cable modem router) whose WAN-side ethernet cable plugs into the BT router. This works fine as a hub.

But, of course, it's also a router in ite innermost soul, and as such it has IP address 192.168.2.254.

What I've found lately (playing with sundry Linux live DVDs, which use DHCP when they initally run) is that sometimes I get a default route set up by DHCP to where it ought to be (namely 192.168.1.1), and sometimes where it ought not to be (192.168.1.254). In some cases I can get it swapping between on and the other on successive boots using the same Linux Live DVD! (I suspect it's due to which ever "gets in first").

Of course, I configure my "real" machines to use static IPs, and I tell them what to use. So they're all set up to make the default route 192.168.1.1.

And similar things go for the DNS IP addresses -- when found by DHCP, sometimes they're right (i.e. the BT router gives them out) and sometimes they're wrong. So of course the file /etc/resolv.conf is edited accordingly on my real machines.

But, when I run a live DVD, often the first ting I have to do is delete the wrong default route and add the right one, and/or edit /etc/resolv.conf to get that right too.

Just a bit of anecdote that may possibly fit your situation. If your fedora box is still picking up the default route and/or the DSN by DHCP, then it may be getting them from somewhere you didn't expect!

So, when your Fedora box is running but not connecting properly to the outside world, have a look at the output of

route

cat /etc/resolv.conf

and see if they're what they should be.

Hoping this helps, Ted.

-------------------------------------------------------------------- E-Mail: (Ted Harding) ted.harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 24-Sep-07 Time: 14:31:10 ------------------------------ XFMail ------------------------------

On 24-Sep-07 13:52:38, Tim Green wrote:

On 9/24/07, Ted Harding ted.harding@nessie.mcc.ac.uk wrote:

...

What I've found lately (playing with sundry Linux live DVDs, which use DHCP when they initally run) is that sometimes I get a default route set up by DHCP to where it ought to be (namely 192.168.1.1), and sometimes where it ought not to be (192.168.1.254). In some cases I can get it swapping between on and the other on successive boots using the same Linux Live DVD! (I suspect it's due to which ever "gets in first").

Sounds like you have two DHCP servers on the same physical network. This is bad, of course.

Tim.

Agreed in principle -- but, since I've always configured my "real" machines to have fixed IPs throughout, and never use DHCP, it doesn't matter normally. It was only when I suck it & see with the DVDs that intitally use DHCP that it has en effect!

Best wishes, Ted.

-------------------------------------------------------------------- E-Mail: (Ted Harding) ted.harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 24-Sep-07 Time: 15:10:19 ------------------------------ XFMail ------------------------------