Results of ifconfig eth0: eth0 Link encap:Ethernet HWaddr 00:13:20:62:47:D4 inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::213:20ff:fe62:47d4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:70 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5320 (5.1KiB) TX bytes:6399 (6.2 KiB)
and route gives: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 cat /etc/resolv.conf: nameserver 10.1.1.1 traceroute: bash: traceroute: command not found cheers Matt > I stand by the config I posted earlier. > > Also, the manner of the problem you have reported could still be explained > by misconfiguration in Firefox. Is is possible that Firefox is attempting > to contact a Proxy server? > > If you follow the instructions in my previous email then we can at least > eliminate or prove some simple network problems. > > Regards, > Michael. > > On Wed, May 09, 2007 at 05:35:17PM +1200, Matthew Whiting wrote: >> Before applying any of your suggestions after trying a few things my >> /etc/network/interfaces file now contains the following. How should I >> proceed to edit this? >> ------------------- >> auto lo >> iface lo inet loopback >> >> mapping hotplug >> script grep >> map eth0 >> >> iface dsl-provider inet ppp >> provider dsl-provider >> >> iface eth0 inet dhcp >> >> auto eth0 >> ------------------- >> >> > On Wed, May 09, 2007 at 12:47:07PM +1200, Nick Rout wrote: >> >> >> >> On Wed, May 9, 2007 12:38 pm, Matthew Whiting wrote: >> >> >>> connecting fine using this apple iBook. No such luck with my >> desktop >> >> >>> pc.. >> >> >>> Its an xtra broadband connection and my machine is connected >> >> physically >> >> >>> to >> >> >>> a port on a linksys wireless router which is connected to a >> d-link >> >> adsl >> >> >>> router. What would be appropriate diagnostic tools to use to suss >> >> out >> >> >>> what >> >> >>> is happening? Firefox tries to connect and times out. I'm not >> >> familiar >> >> >>> enough with linux network admin tools to better determine the >> >> problem.. >> >> > >> >> >> What is the output of >> >> >> ifconfig -a >> >> >> route -n >> >> >> cat /etc/resolv.conf >> >> > >> >> > ifconfig gives a bunch of details for eth0, lo and sit0. not sure >> what >> >> to >> >> > look for here? >> >> >> >> I was looking for the output in relation to eth0, which is the forst >> >> ethernet device. Posting the output of the command would have been >> fine. >> >> >> >> > route -n gives: >> >> > Destination Gateway Genmask Flags Metric Ref Use >> >> Iface >> >> > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth0 >> >> > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 >> eth0 >> >> > >> >> >> >> Weirdly there is no 127. route, but otherwise looks fine. >> > >> > Can't remember ever seeing 127.0.0.1 in a "route -n". Maybe you're >> > thinking of "route -nC" Nick. >> > >> > Anyway, the absence of 127.0.0.0 is not important here. >> > >> >> >> >> > cat /etc/resolve.conf gives: >> >> > nameserver 10.1.1.1 >> >> > >> >> > >> >> >> >> clearly wrong, your dns server won't be 10.1.1.1. >> > >> > Not *clearly* wrong since the Linksys maybe issuing another one of its >> > private IP interfaces as the DNS server address. But yes, 192.168.1.1 >> is >> > likely to be a better bet. The PC can get to it because it's only got >> one >> > default route - via 192.168.1.1 as it happens! >> > >> >> >> >> Try changing this to 192.168.1.1 (if the router provides dns >> services) >> >> or >> >> the ip address of your isp's dns server if it doesn't. >> > >> > If that doesn't work, try changing /etc/network/interfaces as such: >> > >> > --- Snip here >> > auto lo eth0 >> > iface lo inet loopback >> > >> > iface eth0 inet dhcp >> > >> > mapping hotplug >> > script grep >> > map eth0 >> > >> > iface dsl-provider inet ppp >> > provider dsl-provider >> > >> > iface ppp0 inet ppp >> > provider ppp0 >> > --- Cut here >> > >> > Then do "ifdown eth0" and then "ifup eth0". >> > >> > Then do: >> > >> > host www.google.co.nz >> > arp -a >> > ifconfig eth0 >> > route >> > >> > By the way, do you have a link light on your network card and on your >> > Linksys? >> > >> > Regards, >> > Michael. >> > >> >> >
