On Thu, 16 Apr 2009 18:14:27 Mark Misulich wrote:
I am at a hotel in China where I can't get onto the internet with linux. [snip] I am connected with a cable connection via ethernet, and can get linux to connect to the hotel network via knetwork manager.
So you do have a connection then. Do you have name resolution working? Try "dig www.opensuse.org" from the command line. Then try "ping www.opensuse.org".
If both of those work, you're on-line.
/Per
-- Per Jessen, Zürich (11.9°C)
Alternatively, check if you're on the same subnet as the hotel access page (or the hotel gateway); if at all possible, go with DHCP instead of static IPs. And disable any firewalls or IPtables for the time being...
Oh, and disable IPv6 of course...
Hi, I have tried to use DHCP to configure the connection to the ethernet. It only seems to work when I boot up the computer. Other than that I can only get a connection to the network when I put in the set of IP address numbers that the hotel IT guy used. But neither way will it connect to the internet, in fact I am not sure exactly if it is connected to any kind of network. The knetworkmanager is colored when I boot from shutdown, and if I connect with the IP address numbers the icon displays the little mouse icon that shows an ethernet connection. Yet with the dig command, I get the reply connection timed out, no servers could be reached. With the ping command, it says unknown host.
ipv6 is disabled, I disabled that when I installed 11.1.
Mark, I've had a similar issue with a public wireless connection - I could connect under Windows but not Linux - but I did work out how to make it work in my case. These types of services often use an internal login page that requires you to agree to a set of terms and conditions and maybe pay money (as in your case). This is usually an auto -redirect when you first open your browser but for some reason (maybe due to the use of MS-specific code behind the page) it doesn't seem to work properly for Linux clients. What I did was to copy the URL to the login page from the IE address bar under Windows and then manually enter that in Linux. That got me through the login process and connected to the net. There was a second glitch - it took 3 or 4 tries for the wireless connection to actually get an ip address on the local subnet; for some reason, the first 3 tries timed out and I ended up with a non-routable 169.254.x.x (default) address. If you're sure that you have an ip address that is in the correct address range (and check that the dns servers are being assigned by DHCP as well), try manually entering the login page URL. Regards, Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================