Internet problem - Ubuntu

Hi all, my apologies but I also posted this on alt.os.linux before
realizing this was probably a better place...

I've just installed Ubuntu 6.10 and I'm trying to get the internet up
and running. My pc has a Netgear WG311v3 Wireless PCI card. I have
installed the windoes drivers using ndiswrapper and everything seems
to be working fine. I can login to the router at http://10.1.1.1 and
see my linux box as a connected DHCP client through firefox and I can
even successfully ping addresses like www.google.com.

However, when I try to navigate firefox to any web address, i get no
action. I just sits there for ages before eventually timing out.

Here is the output from "sudo iwconfig wlan0"
wlan0 IEEE 802.11g ESSID:"Jane_Is_Great"
Mode:Managed Frequency:2.437 GHz Access Point:
00:11:95:95:FA:8C
Bit Rate:54 Mb/s Sensitivity=-200 dBm
RTS thr:2346 B Fragment thr:2346 B
Encryption key:4321-0812-22 Security mode:restricted
Power Managementff
Link Quality:100/100 Signal level:-71 dBm Noise level:-256
dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

and here is the output from "sudo ifconfig wlan0"
wlan0 Link encap:Ethernet HWaddr 00:0F:B5:85:A0:61
inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::20f:b5ff:fe85:a061/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1622 (1.5 KiB) TX bytes:1818 (1.7 KiB)
Interrupt:209 Memory:ee010000-ee020000

Any ideas why everything exceopt actually using a browser to see the
internet seems to be working??

Thanks....

On Sun, 08 Apr 2007 03:30:28 -0700, joshdotwhite rearranged some electrons
to form:


> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0

You are getting errors, too.

--
David M (dmacchiarolo)
http://home.triad.rr.com/redsled
T/S 53
sled351 Linux 2.4.18-14 has been up 6 days 13:44

David M wrote:
> On Sun, 08 Apr 2007 03:30:28 -0700, joshdotwhite rearranged some electrons
> to form:
>
>
>> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
>
> You are getting errors, too.
>

What errors? The ":" is between the label and the count. There are 0's for all the error counts.

Are you running a firewall? I cannot ATM think of anything else. The fact that you can ping
www.google.com indicates that DNS and routing are working.

Do you get any ping errors? Have you tried the -s option to get packets that are more
real-world-like? My personal test is with 'ping -s 1500 -c 20 www.samba.org'.

Larry

(E-Mail Removed) wrote:
>I've just installed Ubuntu 6.10 and I'm trying to get the internet up
>and running. My pc has a Netgear WG311v3 Wireless PCI card. I have
>installed the windoes drivers using ndiswrapper and everything seems
>to be working fine. I can login to the router at http://10.1.1.1 and
>see my linux box as a connected DHCP client through firefox and I can
>even successfully ping addresses like www.google.com.

I'm assuming that you mean you can ping google.com from your linux
box (as opposed to from the router).

>However, when I try to navigate firefox to any web address, i get no
>action. I just sits there for ages before eventually timing out.

If you can ping google, then you do have basic connectivity. A
data packet can get from your box to the Internet and a reply can
come back.

Perhaps the place to look to see what happens to HTTP packets is
your firewall configuration.

>Here is the output from "sudo iwconfig wlan0"
>wlan0 IEEE 802.11g ESSID:"Jane_Is_Great"
> Mode:Managed Frequency:2.437 GHz Access Point:
>00:11:95:95:FA:8C
> Bit Rate:54 Mb/s Sensitivity=-200 dBm
> RTS thr:2346 B Fragment thr:2346 B
> Encryption key:4321-0812-22 Security mode:restricted
> Power Managementff
> Link Quality:100/100 Signal level:-71 dBm Noise level:-256
>dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0


That looks fine. You have an 802.11g (54Mb/s) connection, and with
a signal level of -71 dBm you've got maybe a 10 dB fade margin to
work with.

>and here is the output from "sudo ifconfig wlan0"
>wlan0 Link encap:Ethernet HWaddr 00:0F:B5:85:A0:61
> inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.0.0.0
> inet6 addr: fe80::20f:b5ff:fe85:a061/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1622 (1.5 KiB) TX bytes:1818 (1.7 KiB)
> Interrupt:209 Memory:ee010000-ee020000

That looks fine too. No errors showing, but you'd only run a few
packets of data at that point, so it probably doesn't mean much
other than it basically does work.

>Any ideas why everything exceopt actually using a browser to see the
>internet seems to be working??

When you /ping/ another node the data is sent using ICMP (control)
packets. You might also try using /traceroute/, which sends UDP
(datagram) packets, just to see if there is a different result.
That would be another indication that your firewall is getting
in the way.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)

On Sun, 08 Apr 2007 14:26:58 +0000, Larry Finger rearranged some electrons
to form:

> David M wrote:
>> On Sun, 08 Apr 2007 03:30:28 -0700, joshdotwhite rearranged some electrons
>> to form:
>>
>>
>>> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
>>
>> You are getting errors, too.
>>
>
> What errors? The ":" is between the label and the count. There are 0's for all the error counts.

Oops, yes, you are correct. My mistake.



--
David M (dmacchiarolo)
http://home.triad.rr.com/redsled
T/S 53
sled351 Linux 2.4.18-14 has been up 6 days 20:35

On 8 Apr 2007, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, (E-Mail Removed)
wrote:

>my apologies but I also posted this on alt.os.linux before
>realizing this was probably a better place...

Perhaps - even though alt.os.linux sees about a third more traffic (and
substantially more trolling).

>I can login to the router at http://10.1.1.1 and see my linux box as a
>connected DHCP client through firefox and I can even successfully ping
>addresses like www.google.com.

OK - sounds as if networking is alive

