Hi, last Thursday evening my DSL signal to my house went dead, and didn't come back. Today the repair man came and replaced a connection module in the box on the wall outside of my house. Voila, DSL signal tested good up to the modem next to the computer inside the house. But the DSL modem didn't show that there was a signal. So the repairman replaced the DSL modem with a new modem with integrated wifi, and I was able to log on to the internet in Win7, WinXP, but not openSuse. He left, and I thought that I just had to configure something in yast to make it work. But it's not working, and the settings seem to be correct for the network. I can't connect to the internet on any computer using openSuse with a wired connection. I can connect using wifi with my laptop, but even it won't connect with a wired connection to the internet. I'm using opensuse leap 15.0 with KDE Frameworks 5.45.0. I will need some help to resolve this, so thanks in advance. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2018 07:15 PM, Mark Misulich wrote:
I can't connect to the internet on any computer using openSuse with a wired connection.
Do you have DHCP enabled? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2018-10-01 at 20:07 -0400, James Knott wrote:
On 10/01/2018 07:15 PM, Mark Misulich wrote:
I can't connect to the internet on any computer using openSuse with a wired connection.
Do you have DHCP enabled?
Yes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2018-10-01 at 19:15 -0400, Mark Misulich wrote:
Hi, last Thursday evening my DSL signal to my house went dead, and didn't come back. Today the repair man came and replaced a connection module in the box on the wall outside of my house. Voila, DSL signal tested good up to the modem next to the computer inside the house. But the DSL modem didn't show that there was a signal. So the repairman replaced the DSL modem with a new modem with integrated wifi, and I was able to log on to the internet in Win7, WinXP, but not openSuse. He left, and I thought that I just had to configure something in yast to make it work. But it's not working, and the settings seem to be correct for the network. I can't connect to the internet on any computer using openSuse with a wired connection. I can connect using wifi with my laptop, but even it won't connect with a wired connection to the internet.
I'm using opensuse leap 15.0 with KDE Frameworks 5.45.0.
I will need some help to resolve this, so thanks in advance.
Mark
Hi, I was able to find the problems in the configuration and resolved them. In Yast on the desktop computer, the network is controlled by wicked. The default device was listed as a "-" for IPv4Gateway and for IPv6Gateway. I selected eth0 as the device for both protocols, and then saved the configuration. Then the wired connection started to work. I checked the configuration one more time, and eth0 was no longer selected. It had gone back to "-". But it has stayed working regardless, and I have a wired connection to the internet. On my laptop, when I checked the network configuration in yast previously, a separate configuration for eth0 did not appear. After several times of attempting to configure the network settings, a separate configuration for wlan and eth0 showed up in yast reflecting the different hardware in use. I edited each of them separately for their respective functions, and they work correctly now. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2018-10-01 at 20:27 -0400, Mark Misulich wrote:
On Mon, 2018-10-01 at 19:15 -0400, Mark Misulich wrote:
Hi, last Thursday evening my DSL signal to my house went dead, and didn't come back. Today the repair man came and replaced a connection module in the box on the wall outside of my house. Voila, DSL signal tested good up to the modem next to the computer inside the house. But the DSL modem didn't show that there was a signal. So the repairman replaced the DSL modem with a new modem with integrated wifi, and I was able to log on to the internet in Win7, WinXP, but not openSuse. He left, and I thought that I just had to configure something in yast to make it work. But it's not working, and the settings seem to be correct for the network. I can't connect to the internet on any computer using openSuse with a wired connection. I can connect using wifi with my laptop, but even it won't connect with a wired connection to the internet.
I'm using opensuse leap 15.0 with KDE Frameworks 5.45.0.
I will need some help to resolve this, so thanks in advance.
Mark
Hi, I was able to find the problems in the configuration and resolved them. In Yast on the desktop computer, the network is controlled by wicked. The default device was listed as a "-" for IPv4Gateway and for IPv6Gateway. I selected eth0 as the device for both protocols, and then saved the configuration. Then the wired connection started to work. I checked the configuration one more time, and eth0 was no longer selected. It had gone back to "-". But it has stayed working regardless, and I have a wired connection to the internet.
On my laptop, when I checked the network configuration in yast previously, a separate configuration for eth0 did not appear. After several times of attempting to configure the network settings, a separate configuration for wlan and eth0 showed up in yast reflecting the different hardware in use. I edited each of them separately for their respective functions, and they work correctly now.
I left the settings overnight as described above, but they didn't remain in memory as set to eth0 in order to allow internet access after I shut the computer down last evening and restarted it this morning. I had to go back into yast to reset the settings to eth0 for IPv4 and IPv6 to get back on the internet. Can anyone advise me what file I need to modify to set this to eth0 for IPv4 and IPv6 permanently to allow internet access? Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 2 oktober 2018 14:07:23 CEST schreef Mark Misulich:
I left the settings overnight as described above, but they didn't remain in memory as set to eth0 in order to allow internet access after I shut the computer down last evening and restarted it this morning. I had to go back into yast to reset the settings to eth0 for IPv4 and IPv6 to get back on the internet. Can anyone advise me what file I need to modify to set this to eth0 for IPv4 and IPv6 permanently to allow internet access?
Thanks, Mark
The settings for wicket are stored in /etc/sysconfig/network/ in a few files. These are ifcfg-eth0 and router. More general settings in config and dhcp, which generally do not need any changing to make the network work. In case you use DHCP for both systems, the content of these files should not differ. You may show the content for further help. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2018-10-02 at 16:47 +0200, Freek de Kruijf wrote:
Op dinsdag 2 oktober 2018 14:07:23 CEST schreef Mark Misulich:
I left the settings overnight as described above, but they didn't remain in memory as set to eth0 in order to allow internet access after I shut the computer down last evening and restarted it this morning. I had to go back into yast to reset the settings to eth0 for IPv4 and IPv6 to get back on the internet. Can anyone advise me what file I need to modify to set this to eth0 for IPv4 and IPv6 permanently to allow internet access?
Thanks, Mark
The settings for wicket are stored in /etc/sysconfig/network/ in a few files. These are ifcfg-eth0 and router. More general settings in config and dhcp, which generally do not need any changing to make the network work. In case you use DHCP for both systems, the content of these files should not differ. You may show the content for further help.
-- fr.gr.
member openSUSE Freek de Kruijf
I'm not sure why,but the /etc/sysconfig/network/ifcfg-eth0 file rewrote itself with several errors when the repair work on the dsl line was being performed. There were two specific errors in file that caused the computer to be unable to connect to the internet. First, the name of the network card was missing from the file. I wrote that into the file by copying a line from the same file in a computer that had opensuse installed that could reach the internet. Second, there was an extra line inserted in the file that was wrong: DHCLIENT_SET_DEFAULT_ROUTE='yes' was written correctly in the file. Then a few lines below it, DHCLIENT_SET_HOSTNAME='yes' was written. The default for that setting is no, according to the /etc/sysconfig/network/dhcp file. The two settings conflicted with each other. I compared the ifcfg-eth0 file in the problem computer with the same file in a working computer, and the working computer didn't have that line in the file. So I just deleted that line in the file in the problem computer. After those changes were made and the file saved, the computer would connect automatically to the internet. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/18/2018 08:55 PM, Mark Misulich wrote:
I'm not sure why,but the /etc/sysconfig/network/ifcfg-eth0 file rewrote itself with several errors when the repair work on the dsl line was being performed. There were two specific errors in file that caused the computer to be unable to connect to the internet.
That's not too different a problem from what I experienced when my /etc/default/grub file had additional setting inserted into it on or about the first week in Oct. causing os-prober to begin running and adding Win10 to my grub.cfg file. It's just a wild guess on my part, but it is almost like some global setting in SuSEConfig that prevents altering working config files was inadvertently flipped so that instead of creating a config.rpmnew file, the changes are just written to your working config instead.... Did you by chance find an /etc/sysconfig/network/ifcfg-eth0.old file in your network directory? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2018-10-19 at 01:26 -0500, David C. Rankin wrote:
On 10/18/2018 08:55 PM, Mark Misulich wrote:
I'm not sure why,but the /etc/sysconfig/network/ifcfg-eth0 file rewrote itself with several errors when the repair work on the dsl line was being performed. There were two specific errors in file that caused the computer to be unable to connect to the internet.
That's not too different a problem from what I experienced when my /etc/default/grub file had additional setting inserted into it on or about the first week in Oct. causing os-prober to begin running and adding Win10 to my grub.cfg file.
It's just a wild guess on my part, but it is almost like some global setting in SuSEConfig that prevents altering working config files was inadvertently flipped so that instead of creating a config.rpmnew file, the changes are just written to your working config instead....
Did you by chance find an /etc/sysconfig/network/ifcfg-eth0.old file in your network directory?
-- David C. Rankin, J.D.,P.E.
No, there was just the ifcfg-eth0 file that had the errors written into it. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/10/2018 03.55, Mark Misulich wrote:
I'm not sure why,but the /etc/sysconfig/network/ifcfg-eth0 file rewrote itself with several errors when the repair work on the dsl line was being performed. There were two specific errors in file that caused the computer to be unable to connect to the internet. First, the name of the network card was missing from the file. I wrote that into the file by copying a line from the same file in a computer that had opensuse installed that could reach the internet. Second, there was an extra line inserted in the file that was wrong: DHCLIENT_SET_DEFAULT_ROUTE='yes' was written correctly in the file. Then a few lines below it, DHCLIENT_SET_HOSTNAME='yes' was written. The default for that setting is no, according to the /etc/sysconfig/network/dhcp file. The two settings conflicted with each other. I compared the ifcfg-eth0 file in the problem computer with the same file in a working computer, and the working computer didn't have that line in the file. So I just deleted that line in the file in the problem computer. After those changes were made and the file saved, the computer would connect automatically to the internet. Mark
Er... no, DHCLIENT_SET_DEFAULT_ROUTE does not conflict with DHCLIENT_SET_HOSTNAME. Typically for most home routers they should be "yes", "no". -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Fri, 2018-10-19 at 09:57 +0200, Carlos E. R. wrote:
On 19/10/2018 03.55, Mark Misulich wrote:
I'm not sure why,but the /etc/sysconfig/network/ifcfg-eth0 file rewrote itself with several errors when the repair work on the dsl line was being performed. There were two specific errors in file that caused the computer to be unable to connect to the internet. First, the name of the network card was missing from the file. I wrote that into the file by copying a line from the same file in a computer that had opensuse installed that could reach the internet. Second, there was an extra line inserted in the file that was wrong: DHCLIENT_SET_DEFAULT_ROUTE='yes' was written correctly in the file. Then a few lines below it, DHCLIENT_SET_HOSTNAME='yes' was written. The default for that setting is no, according to the /etc/sysconfig/network/dhcp file. The two settings conflicted with each other. I compared the ifcfg-eth0 file in the problem computer with the same file in a working computer, and the working computer didn't have that line in the file. So I just deleted that line in the file in the problem computer. After those changes were made and the file saved, the computer would connect automatically to the internet. Mark
Er... no, DHCLIENT_SET_DEFAULT_ROUTE does not conflict with DHCLIENT_SET_HOSTNAME. Typically for most home routers they should be "yes", "no".
Hi Carlos, thanks for correcting me on this. What I meant by conflicted was that when I took the line out of the ifcfg-eth0 file, the internet started to work. Since it didn't work before the change, I assumed there was a conflict. Now I know that I was wrong, and I will work on trying to figure out why. But at least I got lucky and got the problem fixed. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/10/2018 14.34, Mark Misulich wrote:
Er... no, DHCLIENT_SET_DEFAULT_ROUTE does not conflict with DHCLIENT_SET_HOSTNAME. Typically for most home routers they should be "yes", "no".
Hi Carlos,
thanks for correcting me on this. What I meant by conflicted was that when I took the line out of the ifcfg-eth0 file, the internet started to work. Since it didn't work before the change, I assumed there was a conflict. Now I know that I was wrong, and I will work on trying to figure out why. But at least I got lucky and got the problem fixed.
I think you should have: DHCLIENT_SET_DEFAULT_ROUTE=yes DHCLIENT_SET_HOSTNAME=no The second setting saying yes has no consequence besides the machine name not being what you expect. I have not seen it working correctly with a home (aka cheap) router. However, the first setting being "no" typically makes your internet to fail. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (5)
-
Carlos E. R. -
David C. Rankin -
Freek de Kruijf -
James Knott -
Mark Misulich