Hello,
I have OpenSUSE 12.1 on my HP ProBook, half year without problem, but now I cant connect to the internet. I am connected to network via network manager (nm-tool tells I am connected through wired connection (alternatively via wifi)), I can ping both the addresses in the internal and external network, but the firefox (also Konquerror) cant connect to the internet. Also the updates cant be downloaded. Any idea? The problems seemed to start after incorrect shutdown (low batteries), but I am not sure. Thanks
Good info. Should be a desktop config issue, is Proxy disabled?
PROXY_ENABLED: no
I just realised that ping works only if I write the number adress: ping 173.194.35.180 works, but ping Google tells “unknown host”…
Hello,
the problem persists. I switched the network managing from NetworkManager to ifup in Yast. I made the same settings as on my second computer, with the same system and in the same network, but it is still not able to “translate” the adress. When I type 173.194.35.180 into FireFox, it returns normal google page, but “www.google.com” doesn’t work. Any idea? I noticed the system on startup writes:
udevd[252]: failed to execute ‘/etc/sysconfig/network/scripts/ifup-sysctl’ ’ /etc
hotplug’ : No such file or directory
Hi
It is a problem endemic to Suse 12/1.
On install of 12.1 from 11/4 I could not connect to the internet
consistently only in rare cases over time.
I am using a Wi Fi connection from my neighbors network.
Completely legal as the airwaves are free.
When I reinstalled 11.4 I again was able to connect to the Internet.
So it appears there is a problem with openSUSE 12.1.
I have not checked the bug reports yet but I am headed in that
direction now.
On 03/23/2012 03:46 AM, leonakselrad wrote:
>
> jrcz;2449831 Wrote:
>> Hello,
>> I have OpenSUSE 12.1 on my HP ProBook, half year without problem, but
>> now I can`t connect to the internet. I am connected to network via
network manager (nm-tool tells I am connected through wired connection
(alternatively via wifi)), I can ping both the addresses in the internal
and external network, but the firefox (also Konquerror) can`t connect to
>> the internet. Also the updates cant be downloaded. Any idea? The
>> problems seemed to start after incorrect shutdown (low batteries), but I
>> am not sure. Thanks
>
> Hi
>
> IT IS A PROBLEM ENDEMIC TO SUSE 12/1.
>
> On install of 12.1 from 11/4 I could not connect to the internet
> consistently only in rare cases over time.
>
> I am using a Wi Fi connection from my neighbors network.
> Completely legal as the airwaves are free.
>
> When I reinstalled 11.4 I again was able to connect to the Internet.
>
> SO IT APPEARS THERE IS A PROBLEM WITH OPENSUSE 12.1.
>
> I have not checked the bug reports yet but I am headed in that
> direction now.
No need to shout.
The only problem with 12.1 is that sometimes the routing gets messed up when you
change from wireless to wired. If you cannot access the network, always check
‘/sbin/route -n’ and verify that there is a line with flags UG set, and that it
refers to the proper interface.
The temporary fix is ‘sudo /sbin/route add default gw <IP address of router>’.
On 2012-03-20 17:26, jrcz wrote:
>
> I just realised that ping works only if I write the number adress: ping
> 173.194.35.180 works, but ping ‘Google’ (http://www.google.com) tells
> “unknown host”…
Verify you have a DNS setting and that the DNS server is good.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Yesteday installed opeSUSE 12.1 onto my desktop found similar problem connecting.
Found within the Network Settings with ifup selected then on page:overview to get connected needed add my=“RTL8111/8168B PCI Express Gigabit Ethernet controller”, as soon as this completed connection started to work.
Hello,
the problem is solved. I dont know why, but sometimes I need to run
dhcpcd wlan0 (or eth0)
under root. Then it works without problem.
Thanks for this, I’ve been researching for a solution for this annoying problem for a couple of days now!
On my case it was obvious that DHCP wasn’t working correctly under the wired connection (eth0), but it worked perfectly under wlan0. This problem definitely did not exist under 11.4 and almost made me downgrade.
Please note - after issuing the command you recommended, the interface settles with DHCP assigned IP address but also spurs the following errors:
linux-p030:~ # dhcpcd eth0
err, eth0: timed out
err, eth0: lease expired 103659 seconds ago
err, eth0: ARPOP_REPLY received from 169.254.63.189 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.37.192 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.5.62 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.80.6 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.73.215 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.121.106 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.65.218 (00:15:62:95:c7:c8)
err, eth0: ARPOP_REPLY received from 169.254.30.31 (00:15:62:95:c7:c8)
^Cwarn, eth0: using IPV4LL address 169.254.185.152
The messages above continues until CTRL+C is pressed.
If machine reboots, the same process needs to be repeated.
On 2012-04-12 14:26, batequeixo wrote:
> Please note - after issuing the command you recommended, the
> interface settles with DHCP assigned IP address but also spurs the
> following errors:
Notice that you can change what dhcp client the system uses. You don’t need
to call it manually. Look at “/etc/sysconfig/network/dhcp” if you are using
the traditional method.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Gracias Carlos.
Is this what I’d change to make this stick across reboots?
Which DHCPv4 client should be used?
If empty, dhcpcd is tried, then dhclient
Other possible values:
dhcpcd (DHCP client daemon)
dhclient (ISC dhclient)
DHCLIENT_BIN=""
More specifically, the line “DHCLIENT_BIN=” gets changed to DHCLIENT_BIN=dhcpcd eth0 ?
On 2012-04-12 19:56, batequeixo wrote:
>
> Gracias Carlos.
>
> Is this what I’d change to make this stick across reboots?
>
> # Which DHCPv4 client should be used?
> # If empty, dhcpcd is tried, then dhclient
> # Other possible values:
> # dhcpcd (DHCP client daemon)
> # dhclient (ISC dhclient)
> DHCLIENT_BIN=""
>
> More specifically, the line “DHCLIENT_BIN=” gets changed to
> DHCLIENT_BIN=dhcpcd eth0 ?
Yes. Just “dhcpcd”. The comments do not mention that you can add “eth0” or
anything else. Anyway, just try.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)