Re: [ubuntu-uk] ADSL problem

2006-12-21 Thread Tristan Wibberley
On Sat, 2006-12-16 at 20:02 +, Dave Briggs wrote:
> OK...
> 
> 1. [EMAIL PROTECTED]:~$ host www.ubuntu.com
> www.ubuntu.com has address 82.211.81.166
> ;; Warning: Message parser reports malformed message packet.
> 
> 2. [EMAIL PROTECTED]:~$ cat /etc/resolv.conf
> nameserver 192.168.1.1 [ie my modem's ip]
> 
> 3. [EMAIL PROTECTED]:~$ cat /etc/resolv.conf
> nameserver 192.168.1.1
> nameserver 62.241.162.200
> nameserver 62.241.163.200 [I added the primary and secondary DNS
> provided by my isp]
> 
> Tried the web again after adding these, and still no joy :-(

I see you've had no answer to this, can you confirm that David Pashley's
earlier steps worked as described? You didn't say whether you followed
them as suggested:

ip route
ping 
ping 82.211.81.166

-- 
Tristan Wibberley

Any opinion expressed is mine (or else I'm playing devils advocate for
the sake of a good argument). My employer had nothing to do with this
communication.



-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Tony Arnold
Dave,

Dave Briggs wrote:
> On 16/12/06, Toby Smithe <[EMAIL PROTECTED]> wrote:
>> It looks like your router is at 192.168.1.1
>>
>> Go there in a web browser, and see what the router console says.
> 
> Hi Toby. Yep, that's right. Have already got the settings sorted as
> per Pipex's instructions. It's all working from Windows, so I don't
> think there is a problem there.

Could be a dns problem. Try ping'ing a known IP address from a terminal
window. www.ubuntu.com translates to 82.211.81.166, so try:

ping 82.211.81.166

If that works, then try:

ping www.ubuntu.com

and if that doesn't work you have a dns problem. Check out contents of
/etc/resolv.conf and then see if the addresses of the name servers are
reachable via ping.

Regards,
Tony.
> 

-- 
Tony Arnold, IT Security Coordinator, University of Manchester,
IT Services Division, Kilburn Building, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E: [EMAIL PROTECTED], H: http://www.man.ac.uk/Tony.Arnold

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
OK...

1. [EMAIL PROTECTED]:~$ host www.ubuntu.com
www.ubuntu.com has address 82.211.81.166
;; Warning: Message parser reports malformed message packet.

2. [EMAIL PROTECTED]:~$ cat /etc/resolv.conf
nameserver 192.168.1.1 [ie my modem's ip]

3. [EMAIL PROTECTED]:~$ cat /etc/resolv.conf
nameserver 192.168.1.1
nameserver 62.241.162.200
nameserver 62.241.163.200 [I added the primary and secondary DNS
provided by my isp]

Tried the web again after adding these, and still no joy :-(

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread David Pashley
On Dec 16, 2006 at 16:07, Dave Briggs praised the llamas by saying:
> On 16/12/06, David Pashley <[EMAIL PROTECTED]> wrote:
> 
> > Run "ip link"
> 
> OK:
> 
> [EMAIL PROTECTED]:~$ ip link
> 1: lo:  mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
> 3: sit0:  mtu 1480 qdisc noop
> link/sit 0.0.0.0 brd 0.0.0.0
> 
> > "ip addr show dev eth0"
> > The line you're interested in here is the line that starts inet. If you
> > don't or it starts 169.254 then you don't have an ip address assigned.
> 
> [EMAIL PROTECTED]:~$ ip addr show dev eth0
> 2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
> inet6 fe80::213:d3ff:fecd:a6fa/64 scope link
>valid_lft forever preferred_lft forever
> 
> 
> Think that's all ok on the network front. What should I check next?
> 
> Thanks for all this help.

So we've been given an IP address from somewhere. Let's see if they have
given us a default route. We can do this by running "ip route"

mojo-jojo david% ip route
10.187.182.224/27 dev eth0  proto kernel  scope link  src 10.187.182.233 
default via 10.187.182.225 dev eth0 

>From this we can see that our default route is to 10.187.182.225 using
eth0 network device. Lets try pinging that:

mojo-jojo david% ping 10.187.182.225
PING 10.187.182.225 (10.187.182.225) 56(84) bytes of data.
64 bytes from 10.187.182.225: icmp_seq=1 ttl=64 time=0.317 ms
64 bytes from 10.187.182.225: icmp_seq=2 ttl=64 time=0.291 ms
64 bytes from 10.187.182.225: icmp_seq=3 ttl=64 time=0.224 ms

--- 81.187.182.226 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.224/0.277/0.317/0.041 ms

So we know we can at least reach the router.

Now, lets see if we can get any further than this. Lets try pinging
Ubuntu's webserver.

mojo-jojo david% ping 82.211.81.166
PING 82.211.81.166 (82.211.81.166) 56(84) bytes of data.
64 bytes from 82.211.81.166: icmp_seq=1 ttl=52 time=30.5 ms
64 bytes from 82.211.81.166: icmp_seq=2 ttl=52 time=30.8 ms
64 bytes from 82.211.81.166: icmp_seq=3 ttl=52 time=30.2 ms

--- 82.211.81.166 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 30.232/30.532/30.836/0.318 ms

If this works, then we have working networking and can move on to
checking DNS.

If this doesn't work, we need to find out where the problem lies using
mtr (I'd normally suggest traceroute here, but it doesn't look like it's
a part of the standard Ubuntu install). We will trace the route to
ubuntu's webserver again.

mojo-jojo david% mtr -r -c 1  82.211.81.166
HOST: mojo-jojo   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. brian.catnip.org.uk   0.0% 10.4   0.4   0.4   0.4   0.0
  2. 10.187.182.2010.0% 11.1   1.1   1.1   1.1   0.0
  3. careless.aaisp.net.uk 0.0% 1   30.2  30.2  30.2  30.2   0.0
  4. needless.aaisp.net.uk 0.0% 1   28.7  28.7  28.7  28.7   0.0
  5. ge-2-0-216.ipcolo2.London1.L  0.0% 1   30.2  30.2  30.2  30.2   0.0
  6. ae-0-55.bbr1.London1.Level3.  0.0% 1   30.2  30.2  30.2  30.2   0.0
  7. as-0-0.bbr2.London2.Level3.n  0.0% 1   30.3  30.3  30.3  30.3   0.0
  8. ge-3-0-0-55.gar1.London2.Lev  0.0% 1   30.2  30.2  30.2  30.2   0.0
  9. 195.50.91.146 0.0% 1   30.4  30.4  30.4  30.4   0.0
 10. vlan102.core-l-1.lon2.mnet.n  0.0% 1   29.6  29.6  29.6  29.6   0.0
 11. 85.133.32.130 0.0% 1   31.7  31.7  31.7  31.7   0.0
 12. 82.211.81.76  0.0% 1   30.0  30.0  30.0  30.0   0.0
 13. signey.ubuntu.com 0.0% 1   29.9  29.9  29.9  29.9   0.0

This shows us every router between us and the remote machine. The first
line will show your ADSL router. The line after that will be the remote
end of your ADSL line. If your adsl is not connected you won't be able
to reach the second hop. Anything beyond this is nothing you can
control, but considering it works in Windows it's unlikely that this is
the case.

There is another possibility why you can't reach the second hop and that
is that the default route isn't correct, but this address should have
been given to you via DHCP like your IP address.

If this is all working, we can check DNS.

Try looking up a host by name using the host command:

mojo-jojo david% host www.ubuntu.com
www.ubuntu.com has address 82.211.81.166

If this works, then your networking should be working fine. If not, then
we need to check /etc/resolv.conf. It should look something like:

mojo-jojo david% cat /etc/resolv.conf 
nameserver 10.187.182.226
nameserver 10.187.182.229

Here we list DNS name servers. You should edit this file to use the name
servers that you were given by your ISP.



> 

-- 
David Pashley
[E

Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Toby Smithe
Can you ping the router? Can you ping the ISP's router or DNS server?
If so, can you ping a host name (eg www.google.co.uk)? Or can you ping
stuff, but only stuff that's on the local net? What's the output of the
"ip route" command?

On Sat, 2006-12-16 at 16:12 +, Dave Briggs wrote:
> On 16/12/06, Toby Smithe <[EMAIL PROTECTED]> wrote:
> > It looks like your router is at 192.168.1.1
> >
> > Go there in a web browser, and see what the router console says.
> 
> Hi Toby. Yep, that's right. Have already got the settings sorted as
> per Pipex's instructions. It's all working from Windows, so I don't
> think there is a problem there.
> 
> -- 
> Dave Briggs
> 
-- 
Help me get to Venezuela!
http://tibsplace.co.uk/venezuela

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
On 16/12/06, Toby Smithe <[EMAIL PROTECTED]> wrote:
> It looks like your router is at 192.168.1.1
>
> Go there in a web browser, and see what the router console says.

Hi Toby. Yep, that's right. Have already got the settings sorted as
per Pipex's instructions. It's all working from Windows, so I don't
think there is a problem there.

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Toby Smithe
It looks like your router is at 192.168.1.1

Go there in a web browser, and see what the router console says.

On Sat, 2006-12-16 at 16:07 +, Dave Briggs wrote:
> On 16/12/06, David Pashley <[EMAIL PROTECTED]> wrote:
> 
> > Run "ip link"
> 
> OK:
> 
> [EMAIL PROTECTED]:~$ ip link
> 1: lo:  mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
> 3: sit0:  mtu 1480 qdisc noop
> link/sit 0.0.0.0 brd 0.0.0.0
> 
> > "ip addr show dev eth0"
> > The line you're interested in here is the line that starts inet. If you
> > don't or it starts 169.254 then you don't have an ip address assigned.
> 
> [EMAIL PROTECTED]:~$ ip addr show dev eth0
> 2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
> inet6 fe80::213:d3ff:fecd:a6fa/64 scope link
>valid_lft forever preferred_lft forever
> 
> 
> Think that's all ok on the network front. What should I check next?
> 
> Thanks for all this help.
> 
> -- 
> Dave Briggs
> 
-- 
Help me get to Venezuela!
http://tibsplace.co.uk/venezuela

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
On 16/12/06, David Pashley <[EMAIL PROTECTED]> wrote:

> Run "ip link"

OK:

[EMAIL PROTECTED]:~$ ip link
1: lo:  mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
3: sit0:  mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0

> "ip addr show dev eth0"
> The line you're interested in here is the line that starts inet. If you
> don't or it starts 169.254 then you don't have an ip address assigned.

[EMAIL PROTECTED]:~$ ip addr show dev eth0
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:13:d3:cd:a6:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
inet6 fe80::213:d3ff:fecd:a6fa/64 scope link
   valid_lft forever preferred_lft forever


Think that's all ok on the network front. What should I check next?

Thanks for all this help.

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
On 16/12/06, Alan Pope <[EMAIL PROTECTED]> wrote:

> The HantsLUG wiki [0] has a nice network diags page [1] which might be
> useful.

Cheers all. Am logging out of here and going into Ubuntu to run
through David P's list of things. Back in a bit!

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Alan Pope
On Sat, 2006-12-16 at 15:22 +, Dave Briggs wrote:
> To get the Windows side working, I had to ring the Pipex help desk and
> they gave me some DOS commands to run to clear out the TCP/IP things,
> I think they said. This got that side of things working.
> 
> Any ideas? Might ppoeconfig be required?
> 

Unlikely in this country I think.

The HantsLUG wiki [0] has a nice network diags page [1] which might be
useful.

Cheers,
Al.

[0] - http://hants.lug.org.uk/
[1] -
http://hants.lug.org.uk/cgi-bin/wiki.pl?LinuxHints/NetworkDiagnostics




-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread David Pashley
On Dec 16, 2006 at 15:22, Dave Briggs praised the llamas by saying:
> On 16/12/06, Richard Downing <[EMAIL PROTECTED]> wrote:
> 
> > Is the link encrypted?  Do you need a License Registration Server
> > process running?  Did you load the driver?
> 
> No to the first one, it was bbc.co.uk. I am using a Linksys ADSL2
> modem, connected to my ethernet, if that helps for the othr two.

I presume this is connected via an ethernet cable to your workstation
and isn't using wireless.
> 
> > When you say 'Nothing Happens', do you mean that you just see a blank
> > page and 'done', or it there a timeout on the dns lookup?
> 
> Blank page. Status bar says 'Connecting to...' but nothing happens. I
> have left it for quite a while without it timing out.
> 
The first thing to do is check that your network card has been detected. 

Run "ip link"

mojo-jojo david% ip link
1: lo:  mtu 16436 qdisc noqueue 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:a0:c9:92:9c:c0 brd ff:ff:ff:ff:ff:ff
3: sit0:  mtu 1480 qdisc noop 
link/sit 0.0.0.0 brd 0.0.0.0

You should see eth0. If this is the case, then your network card was
detected correctly. The next thing to do is to check that you have got
an IP address for that network device. You can do that by running "ip
addr show dev eth0"

2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:a0:c9:92:9c:c0 brd ff:ff:ff:ff:ff:ff
inet 10.187.182.233/27 brd 10.187.182.255 scope global eth0
inet6 2002:8b0:ed:2:2a0:c9ff:fe92:9cc0/64 scope global dynamic 
   valid_lft 2591991sec preferred_lft 604791sec
inet6 fe80::2a0:c9ff:fe92:9cc0/64 scope link 
   valid_lft forever preferred_lft forever

The line you're interested in here is the line that starts inet. If you
don't or it starts 169.254 then you don't have an ip address assigned.

You can either get this dynamically via something called DHCP, or you
can configure it statically. We'll try dhcp first by running "sudo
dhclient eth0"

mojo-jojo david% sudo dhclient eth0
Password:
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:a0:c9:92:9c:c0
Sending on   LPF/eth0/00:a0:c9:92:9c:c0
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 10.187.182.226
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.187.182.226
bound to 10.187.182.233 -- renewal in 38436 seconds.

If you keep seeing DHCPDISCOVER lines over and over, then it means your
router is not providing addresses via DHCP, although I find this quite
unlikely.

If you repeat the "ip addr show eth0" line again you should see that you
now have a new "inet" line.

Lets see if our networking is working. Let's ping the machine that gave
us an IP address. If you take the IP address from the DHCPOFFER line and
try to ping it using "ping ". Press Ctrl-C to stop it.

mojo-jojo david% ping 10.187.182.226
PING 10.187.182.226 (10.187.182.226) 56(84) bytes of data.
64 bytes from 10.187.182.226: icmp_seq=1 ttl=64 time=0.364 ms
64 bytes from 10.187.182.226: icmp_seq=2 ttl=64 time=0.274 ms
64 bytes from 10.187.182.226: icmp_seq=3 ttl=64 time=0.286 ms

--- 10.187.182.226 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 0.274/0.308/0.364/0.039 ms

If you get lines like this, then you have working IP networking. I'll
let you work thought this email before we move onto dealing with routing
and DNS.

-- 
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
On 16/12/06, Richard Downing <[EMAIL PROTECTED]> wrote:

> Is the link encrypted?  Do you need a License Registration Server
> process running?  Did you load the driver?

No to the first one, it was bbc.co.uk. I am using a Linksys ADSL2
modem, connected to my ethernet, if that helps for the othr two.

> When you say 'Nothing Happens', do you mean that you just see a blank
> page and 'done', or it there a timeout on the dns lookup?

Blank page. Status bar says 'Connecting to...' but nothing happens. I
have left it for quite a while without it timing out.

To get the Windows side working, I had to ring the Pipex help desk and
they gave me some DOS commands to run to clear out the TCP/IP things,
I think they said. This got that side of things working.

Any ideas? Might ppoeconfig be required?

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread baza
On Sat, 2006-12-16 at 15:05 +, Richard Downing wrote:
> Dave Briggs wrote:
> > Hi list
> > 
> > Just got my broadband live, and there's a bit of a problem with it.
> > Basically, I have got all my settings right in the modem interface,
> > and it is working fine in my windows partition.
> > 
> > But in Ubuntu, I boot up Firefox, try and load a webpage, and...
> > nothing happens.
> > 
> > Can anyone give me any clues on what might be wrong?
> > 
> > Cheers
> > 
> 
> 
> Is the link encrypted?  Do you need a License Registration Server
> process running?  Did you load the driver?
> 
> When you say 'Nothing Happens', do you mean that you just see a blank
> page and 'done', or it there a timeout on the dns lookup?
> 
> This is a BIG question - it took me three days to get my mate's Linux to
> work with WiFi.  Regrettably it isn't something that can be easily
> explained either.  This is one of the areas where Linux isn't plug and
> play, whereas Windows is.
> 

Are you using a USB type modem? There are a few steps you need to follow
to get these up and running. Check the forum and wiki.

Linux is not that tricky to get working with wifi, you just need to
check that the hardware is supported.

Baz

-- 
+++
http://walkertopia.com/blog

Cock, lock and ready to rock!
+++



-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


Re: [ubuntu-uk] ADSL problem

2006-12-16 Thread Richard Downing
Dave Briggs wrote:
> Hi list
> 
> Just got my broadband live, and there's a bit of a problem with it.
> Basically, I have got all my settings right in the modem interface,
> and it is working fine in my windows partition.
> 
> But in Ubuntu, I boot up Firefox, try and load a webpage, and...
> nothing happens.
> 
> Can anyone give me any clues on what might be wrong?
> 
> Cheers
> 


Is the link encrypted?  Do you need a License Registration Server
process running?  Did you load the driver?

When you say 'Nothing Happens', do you mean that you just see a blank
page and 'done', or it there a timeout on the dns lookup?

This is a BIG question - it took me three days to get my mate's Linux to
work with WiFi.  Regrettably it isn't something that can be easily
explained either.  This is one of the areas where Linux isn't plug and
play, whereas Windows is.

R.


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/


[ubuntu-uk] ADSL problem

2006-12-16 Thread Dave Briggs
Hi list

Just got my broadband live, and there's a bit of a problem with it.
Basically, I have got all my settings right in the modem interface,
and it is working fine in my windows partition.

But in Ubuntu, I boot up Firefox, try and load a webpage, and...
nothing happens.

Can anyone give me any clues on what might be wrong?

Cheers

-- 
Dave Briggs

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/