Please, no flames. I went into the yast2 gui and changed the network setup from Network Manager to Wicked. All appeared happy until I went to firefox. If I clicked on google, it came up and performed the search I requested. But when I tried to load one of these, opensuse.org, I received an "unable to Connect" failure. All of the name servers I had previously listed for wicked are grayed out under Network manager, so I am curious if the ones I had listed are not correct, or I listed them improperly. Also, what should be in Domain Search field? Comcast, my ISP provides the following: Domain Name: hsd1.az.comcast.net -- is what I put in domain search DNS1: 75.75.75.75 DNS2: 75.75.76.76 When I do a ifconfig I get: ifconfig enp9s0 Link encap:Ethernet HWaddr 34:E6:D7:01:2A:DD inet addr:192.168.7.56 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fe80::36e6:d7ff:fe01:2add/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6550 errors:0 dropped:0 overruns:0 frame:0 TX packets:5126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3477529 (3.3 Mb) TX bytes:916184 (894.7 Kb) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:435 errors:0 dropped:0 overruns:0 frame:0 TX packets:435 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:44663 (43.6 Kb) TX bytes:44663 (43.6 Kb) wlp11s0 Link encap:Ethernet HWaddr C0:38:96:60:41:79 inet addr:192.168.7.55 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fda6:1c9c:a527:0:c238:96ff:fe60:4179/64 Scope:Global inet6 addr: 2601:5:a100:7c:b063:134f:a462:95fb/64 Scope:Global inet6 addr: fda6:1c9c:a527:0:b063:134f:a462:95fb/64 Scope:Global inet6 addr: 2601:5:a100:7c:c238:96ff:fe60:4179/64 Scope:Global inet6 addr: fe80::c238:96ff:fe60:4179/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6815 errors:0 dropped:0 overruns:0 frame:0 TX packets:1682 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1667635 (1.5 Mb) TX bytes:341085 (333.0 Kb) Anything obvious I am doing wrong? If I go back to Network Manager the system works again. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue 21 Apr 2015 04:49:55 PM CDT, don fisher wrote:
Please, no flames. I went into the yast2 gui and changed the network setup from Network Manager to Wicked. All appeared happy until I went to firefox. If I clicked on google, it came up and performed the search I requested. But when I tried to load one of these, opensuse.org, I received an "unable to Connect" failure. All of the name servers I had previously listed for wicked are grayed out under Network manager, so I am curious if the ones I had listed are not correct, or I listed them improperly. Also, what should be in Domain Search field?
Comcast, my ISP provides the following:
Domain Name: hsd1.az.comcast.net -- is what I put in domain search DNS1: 75.75.75.75 DNS2: 75.75.76.76
When I do a ifconfig I get:
ifconfig enp9s0 Link encap:Ethernet HWaddr 34:E6:D7:01:2A:DD inet addr:192.168.7.56 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fe80::36e6:d7ff:fe01:2add/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6550 errors:0 dropped:0 overruns:0 frame:0 TX packets:5126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3477529 (3.3 Mb) TX bytes:916184 (894.7 Kb) Interrupt:18
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:435 errors:0 dropped:0 overruns:0 frame:0 TX packets:435 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:44663 (43.6 Kb) TX bytes:44663 (43.6 Kb)
wlp11s0 Link encap:Ethernet HWaddr C0:38:96:60:41:79 inet addr:192.168.7.55 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fda6:1c9c:a527:0:c238:96ff:fe60:4179/64 Scope:Global inet6 addr: 2601:5:a100:7c:b063:134f:a462:95fb/64 Scope:Global inet6 addr: fda6:1c9c:a527:0:b063:134f:a462:95fb/64 Scope:Global inet6 addr: 2601:5:a100:7c:c238:96ff:fe60:4179/64 Scope:Global inet6 addr: fe80::c238:96ff:fe60:4179/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6815 errors:0 dropped:0 overruns:0 frame:0 TX packets:1682 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1667635 (1.5 Mb) TX bytes:341085 (333.0 Kb)
Anything obvious I am doing wrong? If I go back to Network Manager the system works again.
Don Hi You can't have both wireless and ethernet running, turn one off...
-- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default up 3 days 12:50, 3 users, load average: 0.35, 0.22, 0.16 CPU AMD A4-5150M APU @ 3.3GHz | GPU Richland Radeon HD 8350G -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, April 21, 2015 08:37:18 PM Malcolm wrote:
Hi You can't have both wireless and ethernet running, turn one off...
Wait, what? Is that a limitation of Wicked? I only ask because I've never heard of that being an issue before. -Garheade www.romerotools.net
On Tue, 21 Apr 2015 22:17:58 -0400 Gary Romero wrote:
On Tuesday, April 21, 2015 08:37:18 PM Malcolm wrote:
Hi You can't have both wireless and ethernet running, turn one off...
Wait, what? Is that a limitation of Wicked? I only ask because I've never heard of that being an issue before.
Please don't take his answer out of context. It certainly takes a unique configuration to achieve seamless parallel connections (one wired, one wireless) to the same network on two IP addresses. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed 22 Apr 2015 02:57:38 AM CDT, Carl Hartung wrote:
On Tue, 21 Apr 2015 22:17:58 -0400 Gary Romero wrote:
On Tuesday, April 21, 2015 08:37:18 PM Malcolm wrote:
Hi You can't have both wireless and ethernet running, turn one off...
Wait, what? Is that a limitation of Wicked? I only ask because I've never heard of that being an issue before.
Please don't take his answer out of context. It certainly takes a unique configuration to achieve seamless parallel connections (one wired, one wireless) to the same network on two IP addresses. Hi Yes, since both are on the same network I assumed the OP was running either one or the other with Network Manager. I have four interfaces running on one system/network with wicked, except three are bridged devices....
-- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default up 3 days 14:57, 3 users, load average: 0.13, 0.18, 0.20 CPU AMD A4-5150M APU @ 3.3GHz | GPU Richland Radeon HD 8350G -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/21/2015 07:57 PM, Carl Hartung wrote:
On Tue, 21 Apr 2015 22:17:58 -0400 Gary Romero wrote:
On Tuesday, April 21, 2015 08:37:18 PM Malcolm wrote:
Hi You can't have both wireless and ethernet running, turn one off...
Wait, what? Is that a limitation of Wicked? I only ask because I've never heard of that being an issue before.
Please don't take his answer out of context. It certainly takes a unique configuration to achieve seamless parallel connections (one wired, one wireless) to the same network on two IP addresses.
I have made some progress. I added the wireless device name as the routing device and now it appears to work. But that leaves a bit of work if I take my laptop where the cable is required. Do I really have to change the routing device every time I plug the cable in? Shouldn't it just know that the routing device is the active network interface? There is an option to enable the cable interface on cable insertion. Is there a way to disable the wireless interface on cable insertion? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 21 april 2015 20:58:34 schreef don fisher:
On 04/21/2015 07:57 PM, Carl Hartung wrote:
On Tue, 21 Apr 2015 22:17:58 -0400
Gary Romero wrote:
On Tuesday, April 21, 2015 08:37:18 PM Malcolm wrote:
Hi You can't have both wireless and ethernet running, turn one off...
Wait, what? Is that a limitation of Wicked? I only ask because I've never heard of that being an issue before.
Please don't take his answer out of context. It certainly takes a unique configuration to achieve seamless parallel connections (one wired, one wireless) to the same network on two IP addresses.
I have made some progress. I added the wireless device name as the routing device and now it appears to work. But that leaves a bit of work if I take my laptop where the cable is required. Do I really have to change the routing device every time I plug the cable in? Shouldn't it just know that the routing device is the active network interface? There is an option to enable the cable interface on cable insertion. Is there a way to disable the wireless interface on cable insertion?
Don
There is a priority field associated with each interface, which goes with On cable connection. So you give the wireless a lower priority, in which case the wireless will not be active when the cable is connected. When the cable is not connected the wireless will be active. It is more or less explained in the help of YaST in the network module. -- 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 04/22/2015 01:09 AM, Freek de Kruijf wrote:
Op dinsdag 21 april 2015 20:58:34 schreef don fisher: There is a priority field associated with each interface, which goes with On cable connection. So you give the wireless a lower priority, in which case the wireless will not be active when the cable is connected. When the cable is not connected the wireless will be active. It is more or less explained in the help of YaST in the network module.
I looked at the help fields in each of the Yast2 windows. Do you know if 0 or 1 is the highest priority? Also it says that the "-" is an alias for any interface, but I tried that again and it still does not work. That assumption caused my original problem. The any interface would make sense because I would like the cable to have preference over wifi, if I have the cable available, and the "-" would allow the routing device to switch. I realize this is only a problem for laptops, which may be an endangered species due to touch pads and social media. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 22 april 2015 10:10:51 schreef don fisher:
On 04/22/2015 01:09 AM, Freek de Kruijf wrote:
Op dinsdag 21 april 2015 20:58:34 schreef don fisher: There is a priority field associated with each interface, which goes with On cable connection. So you give the wireless a lower priority, in which case the wireless will not be active when the cable is connected. When the cable is not connected the wireless will be active. It is more or less explained in the help of YaST in the network module.
I looked at the help fields in each of the Yast2 windows. Do you know if 0 or 1 is the highest priority? Also it says that the "-" is an alias for any interface, but I tried that again and it still does not work. That assumption caused my original problem. The any interface would make sense because I would like the cable to have preference over wifi, if I have the cable available, and the "-" would allow the routing device to switch. I realize this is only a problem for laptops, which may be an endangered species due to touch pads and social media.
You need to specify "On Cable Connection", even for the wireless interface. In this case, if it has the highest priority, it needs to be able to connect to an AP, otherwise a lower priority interface will be used. Only one interface, typed "On Cable Connection" will become active, however it also needs to have a priority != 0. So look in /etc/sysconfig/network/ifcfg-<interface> for STARTMODE='ifplugd' and IFPLUGD_PRIORITY= The higher the numeric value, the higher the priority. So most likely you give wireless priority 1 and cable priority 2. -- 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 04/22/2015 03:02 PM, Freek de Kruijf wrote:
You need to specify "On Cable Connection", even for the wireless interface. In this case, if it has the highest priority, it needs to be able to connect to an AP, otherwise a lower priority interface will be used. Only one interface, typed "On Cable Connection" will become active, however it also needs to have a priority != 0.
So look in /etc/sysconfig/network/ifcfg-<interface> for STARTMODE='ifplugd' and IFPLUGD_PRIORITY= The higher the numeric value, the higher the priority. So most likely you give wireless priority 1 and cable priority 2.
I did specify on cable connection for both interfaces. I read in the man page that it should mean it found the service, but that it did not work well. I will go to the text file and exit the IFPLUGD_PRIORITY for both ports. I did find that the /etc/sysconfig/network/routes file was empty, the the one on my other machine has: default 192.168.7.1 - - in it. So I updated my routes file and tried the "-" interface option again, and again had failure. The system is working, not just the way I think it should. I am going on to other adventures and let somebody that understands networking a lot more than me stumble upon this, and hopefully fix it:-) Thanks for your help, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carl Hartung -
don fisher -
Freek de Kruijf -
Gary Romero -
Malcolm