with the ifup method everything works fine. But now I bought a wireless card, so I prefer to use the network manager to manage my connection.
On my computer I need a static IP for wired connection, so I created a new wired connection and I called it “wired connection”. But network manager always connect automatically to “Auto eth0” and I can’t find how to modify this connection. Setting “wired connection” as default didn’t change anything, probably becouse it need me to unlock the default wallet…
Now, another problem, I really don’t know why network manager applet doesn’t appear on system tray, but I’m sure that I’m using it instead of the ifup method.
First get the wireless card working using ifup (see YAST->Network). Once you can use the wireless card using ifup go back to YAST->network and change it to networkmanager. Then using network manager modify the settings to point at the wireless instead of eth0.
I can connect with wifi card. But I’ll use wifi only sometimes, mostly I’ll use wired.
My problem, actually, is to set the wired connection with network manager. It automatically connect to eth0 using dhcp. I can’t find how to modify this automatic connection, so I created a new one with static ip address and I set this as default connection.
But network manager continue to automatically connect to eth0 instead of the connection that I have created.
I can’t do what you said becouse the automatic connection that nm create isn’t in the lits of connection when I open the nm. I can see only the one that I made manually. I can modify only that one and I checked the box “connect automatically”.
Nothing happen. It continue to connect via “auto eth0” (that is the one that it consider the default).
As I understand you, you created a eth1 using NetworkManager with a static IP address but a eth0 connection is still the default and starts automatically?
After running ifconfig -a you should try
:~> ifdown eth0
:~> ip link set eth0 down
to make sure eth0 is down then use NetworkManager to start eth1 with its static IP.
If eth0 is connected through a router maybe you can set the router to always use the Static IP for the MAC address of eth0 using DHCP. Reserve DHCP IP addressing.
Then, when I click on nm and select the connection I created (for example: “mickey mouse”, it ask me the password of the wallet and then this is the output of ifconfig:
Thanks. IMO, the change to IP address (and the log file) indicates that NetworkManager does change something.
Stupid me, in NetworkManager you do change the IPv4 Settings from Automatic DHCP to Manual?
Does the 2nd output have the correct static address? Did you check auto connect for the Wireless Connection 1?
In the posts before the output I think you write that you add a new eth0 and check auto connect?
Yes. I did. But I did it only for the connection that I created. I can’t modify the connection that the network manager automatically create becouse it doesn’t appear in the list.
Yes, the second output has the correct ip address becouse it is static. While the first output (with “auto eth0”) can change, it depends on how many client are associated with the router. I didn’t check autoconnect for the wireless connection becouse I want wired one to auto connect but with static ip address.
And yes. I added a new connection for eth0, but with static ip. Auto connect is checked but doesn’t work.
I didn’t understand why when i select the wired connection that I added it ask me to unlock the default wallet. There is no password for the connection…
I don’t know about the wallet, why it’s asking for a pword, etc.
I think the only time we see messages as you have in /var/log/NetworkManager is when there’s errors, like /etc/NetworkManager/dispatcher.d/autofs failing.
I think the autofs exit 1, means that some mounted device either failed to load or failed to unload. I don’t know it that’s your problem or not.
Try
sudo rcnetwork restart
This restarts the init process for the network and maybe it’ll provide details. Then check output from tail -n 30 /var/log/messages and tail -n 30 /var/log/NetworkManager again.
I’ll take another look at your /var/log/NetworkManager output but I’m at a loss, ie, it should’ve worked but it’s not.
Nov 29 14:41:03 francesco-desktop avahi-daemon[1949]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.8.
Nov 29 14:41:03 francesco-desktop avahi-daemon[1949]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov 29 14:41:03 francesco-desktop ifdown: wlan0 device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
Nov 29 14:41:03 francesco-desktop ifdown: No configuration found for wlan0
Nov 29 14:41:03 francesco-desktop ifdown: Nevertheless the interface will be shut down.
Nov 29 14:41:05 francesco-desktop rcnetwork: Starting the NetworkManager
Nov 29 14:41:05 francesco-desktop kernel: 6147.129769] eth0: setting full-duplex.
Nov 29 14:41:05 francesco-desktop kernel: 6147.156445] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 29 14:41:05 francesco-desktop dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Nov 29 14:41:05 francesco-desktop dhclient: Copyright 2004-2010 Internet Systems Consortium.
Nov 29 14:41:05 francesco-desktop dhclient: All rights reserved.
Nov 29 14:41:05 francesco-desktop dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov 29 14:41:05 francesco-desktop dhclient:
Nov 29 14:41:05 francesco-desktop dhclient: Listening on LPF/eth0/00:11:d8:97:61:63
Nov 29 14:41:05 francesco-desktop dhclient: Sending on LPF/eth0/00:11:d8:97:61:63
Nov 29 14:41:05 francesco-desktop dhclient: Sending on Socket/fallback
Nov 29 14:41:06 francesco-desktop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Nov 29 14:41:06 francesco-desktop dhclient: DHCPOFFER from 192.168.1.1
Nov 29 14:41:11 francesco-desktop dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Nov 29 14:41:11 francesco-desktop dhclient: DHCPACK from 192.168.1.1
Nov 29 14:41:11 francesco-desktop dhclient: bound to 192.168.1.8 -- renewal in 34347 seconds.
Nov 29 14:41:11 francesco-desktop avahi-daemon[1949]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.8.
Nov 29 14:41:11 francesco-desktop avahi-daemon[1949]: New relevant interface eth0.IPv4 for mDNS.
Nov 29 14:41:11 francesco-desktop avahi-daemon[1949]: Registering new address record for 192.168.1.8 on eth0.IPv4.
Nov 29 14:41:12 francesco-desktop if-up.d/21-dhcpcd-hook-samba: No dhcpcd info nor dhclient leases file found for eth0.
Nov 29 14:41:12 francesco-desktop SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Nov 29 14:41:12 francesco-desktop SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Nov 29 14:41:12 francesco-desktop SuSEfirewall2: using default zone 'ext' for interface wlan0
Nov 29 14:41:12 francesco-desktop SuSEfirewall2: batch committing...
Nov 29 14:41:12 francesco-desktop SuSEfirewall2: Firewall rules successfully set
And this one for the Network Manager
tail -30 /var/log/NetworkManager
Nov 29 14:41:05 francesco-desktop NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Nov 29 14:41:05 francesco-desktop NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Nov 29 14:41:05 francesco-desktop NetworkManager: <WARN> user_connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus).
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> address 192.168.1.8
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> prefix 24 (255.255.255.0)
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> gateway 192.168.1.1
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> nameserver '193.70.152.15'
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> nameserver '193.70.152.25'
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> domain name 'WAG160N'
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Nov 29 14:41:11 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.031437] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.033260] write_to_netconfig(): Writing to netconfig: INTERFACE='eth0'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.033391] write_to_netconfig(): Writing to netconfig: DNSSEARCH='WAG160N WAG160N'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.033434] write_to_netconfig(): Writing to netconfig: DNSSERVERS='193.70.152.15 193.70.152.25'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> Clearing nscd hosts cache.
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.038676] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.041605] write_to_netconfig(): Writing to netconfig: INTERFACE='eth0'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.041710] write_to_netconfig(): Writing to netconfig: DNSSEARCH='WAG160N WAG160N'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <debug> [1291038072.041749] write_to_netconfig(): Writing to netconfig: DNSSERVERS='193.70.152.15 193.70.152.25'#012
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> Clearing nscd hosts cache.
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> Activation (eth0) successful, device activated.
Nov 29 14:41:12 francesco-desktop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Nov 29 14:41:12 francesco-desktop nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1
Well, the only other choices I have is to check YaST2 | “Network Settings” | make sure that NetworkManager is selected to control your network settings and not ifup/ifdown.
Install ‘plasmoid networkmanagement’, it will cause uninstall of ‘Networkmanager-kde4’ but that’s OK.
BTW. AFAIK the Networkmanager will alway choose the fastest way out, so as soon as you have a wired physical connection it will build a connection ‘aut eth0’.
Things should work with default settings.
One thing you can try: create a new user, login as that new user, see how things behave. If behaviour for the new user is OK, then please report it here.
I had a similar problem: a laptop with a wired and a wireless connection for which my preference was to use the wireless except when the wired connection was plugged in. Using Opensuse 11.3, KDE, Network Manager, the system always preferred the wired connection even if it wasn’t plugged in. I had to right click on the Network Manager and click my wireless network to override. (Only a couple of clicks, but what an annoyance!) However, the solution I found was as follows:
Open YAST | Network Settings, click ok to the warning about Network Manager and change to “traditional using IFUP”. Switch to the Overview tab. Both my wired and wireless connections were displayed with an IP address of “not configured”. At the bottom of the screen, the summary also reports “this device is not configured. Press edit to configure”. So, select the wired connection and click “edit” to configure. On the General tab, make sure the “activate device” drop down says “on cable connection” and then click “next”. click “ok” and the settings will be saved - you will get a warning message about Network Manager. Open YAST | Network Settings again and switch back to “user controlled with Network Manager”, click “ok”. In my case this crashed Network Manager, just click ok or whatever to the bug report, and then ok in the next YAST warning message. Reboot and all should be ok, i.e. in my case, the wireless connection fires up every time. When I plug the cable into the wired socket, this overrides the wireless, and when I pull the cable out, the wireless takes over again.
I don’t know whether this is just “normal” behaviour or if it is indicative of a bug (with the above workaround) or whether it could possibly be an area for enhancement (somewhere – I am not sure where). Other forum posters (here and elsewhere) have indicated that there is grey area of overlap (underlap?) between IFUP settings and Network Manager settings.
On 12/01/2010 11:06 AM, choslimi wrote:
>
> I had a similar problem: a laptop with a wired and a wireless connection
> for which my preference was to use the wireless except when the wired
> connection was plugged in. Using Opensuse 11.3, KDE, Network Manager,
> the system always preferred the wired connection even if it wasn’t
> plugged in. I had to right click on the Network Manager and click my
> wireless network to override. (Only a couple of clicks, but what an
> annoyance!) However, the solution I found was as follows:
>
> Open YAST | Network Settings, click ok to the warning about Network
> Manager and change to “traditional using IFUP”. Switch to the Overview
> tab. Both my wired and wireless connections were displayed with an IP
> address of “not configured”. At the bottom of the screen, the summary
> also reports “this device is not configured. Press edit to configure”.
> So, select the wired connection and click “edit” to configure. On the
> General tab, make sure the “activate device” drop down says “on cable
> connection” and then click “next”. click “ok” and the settings will be
> saved - you will get a warning message about Network Manager. Open YAST
> | Network Settings again and switch back to “user controlled with
> Network Manager”, click “ok”. In my case this crashed Network Manager,
> just click ok or whatever to the bug report, and then ok in the next
> YAST warning message. Reboot and all should be ok, i.e. in my case, the
> wireless connection fires up every time. When I plug the cable into the
> wired socket, this overrides the wireless, and when I pull the cable
> out, the wireless takes over again.
>
> I don’t know whether this is just “normal” behaviour or if it is
> indicative of a bug (with the above workaround) or whether it could
> possibly be an area for enhancement (somewhere – I am not sure
> where). Other forum posters (here and elsewhere) have indicated that
> there is grey area of overlap (underlap?) between IFUP settings and
> Network Manager settings.
The problem was due to the use of the traditional method sometime during the
lifetime of your system, which created the file
/etc/sysconfig/network/ifcfg-eth0. As this file is read during bootup (long
before NM is started), its settings will override some things in NM. Another
workaround would have been to delete the above file.
You are quite correct in that I have used the traditional method during the lifetime of my system (I have just reached the end of my nightmare trying to get the wireless to work using the advice of you and others posted in these forums). And I fully admit that I do not have the technical knowledge to articulate my observations in sufficient detail. But, as with Zagorax in post #1 and #3 and #5 leading ultimately to #16, it seems that NM is trying to use a connection that - as a NM user - I do not want it to use and - as a NM user - I don’t seem to be able to use NM to alter NM’s behaviour. That seems to me to be a bug, or something that could/should be improved/enhanced.
And, lwfinger, many thanks for you regular contributions to these forums without which I would not be able to use my wireless connection to post this message!
