Just upgraded to 12.3 from 12.1 all went well except >:(
The the static IP address that I set in not being used, a DHCP address is being used instead.
Most frustrating trying to access the services I am running on this machine.
Note: I am a long time Linux User despite my “Newcomer” status.
Did we try in both Network manager and YaST ?
Welcome to the forums.
Could you be a little more specific in what you have done and what you
expected? For example, if your NIC is setup for DHCP in Yast, or if it is
set to use Network Manager, but you (being a non-newbie) explicitly added
an IP address to your NIC using the ‘ip’ command, then what you describe
would sound pretty normal to me. If, on the other hand, you configured
Yast to use a static IP address and disabled Network Manager, then getting
an IP address via DHCP would be a little strange. As usual, providing
some output from your system may help:
Please describe exactly what you setup, where and how, to help us
duplicate the scenario.
Good luck.
http://www.haidagwaii.net/carlmerk/asnapshot1129.pnghttp://www.haidagwaii.net/carlmerk/asnapshot1130.png
I have used every version Suse from 8.0 to-date some where not good and I reverted to the previous version.
I could not access the machine remotely (web server, rsync server, ftp server), and could not even ping it.
After checking and rechecking my settings, I found my static IP that was set in Yast was not being respected, a DHCP IP was being used instead
My temporary work around, change my DHCP server to give it the expected IP http://usalug.com/phpBB3/images/smilies/smilies/usalug/icon_idea.gif
Until this issue is fixed the upgrade of my gateway computer protecting my internal network is on hold.
Try:
ps -ef | grep Network
For me, that gives only one line of output (the grep command itself). I’m guessing that you will get another line showing that NetworkManager is running and managing your network.
If NetworkManger is running, then you could try:
Go to Yast, and switch to Network Manager.
After that is done, switch back to “ifup”.
I’m thinking that Yast is confused as to the current state.
Also check the release-notes for 12.3. They give the command-line way of choosing between NetworkManager and “ifup”.
:~> ps -ef | grep Network
root 527 1 0 Mar14 ? 00:00:00 /usr/sbin/NetworkManager --no-daemon
carl 8071 8047 0 14:16 pts/1 00:00:00 grep --color=auto Network
Went to Yast, and switch to Network Manager.
After that is done, switched back to “ifup”.
:~> ps -ef | grep Network
carl 9886 8047 0 14:19 pts/1 00:00:00 grep --color=auto Network
That may have fixed it. Thank you.
Another user who is experiencing this exact problem. I too ran an upgrade from OpenSuse 12.1 to 12.3. I am using ifup and have a static ip installed, however there seems to be a dhcp address being used which I cannot identify where it is coming from. Switching back and forth from NetworkManager did not help.
The static IP I set is 192.168.0.240, set in the Network Devices section via Yast.
Following the remarks above, here are my findings.
computer:~ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:15:5d:00:e7:07 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.116/24 brd 192.168.0.255 scope global eth0
inet 192.168.0.240/24 brd 192.168.0.255 scope global secondary eth0
computer:~ # ip route
default via 192.168.0.254 dev eth0
127.0.0.0/8 dev lo scope link
169.254.0.0/16 dev eth0 scope link
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.116
computer:~ # ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
25838272 169122 0 0 0 0
TX: bytes packets errors dropped carrier collsns
25838272 169122 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
link/ether 00:15:5d:00:e7:07 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
213106565 1512931 0 648 0 0
TX: bytes packets errors dropped carrier collsns
289398493 849128 0 0 0 0
computer:~ # grep -v ‘^#’ /etc/resolv.conf
search mydomain.local
nameserver 192.168.0.228
nameserver 192.168.0.248
Please advise.
Regards,
Set the IP statically with NetworkManager disabled and then reboot. Does
the other IP come back at that point? If so, look for it under
/etc/sysconfig as shown below:
Post the output.
Good luck.
This looks like a problem I reported in 2011… [Bug 733506] eth0:r8169 driver: No DHCP/Static IP only works after fiddl](http://lists.opensuse.org/archive/opensuse-bugs/2011-12/msg00156.html)
The solution is to download a working ethernet driver for your chipset from RealTek Realtek
The problem as you noted is, the shipped driver “almost” works. I asked that the driver solution be communicated to www.kernel.org as this driver issue affects all distributions and isn’t an OS problem. I’d report it myself except the kernel guys are too busy and don’t listen to individual users (they will listen to OS distributor teams, like OpenSUSE). This problem was around for years before I reported it here, and it’s been years since I reported it and it’s still here. It’s also a problem that’s darn difficult to track down.
The good news is since installing the RealTek driver, everything works and is rock solid. And installing the RealTek driver was almost trivial as root.
Best of luck…
Craig
Hi…
On 04/12/13 08:16 pm, craigarno thus wrote :
>
> This looks like a problem I reported in 2011… ‘[Bug 733506] eth0:r8169
> driver: No DHCP/Static IP only works after fiddl’
> (http://lists.opensuse.org/archive/opensuse-bugs/2011-12/msg00156.html)
>
> The solution is to download a working ethernet driver for your chipset
> from RealTek ‘Realtek’ (http://tinyurl.com/la9ey)
>
> The problem as you noted is, the shipped driver “almost” works. I
> asked that the driver solution be communicated to ‘www.kernel.org’
> (https://www.kernel.org/) as this driver issue affects all distributions
> and isn’t an OS problem. I’d report it myself except the kernel guys
> are too busy and don’t listen to individual users (they will listen to
> OS distributor teams, like OpenSUSE). This problem was around for years
> before I reported it here, and it’s been years since I reported it and
> it’s still here. It’s also a problem that’s darn difficult to track
> down.
>
> The good news is since installing the RealTek driver, everything works
> and is rock solid. And installing the RealTek driver was almost trivial
> as root.
>
> Best of luck…
>
Craig, I don;t know if this is the same issue or not. I bumped into it
with an upgrade from 12.1 x64 to 12.3 x64 on a Proliant server, using
the same NIC driver. The issue had/has to do with NetworkManager and the
fact that when NetWorkManager is present, dhcp-client starts up, which
effectively disconnects the static address assigned to the interface.
A more thorough discussion may be found here:
https://bugzilla.novell.com/show_bug.cgi?id=807646
What a pain!
Got something similar with 8139too
I’ve set up static with ifup, it will connect to router ip with no problem, however…
It doesn’t resolve anything, opensuse.com in firefox returns “unable to connect”
If I change hostname or other network settings in yast, and let it save, then it works.
On reboot, it doesn’t work again.
If I run “dhcpcd eth0” it works, but on reboot, it doesn’t work again.
Thing is, it’s working just fine on 12.2 with no dhcpd installed.
On 5/24/2013 12:06 AM, finders wrote:
>
> Got something similar with 8139too
>
> I’ve set up static with ifup, it will connect to router ip with no
> problem, however…
> It doesn’t resolve anything, opensuse.com in firefox returns “unable to
> connect”
>
> If I change hostname or other network settings in yast, and let it
> save, then it works.
> On reboot, it doesn’t work again.
>
> If I run “dhcpcd eth0” it works, but on reboot, it doesn’t work again.
> Thing is, it’s working just fine on 12.2 with no dhcpd installed.
>
>
finders;
It rather sounds like you are not setting the DNS server. When you are unable to resolve names, check if you can ping the Google
DNS server by IP:
ping -c3 8.8.8.8
If the ping succeeds try setting your DNS servers in YaST to the public Google name servers; 8.8.8.8 and 8.8.4.4
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
On 5/24/2013 12:41 AM, PV wrote:
<snip>
>>
>> If I run “dhcpcd eth0” it works, but on reboot, it doesn’t work again.
>> Thing is, it’s working just fine on 12.2 with no dhcpd installed.
>>
>>
<snip>
>
P.V.
“We’re all in this together, I’m pulling for you” Red Green
I’ve set these servers in yast from the start, it will not ping any ip after reboot, regardless of dns settings.
The router is set as gateway on eth0, normally it connects just fine (I’m on 12.2 atm)
No typo, it’s the daemon. I run that and it works somehow.
There’s a difference between dhcpd and dhcpcd!
dhcpd is the dhcp daemon, but dhcpcd is a client…
See http://www.phystech.com/download/dhcpcd_man.html:
DESCRIPTION
dhcpcd is an implementation of the DHCP client specified in RFC2131 (when -r option is not specified) and RFC1541 (when -r option is specified).
So it’s dhcp client daemon and not a dhcp server daemon… Point is?
I don’t need any of them on 12.2, ifup static just works with no dhcp.
So if it’s working with dhcpcd running, i.e. you get the IP address and network setup via DHCP, and not without it, there must be something wrong with your static setup.
Maybe you forgot to specify the default gateway? (should be the router I guess)
The point is that dhcpcd is a DHCP **client **like dhclient. So if you run it you don’t have a static setup anymore.
It’s the exact same setup that’s working on 12.2 so it’s nothing wrong with it.
The problem is not in default gateway, because if I change any setting in yast, like hostname or ip, it’s working fine.
When yasts saves the settings and restarts the interface, it’s fine. It just fails on reboot, every single time.
I hope with “exact same” you don’t mean the IP address…
But well, try to edit/compare the config file directly, maybe there is a difference?
The config is stored in /etc/sysconfig/network/ifcfg-xxxx
I remember a bug in YaST where it just “forgot”/overwrote the default gateway, I got bitten by that one once and suddenly couldn’t reach the remote server I was logged into anymore…:X