[opensuse] Problem with wireless connection with DHCP on OpenSuSE 11.0
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed. The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet. If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either. I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card. The Ethernet connection sometimes hotplugs and sometimes doesn't. It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s). TIA Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
The Ethernet connection sometimes hotplugs and sometimes doesn't.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
TIA Lisi
What does the route command show? -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 16:06:11 James Knott wrote:
Lisi Reisz wrote:
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
TIA Lisi
What does the route command show?
I must record that I fddled a bit, and it now seems to come up worse, but I have discovered that I can manually connect by entering a new connection in Network Manager. The new connection does not, however, survive a reboot. # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface loopback * 255.0.0.0 U 0 0 0 lo In other words, I have gone from a non-functioning connection to no connection! But as I say, I acn enter it as a new connection and it is then fine until I reboot again. TIA Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
The Ethernet connection sometimes hotplugs and sometimes doesn't.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
TIA Lisi
what make lap top are you using kde gnome ot something else ? do you know how to use the command line ? -- Hans Krueger hanskrueger007@roadrunner.com registered Linux user 289023 411024 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 16:12:30 Hans Krueger wrote:
Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
what make lap top
Dell Latitude C840, Ralink RT2500 external card
are you using kde gnome ot something else ?
KDE
do you know how to use the command line ?
Yes TIA Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lisi Reisz wrote:
On Sunday 09 November 2008 16:12:30 Hans Krueger wrote:
Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
what make lap top
Dell Latitude C840, Ralink RT2500 external card
are you using kde gnome ot something else ?
KDE
do you know how to use the command line ?
Yes
TIA Lisi
how do you want your lap top to connect to a network ? -- Hans Krueger hanskrueger007@roadrunner.com registered Linux user 289023 411024 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 17:50:29 Hans Krueger wrote:
Lisi Reisz wrote:
On Sunday 09 November 2008 16:12:30 Hans Krueger wrote:
Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
what make lap top
Dell Latitude C840, Ralink RT2500 external card
are you using kde gnome ot something else ?
KDE
do you know how to use the command line ?
Yes
how do you want your lap top to connect to a network ?
Ideally, automatically on boot up. Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lisi Reisz wrote:
how do you want your lap top to connect to a network ?
Ideally, automatically on boot up.
Lisi
On notebooks, you probably want ethernet to connect when the cable is plugged in, rather than at boot up. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 19:04:13 James Knott wrote:
Lisi Reisz wrote:
how do you want your lap top to connect to a network ?
Ideally, automatically on boot up.
Lisi
On notebooks, you probably want ethernet to connect when the cable is plugged in, rather than at boot up.
Yes - but I am not bothered about ethernet for the moment. If it connected when the cable was plugged in, that would be great. But that is decoration on the icing on the cake. A functioning wireless connection is essential. Without it the laptop can simply not fulfil its raison d'être, and will be of no use. Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lisi Reisz wrote:
On Sunday 09 November 2008 19:04:13 James Knott wrote:
Lisi Reisz wrote:
how do you want your lap top to connect to a network ?
Ideally, automatically on boot up.
Lisi
On notebooks, you probably want ethernet to connect when the cable is plugged in, rather than at boot up.
Yes - but I am not bothered about ethernet for the moment. If it connected when the cable was plugged in, that would be great. But that is decoration on the icing on the cake.
A functioning wireless connection is essential. Without it the laptop can simply not fulfil its raison d'être, and will be of no use.
Lisi
Given that the computer was previously talking to the Wifi router, though no further, indicates, at least, that the drivers are working with that hardware. This means that the problem is something in your configuration, though I have no idea, beyond that, where your problem lies. You mentioned in another note that the network configuration does not survive a reboot. That indicates a problem beyond networking, if a configuration is not saved. I use WiFi on my notebook and find it works very well. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 20:52:31 James Knott wrote:
Lisi Reisz wrote:
On Sunday 09 November 2008 19:04:13 James Knott wrote:
Lisi Reisz wrote:
how do you want your lap top to connect to a network ?
Ideally, automatically on boot up.
Lisi
On notebooks, you probably want ethernet to connect when the cable is plugged in, rather than at boot up.
Yes - but I am not bothered about ethernet for the moment. If it connected when the cable was plugged in, that would be great. But that is decoration on the icing on the cake.
A functioning wireless connection is essential. Without it the laptop can simply not fulfil its raison d'être, and will be of no use.
Lisi
Given that the computer was previously talking to the Wifi router, though no further, indicates, at least, that the drivers are working with that hardware. This means that the problem is something in your configuration, though I have no idea, beyond that, where your problem lies. You mentioned in another note that the network configuration does not survive a reboot. That indicates a problem beyond networking, if a configuration is not saved. I use WiFi on my notebook and find it works very well.
Yes - that is exactly my problem! That I can see no earthly reason why it works sometimes and others not. I am sticking to using the network manager because it is a long time since I used an .rpm distro since I hve used almost exclusively .deb distros - and I would know how to go down and dirty in a .deb system!! Anyhow, it is obviously not a known issue with Network Manager, and I am clearly not making an obvious mistake. As of now, it is working. I shall just have to show my granddaughter how to start it manually if it loses itself again. That is the bit that really gets me - that it sometimes saves alright and then a reboot or three later suddenly all the settings are gone again. I'm even beginning to wonder whether it is a hardware fault of some kind in the laptop. Anyhow, thanks for your help - all of you. Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2008-11-09 at 15:41 -0000, Lisi Reisz wrote:
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
I think you are not getting a default GW, or it is incorrect. The "route" command should say. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkXDfkACgkQtTMYHG2NR9X7MwCfQX+mE2p8A0pssmAnBl7Mj8pI SMgAnR9hPP7y9qAB5sCghejPh43Cv8JE =rt0J -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 09 November 2008 16:21:10 Carlos E. R. wrote:
On Sunday, 2008-11-09 at 15:41 -0000, Lisi Reisz wrote:
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
I think you are not getting a default GW, or it is incorrect. The "route" command should say.
Unfortunately, in improving the immediate future, thereby allowing myself to install the extra software I needed, I made the long term worse. :-( See my reply to James Knott. Three things are essential for this laptop: 1) At least one office suite (in English) Open Office and Koffice. Done. 2) At least one wordprocessor and one email client that can input in Japanese from the keyboard. Done easily on SuSE. But using a lot of help previously and laboriously absorbed earlier. 3) On-at-boot wireless DHCP connection. This is the closest I have got with any distro (and this is a longstanding problem). So I am tantalisingly close. But it is becoming really urgent. Tomorrow XP. So please, save me from having to administer an XP machine! TIA Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Sonntag, 9. November 2008 16:41:19 schrieb Lisi Reisz:
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
If you have a look at /etc/resolv.conf, does it list a DNS and does it state that the file was created by networkmanager? As root you can run the command "route -n" to check whether the route is set- up correctly.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
You can try to swithc to the traditional method in YaST (global options), just to make sure that it is networkmanager and not something else.
The Ethernet connection sometimes hotplugs and sometimes doesn't.
There might be hints in the logs, you can either check them manually as root in /var/log, i.e. messages and NetworkManager or you can use the YaST-tool in the Misc. section. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On November 9, 2008 07:41:19 am Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed.
The laptop has two network cards: an ethernet card and a wireless card. If the ethernet card is plugged in at boot it works fine on DHCP and can connect to the internet.
If the wireless card is the only interface plugged in at boot, it is connecting to the router and being assigned an IP. It can then ping the router and the router can ping it. It cannot however connect to the internet. This does not appear to be a DNS problem, since it cannot reach the internet by IP either.
I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card.
The Ethernet connection sometimes hotplugs and sometimes doesn't.
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
TIA Lisi
Lisi, I hope you're not offended if I ask if you have configured the network cards via Yast yet? It's just that I haven't seen any mention of it in the thread and the wired nic card defaults are ususally enough to get a connection, but wireless often is not. (System, Yast, enter root password, Network Devices, Network Setting). This is where you highlight each nic card setting - one for wired, one for wireless in your case, and can then edit the settings. Once you complete the network connections page, click on next and you'll be able to enter the ESSID of the network, any encryption keys, etc. Clicking on finish should save all the settings. Now you should be able to use knetwork manager to make the connection. Hope this helps. Bob. -- bob@rsmits.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Montag, 10. November 2008 02:20:05 schrieb Robert Smits:
Lisi, I hope you're not offended if I ask if you have configured the network cards via Yast yet? It's just that I haven't seen any mention of it in the thread and the wired nic card defaults are ususally enough to get a connection, but wireless often is not.
(System, Yast, enter root password, Network Devices, Network Setting).
This is where you highlight each nic card setting - one for wired, one for wireless in your case, and can then edit the settings. Once you complete the network connections page, click on next and you'll be able to enter the ESSID of the network, any encryption keys, etc. Clicking on finish should save all the settings.
Now you should be able to use knetwork manager to make the connection.
If one uses the user-driven method, i.e. networkmanager, there is no need for YaST. YaST is only need for the traditional-method in which case networkmanager is not started anymore. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 10 November 2008 01:20:05 Robert Smits wrote: On Monday 10 November 2008 01:20:05 Robert Smits wrote:
On November 9, 2008 07:41:19 am Lisi Reisz wrote:
I have a fresh installation of OpenSuSE 11.0 on a laptop. I am almost a SuSE newbie and am flummoxed. ........ I am completely unfamiliar with NetworkManager, but can see no way of persuading it to connect fully with the wireless card. ........
It is the wireless connection that is crucial. It must connect via DHCP to a school system with a known SSID, but unknown gateway and DNS server(s).
Lisi, I hope you're not offended if I ask if you have configured the network cards via Yast yet?
Not in the least - as I said, I am a virtually a newbie in SuSE and .rpm, so don't really know what I am doing.
It's just that I haven't seen any mention of it in the thread and the wired nic card defaults are ususally enough to get a connection, but wireless often is not.
(System, Yast, enter root password, Network Devices, Network Setting).
This is where you highlight each nic card setting - one for wired, one for wireless in your case, and can then edit the settings. Once you complete the network connections page, click on next and you'll be able to enter the ESSID of the network, any encryption keys, etc. Clicking on finish should save all the settings.
Now you should be able to use knetwork manager to make the connection.
I had looked at it, but as a last resort not as a first. And I still hadn't/haven't sussed it out fully. So this is very helpful. I now know how it is _supposed_ to work! For 3 or 4 years I have solved network problems at the command line via the config files. But I have not set up a wireless card before and it is some 5 years since I briefly dipped my toe in SuSE. I have used .deb systems, which store some things in different places from .rpm systems. So - think newbie. And I am grateful for all advice, not insulted!! At the moment it is working. I am keeping my fingers crossed that it will work at school! Lisi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Hans Krueger -
James Knott -
Lisi Reisz -
Robert Smits -
Sven Burmeister