wi-pi is working, kinda sorta

That doesn't sound like a wifi consideration - more of a routeing or firewall issue. If you can ping the router, there's no on-board reason you can't ping anywhere else.

Have you tried using Wicd to configure your network settings?

Roger, I stated (parenthetically) that I can ping, (... any website). ...and I can visit any website with Lynx. Furthermore (I didn't mention this one before) I can see the RASPBERRYPI computer from other computers on my home network; a firewall or router issue would prevent this. I was thinking it might be a packet size issue. The page loading problem (the message is "unable to resolve", but when I use the website ip address the pages still don't load) might have been some type of time out issue, but messing with mtu size didn't help. I have a few more things I can try out before I have too do any serious work.

Dave

That would point me in the direction of DNS issues, how is the Pi being told which DNS to use? Is it being told the right one?

Sites hosted on shared servers require the relevant domain name in the GET command so they know which site to serve. Without it you may get a page from the hosting co or nothing at all.

No, but I just looked it up afer reading your post. I did everything by hand. I setup /etc/network/intefaces to use dhcp, and it gets a lease; comes up OK on the boot. I messed around with the packet size, but it still seems to be some kind of timeout issue when I use x-windows. I don't get any timeouts when using eth0, so maybe the wi-pi is too slow. Maybe I need to mess with the ttl of the packets. Anyway, I can mount a network drive (that's on a Windows 7 PC) on my Raspberry Pi, so my network setup must be OK.

If you run lynx in a terminal window on the desktop that works?

website).

this

my

thinking

is

still

with

have

website).

this

my

thinking

is

still

with

have

Dave, can you stop "top posting", please?

Dave - could you be persuaded to adopt the bottom post convention that others are using in this newsgroup?

The mixture of top and bottom posting on this interesting thread makes it hard to follow.

John

es

Seconded.

James

Dave Marshall Inscribed thus:

Could be a permissions issue !

Which you can find using iptables-save. If it prints something else than just a newline you have firewall rules enabled, and these will be listed.

To test basic connectivity, use ping

Next try ping -i 0.2

If all this works without packet loss or delays then your network basic connectivity is OK, then you have to look at filters and permissions.

You can try to execute the network part of the HTTP directly by using telnet. "telnet

If all of these work, then the error is with the application itself.

-- mrr

I thought you said lynx worked on the gui desktop?

If it's not working it's probably the network manager on the desktop overriding your wifi configuration. best solution is probably disabling the network manager. I'm not sure how.

"Lynx stopped working" as a diagnostic is about as useless as my long ex girlfriend phoning on her mobile saying 'how to I find your house' and when I asked 'where are you?' she said 'I don't know or I wouldn't have phoned'.

You are second guessing the problem. Don't guess, ask.

Start X open a terminal type this on the command line:

host

You should see something like this:

host

I doubt wi-pi is too slow, unless it is implementing CP/IP[*] and you live in a hawk infested environment[**]. ;-)

Oh, you mean a terminal window brought up with xwindows running. It doesn't; no browser works after running startx, so this isn't a network issue. In fact, I fixed the problem. I switched to the Mate windows manager, and everthything works. I first thought this might be a power problem, since I was adding a device, but using a powered hub didn't work. I found that Raspbian used to have problem with certain mice, but switching to a different mouse didn't help. ...and, deleting all of my log files (too free up disk space didn't help - my SD card was getting pretty full).

It obviously had something to do with startx, so I changed from lxcde to Mate, and I can now browse with my gui up. Btw, you can read about Mate on the raspbian.org website. Mate is the resurrection of gnome 2, so I thought it would use less processor time then gnome 3 or kde.

Dave

website).

this

my

thinking

is

still

with

have

This isn't a network issue, like everybody seems to think. In fact, I fixed the problem. I switched from lxcde to the Mate and everthything works. I first thought this might be a power problem, since I was adding a device, but using a powered hub didn't work. I found that Raspbian used to have problem with certain mice, but switching to a different mouse didn't help. ...and, deleting all of my log files (too free up disk space didn't help - my SD card was getting pretty full).

It obviously had something to do with startx, so I changed from lxcde to Mate, and I can now browse with my gui up. Btw, you can read about Mate on the raspbian.org website. Mate is the resurrection of gnome 2, so I thought it would use less processor time then gnome 3 or kde.

Dave