>However, when I try to navigate firefox to any web address, i get no
>action. I just sits there for ages before eventually timing out.

It really helps to look under the hood, and not just be looking at the
pretty pictures. 'tcpdump' or 'wireshark' (the former 'ethereal') may
show the problem.

>Here is the output from "sudo iwconfig wlan0"
>wlan0 IEEE 802.11g ESSID:"Jane_Is_Great"

I'm sure that Jane appreciates that sentiment, and am glad you've
changed the default settings - hopefully you are using a secure
authentication scheme (WEP can be cracked in seconds - literally, so
WPA-PSK is highly desirable).

> Mode:Managed Frequency:2.437 GHz Access Point: 00:11:95:95:FA:8C

OK

> Bit Rate:54 Mb/s Sensitivity=-200 dBm

The sensitivity number is totally bogus

> Encryption key:4321-0812-22 Security mode:restricted

Now go change the encryption key to something a hell of a lot more
robust. Because you don't have to remember the key, you could use
something like

[compton ~]$ head -2 /dev/random | mimencode
ETx/fXyDXuhL1IPMKomxiVl3WEwGrNs97hgBQnBFov0h/ww4eyJgMPvsCh86hUNexOPn3XmV
cvw71zezY/CU/D6AJGOd5LYDuy2YqNd9Rf6eCg==
[compton ~]$

pick twenty or more character out of something like that.

> Link Quality:100/100 Signal level:-71 dBm Noise level:-256 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Noise level is also bogus - signal level not very good if real

>wlan0 Link encap:Ethernet HWaddr 00:0F:B5:85:A0:61
> inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.0.0.0
> inet6 addr: fe80::20f:b5ff:fe85:a061/64 Scope:Link

Do you know that you need IPv6? Do you know that your upstream can
handle this and any IPv6 name queries correctly? Oz only has about 26
IPv6 blocks (compared to 5519 IPv4 blocks), and this _frequently_
causes grief when the name server doesn't respond to AAAA querues
correctly.

> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

If you are on a PPPoE connection (only), you may want to try dropping
that MTU to 1492 and checking that any firewall on the DLink router is
not blocking ICMP Type 4 Code 4 (Fragmentation needed, but don't
fragment bit set) - a very well documented problem.

>Any ideas why everything except actually using a browser to see the
>internet seems to be working??

Networking appears alive, as does some elements of name resolution, and
ICMP pings. My next step would be to fire up a packet sniffer to see
if IPv6 is causing grief, then using a tool OTHER THAN A BROWSER works.
For example, try to use the command line version of ftp to connect to
an FTP server (Oz... ok, try ftp.planetmirror.com 203.16.234.85 or
203.16.234.86 - look in /pub/ibiblio/ which is a mirror of the sunsite
archive). Browsers - especially the "let me help you" kind like
firefox - have their own setups because they obviously know more about
networking than the kernel, and that often trips users. Badly.

Old guy

On Sun, 08 Apr 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <SY6Sh.265617$(E-Mail Removed)>,
Larry Finger wrote:

>Are you running a firewall? I cannot ATM think of anything else. The
>fact that you can ping www.google.com indicates that DNS and routing
>are working.

but his post also showed he has IPv6 running, which is frequently a
problem. I usually like to see a simple tcpdump before jumping to
any conclusions.

>Do you get any ping errors? Have you tried the -s option to get packets
>that are more real-world-like? My personal test is with
>'ping -s 1500 -c 20 www.samba.org'.

Please don't be beating on some computer you don't control. If you
suspect a networking problem, five or ten pings are going to tell you
as much as twenty, and won't be _as_ abusive. Also remember that
ping (ICMP Echo) has less realism than actually downloading a file
from the server using TCP. Some administrators routinely block ping
or assign it a lower priority at the router because it is less
important for getting the data to the customer. Mere;y looking at the
IP and TCP headers (specifically the sequence numbers) will often
tell more about a connection than any amount of pinging.

Old guy

On Apr 8, 6:30 pm, joshdotwh...@gmail.com wrote:
> Hi all, my apologies but I also posted this on alt.os.linux before
> realizing this was probably a better place...
>
> I've just installed Ubuntu 6.10 and I'm trying to get the internet up
> and running. My pc has a Netgear WG311v3 Wireless PCI card. I have
> installed the windoes drivers using ndiswrapper and everything seems
> to be working fine. I can login to the router athttp://10.1.1.1and
> see my linux box as a connected DHCP client through firefox and I can
> even successfully ping addresses likewww.google.com.
>
> However, when I try to navigate firefox to any web address, i get no
> action. I just sits there for ages before eventually timing out.
>
> Here is the output from "sudo iwconfig wlan0"
> wlan0 IEEE 802.11g ESSID:"Jane_Is_Great"
> Mode:Managed Frequency:2.437 GHz Access Point:
> 00:11:95:95:FA:8C
> Bit Rate:54 Mb/s Sensitivity=-200 dBm
> RTS thr:2346 B Fragment thr:2346 B
> Encryption key:4321-0812-22 Security mode:restricted
> Power Managementff
> Link Quality:100/100 Signal level:-71 dBm Noise level:-256
> dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> and here is the output from "sudo ifconfig wlan0"
> wlan0 Link encap:Ethernet HWaddr 00:0F:B5:85:A0:61
> inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.0.0.0
> inet6 addr: fe80::20f:b5ff:fe85:a061/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1622 (1.5 KiB) TX bytes:1818 (1.7 KiB)
> Interrupt:209 Memory:ee010000-ee020000
>
> Any ideas why everything exceopt actually using a browser to see the
> internet seems to be working??
>
> Thanks....

Thanks for all your help - I ended up solving it just by switching off
ipv6 in firefox.