This can be done with a NM dispatcher script if desired.
For example
On 2015-06-02 23:46, deano ferrari wrote:
>
> robin_listas;2713364 Wrote:
>>
>> My intention is to configure cable connection to disconnect wifi
>> connection. Define priorities.
> This can be done with a NM dispatcher script if desired.
>
> For example
>
> http://tinyurl.com/qddsj6l
Interesting, thanks.
I’ll have to think it over, it is another modification to the system.
One reason I do not want both interfaces active, is that both have
configured the same IP. I access the laptop from other machines by name
sometimes, and that needs the IP not change, regardless what interface.
(With different IPs, I get martians if both connected. But it works, yes).
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Okay then. Switched back to Network Manager and can no longer ping my router. That’s okay, I pulled up my connections and took a look at “Wired connection 1.” The route command does not give promising results, but maybe they’ll be informative. If we’ve already determined that the network interface is installed correctly, I can only imagine that my settings are missing something.
My settings (Big picture) http://i.imgur.com/Vev5ocz.png
You’ve assigned an incorrect gateway in NM. It needs to be 192.168.0.1 (your router’s internal IP address). Be aware, if you’re assigning static IP addresses, you’ll need to take care of the name server assignment too (in /etc/resolv.conf).
Okay, that’s good to know. I am curious though, why does my router say that the Gateway Address is 24.32.192.1 if that’s not the number I should be using?
Either way, I have checked my /etc/resolv.conf and found that I hve already taken care of the nameserver assignment.
/etc/resolve.conf:
nameserver 208.180.42.68
So in the past few minutes, I’ve tried this two different ways. Once with a static IP address and once just using DHCP and leaving the settings blank. Both seem to give similar results. The IP routing table is not blank anymore, so changing the gateway address seems to have fixed that.
DHCP settings (in Network Manager)
Method: Automatic (DHCP)
Address: BLANK
Netmask: BLANK
Gateway: BLANK
Additional DNS Servers: 208.180.42.68, 208.180.42.100
Routes ALL BLANK
Reults
anthony@opensuseamdfx:~> /sbin/route -nKernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 1024 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 192.168.0.1 255.255.255.0 UG 1 0 0 eth0
anthony@opensuseamdfx:~> ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=5.80 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.572 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.566 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.536 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.545 ms
^C
--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 0.536/1.605/5.809/2.102 ms
anthony@opensuseamdfx:~> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 5999ms
anthony@opensuseamdfx:~> ping www.google.com
^Canthony@opensuseamdfx:~≥
Static IP
Method: Manual
Address: 192.168.0.50
Netmask: 255.255.255.0
Gateway: 192.168.0.1
Additional DNS Servers: 208.180.42.68, 208.180.42.100
Routes ALL BLANK
Results
anthony@opensuseamdfx:~> /sbin/route -nKernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 1024 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 192.168.0.1 255.255.255.0 UG 1 0 0 eth0
anthony@opensuseamdfx:~> ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.554 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.557 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.547 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.546 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.536 ms
^C
--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.536/0.548/0.557/0.007 ms
anthony@opensuseamdfx:~> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 5999ms
anthony@opensuseamdfx:~> ping [www.google.com](http://www.google.com)
anthony@opensuseamdfx:~>
In both cases, I was able to ping my router, but not 8.8.8.8 or google. Oddly, pinging Google doesn’t even give me a failure message. It just freezes and waits for me to press Ctrl+C
That’s the router’s external gateway address. You’re connected to the LAN side (internal network) of the router.
Your routing table doesn’t look right. You have two gateway flags set, and the ‘1024’ metric doesn’t make sense to me either. I don’t understand the last entry. It should look more like this
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 9 0 0 eth0
On 2015-06-05 18:46, anthony62490 wrote:
> Okay, that’s good to know. I am curious though, why does my router say
> that the Gateway Address is 24.32.192.1 if that’s not the number I
> should be using?
That’s the gateway that the router uses to connect, outside, to the rest
of the world. The router for your router, let’s say. Your little inside
world uses the router as gateway (192.168.0.1), and this router-gateway
sends to 24.32.192.1. Like a bucket brigade 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Okay, I’ve had a chance to review/test this a little more thoroughly and I think the routing table is okay. I’m wondering whether your router is properly connected to the internet though. Do other devices have working internet access via this router?
Every other device that goes through this router can connect to the internet just fine. In fact, this computer had the Windows 10 preview installed on it previously and it worked just fine. I know you said it was okay, but I will still see about cleaning up the routing table and I’ll see if that helps.
Is there anything else I can supply that would help get to the bottom of this? I have never had this much trouble with a network connection before.
Can you demonstrate current working connecitvity with any other device? For example, a smart phone with wireless connectivity? Does the router staus lights suggest all is okay? Doe it have a diagnostic page that can be used to check status?
Try restarting the router and see if you can get a working internet connection established (with DHCP).
ip addr
ip route
Yes, everything appears to be okay on the router’s end. Several devices are connected with wired and wireless connections
All of the devices are using DHCP and they all appear to be working correctly. The router has been reset a few times since this problem arose.
anthony@opensuseamdfx:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether fc:aa:14:2f:c5:16 brd ff:ff:ff:ff:ff:ff
anthony@opensuseamdfx:~> ip route
anthony@opensuseamdfx:~>
Thanks for reporting back with that info, and maybe confirm network status
systemctl -p Id show network.service
systemctl status network
It might be useful to trawl the journal log for messages related to the networking.
anthony@opensuseamdfx:~> systemctl -p Id show networkork.serviceId=networkork.service
anthony@opensuseamdfx:~> systemctl status network
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Wed 2015-06-10 23:03:37 CDT; 1h 10min ago
Main PID: 776 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─776 /usr/sbin/NetworkManager --no-daemon
anthony@opensuseamdfx:~>
Looked at the log journal. THAT is a lot to look through. I am leaving for a trip tomorrow, but when I get back, I will take a look at the journal. Are there any keywords I should be paying attention for?
[QUOTE=anthony62490;2714595]
anthony@opensuseamdfx:~> systemctl -p Id show networkork.serviceId=networkork.service
anthony@opensuseamdfx:~> systemctl status network
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Wed 2015-06-10 23:03:37 CDT; 1h 10min ago
Main PID: 776 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─776 /usr/sbin/NetworkManager --no-daemon
anthony@opensuseamdfx:~>
Strange… I don’t see any dhcp client running. For reference, take a look at mine.
For reference, I get
# systemctl status network
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Thu 2015-06-11 12:00:22 NZST; 8h ago
Main PID: 588 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─ 588 /usr/sbin/NetworkManager --no-daemon
└─7761 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-client.action -pf /var/run/dhclient-wlan0.pid -lf...
IMO
Troubleshooting has gone a bit of a tangent.
Established:
This is the only machine that is having problems connecting to the Internet. Other machines have no problem.
So, the problem is narrowed very specifically…
Most likely issue is that the DG and network settings for the machine are not configured correctly. Post the following if you don’t know how to interpret
On both the problem machine and a working machine
ip addr
route show
Use traceroute to determine your problem
The assigned address somehow is being blocked at the router (you should be able to test whether this is the case pretty easily with
traceroute 8.8.8.8
If the above pings your router but nothing further, then you need to look at your IP forwarding rules. Maybe your configured IP address is incorrectly outside your defined subnetted network. Maybe it’s just a simple typo.
If the above doesn’t even ping your router, then the problem is definitely in that local machine’s network, and specifically the GW configuration.
If your traceroute test works fine and reliably, then you should probably turn your attention to name resolution issues.
TSU
@Tsu: The address/gatway information already been requested and you’ll observe that they are not set, even though the OP claims to have configured a DHCP connection. They appear to have changed from wicked to NM in the course of this thread as well. Of course, it may be that the connection is not configured properly. It would be useful to verify the OP’s NM connection as defined in the
/etc/NetworkManager/system-connections/ directory.
anthony@opensuseamdfx:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether fc:aa:14:2f:c5:16 brd ff:ff:ff:ff:ff:ff
anthony@opensuseamdfx:~> sudo route show
Usage: route -nNvee] -FC] <AF>] List kernel routing tables
route -v] -FC] {add|del|flush} ... Modify routing table for AF.
route {-h|--help} <AF>] Detailed usage syntax for specified AF.
route {-V|--version} Display version/author and exit.
-v, --verbose be verbose
-n, --numeric don't resolve names
-e, --extend display other/more information
-F, --fib display Forwarding Information Base (default)
-C, --cache display routing cache instead of FIB
<AF>=Use '-A <af>' or '--<af>'; default: inet
List of possible address families (which support routing):
inet (DARPA Internet) inet6 (IPv6) ax25 (AMPR AX.25)
netrom (AMPR NET/ROM) ipx (Novell IPX) ddp (Appletalk DDP)
x25 (CCITT X.25)
Okay, this is interesting. This command comes back as invalid. The same thing happens with “sudo route show 192.168.0.1”
anthony@opensuseamdfx:~> sudo traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
connect: Network is unreachable
That’s… a bit concerning. Any idea how I might remedy that? I don’t recall disabling anything, but if this is supposed to be enabled by default, I could try reinstalling.
Sorry, should have made it more clear. I switched to NM at the suggestion of a previous poster.
anthony@opensuseamdfx:/etc/NetworkManager/system-connections> sudo nano suddenlink.net-5AA0
[connection]
id=suddenlink.net-5AA0
uuid=39574d67-63d7-46e8-a67e-230f10c5afd6
type=wifi
permissions=user:anthony:;
timestamp=1432397243
[wifi]
ssid=suddenlink.net-5AA0
mode=infrastructure
mac-address=80:1F:02:A2:C7:F2
security=802-11-wireless-security
[wifi-security]
key-mgmt=wpa-psk
psk=13507509507332
[ipv4]
method=auto
[ipv6]
method=auto
ip6-privacy=0
anthony@opensuseamdfx:/etc/NetworkManager/system-connections> sudo nano Wired\ connection\ 1
[ethernet]
duplex=full
mac-address=FC:AA:14:2F:C5:16
[connection]
id=Wired connection 1
uuid=42085124-6619-4dc2-acc5-ec4275a66c3b
type=ethernet
timestamp=1433876540
[ipv6]
method=auto
ip6-privacy=0
[ipv4]
method=manual
dns=208.180.42.68;208.180.42.100;
address1=192.168.0.50/24,192.168.0.1
may-fail=false
Okay, your wireless connection looks essentially as I’d expect, (although I have mine set up as a system connection - 'All users may connect to this network). Your wired connection is as a ‘Manual’ connection , using static IP addresses. That explains why dhclitent wasn’t running. I think you should try an ‘Automatic’ connection, which will use DHCP to assign the necessary addresses and DNS assignments as well.
Okay, I’m a dumbass. Disregard that previous post. After getting back from my trip, I forgot to plug in my ethernet cable, so some of those results are not correct. I have changed my connection to Automatic, deleted the wireless profile, and this is what I come up with:
anthony@opensuseamdfx:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether fc:aa:14:2f:c5:16 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.50/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::feaa:14ff:fe2f:c516/64 scope link
valid_lft forever preferred_lft forever
“route show” is still invalid for some reason
anthony@opensuseamdfx:~> sudo traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 11.204 ms 11.289 ms 11.368 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
anthony@opensuseamdfx:/etc/NetworkManager/system-connections> sudo nano Wired\ connection\ 1
[ethernet]
duplex=full
mac-address=FC:AA:14:2F:C5:16
[connection]
id=Wired connection 1
uuid=42085124-6619-4dc2-acc5-ec4275a66c3b
type=ethernet
timestamp=1434676446
[ipv6]
method=auto
ip6-privacy=0
[ipv4]
method=auto
dns=208.180.42.68;208.180.42.100;
may-fail=false