ATLAS Support Center

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Using Ethernet Connection to HSIO-2 Board and WiFi Simultaneously ======

When using an ethernet cable to hook up a computer with the HSIO-2 board, you may find that your wi-fi connection stops working. The reason for this is that your computer thinks both the wi-fi and ethernet connection are methods of connecting to the internet. As ethernet is generally faster than wi-fi, the computer will automatically ignore the wi-fi and start trying to use the ethernet port for internet stuff. The HSIO-2 board receives this info, doesn't know what to do with it, and just throws it away.

Here's how to fix it: Open up terminal and type: <code>route -n</code> You should see something like the following:

<code>
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.3.1     0.0.0.0         UG    100    0        0 enp1s7
0.0.0.0         130.202.2.1     0.0.0.0         UG    600    0        0 wlp0s2f1u5
1.1.1.1         130.202.2.1     255.255.255.255 UGH   600    0        0 wlp0s2f1u5
130.202.2.0     0.0.0.0         255.255.254.0   U     600    0        0 wlp0s2f1u5
192.168.3.0     0.0.0.0         255.255.255.0   U     100    0        0 enp1s7
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
</code>

If you want to learn about networking and IP addresses and things like that, [[http://www.aboutdebian.com/network.htm|the first section of this]] is a really nice and easy read. It will probably make your life easier in the future if you do a lot of computer stuff, but you don't have to read it. Anyway, what we see here is that the ethernet connection (here named enp1s7) has a metric of 100. Since this is lower than the metric of 600 used by the wifi, the computer automatically tries to use that connection. We need to set it to something higher. Type the following commands (if the IP address you see is different, be sure to use that instead).

<code>
route del default gw 192.168.3.1
route add default gw 192.168.3.1 metric 1000
</code>

Now if we look at our connections again with: <code>route -n</code> we'll see that everything is fixed and we can use our wifi again!

<code>
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         130.202.2.1     0.0.0.0         UG    600    0        0 wlp0s2f1u5
0.0.0.0         192.168.3.1     0.0.0.0         UG    1000   0        0 enp1s7
1.1.1.1         130.202.2.1     255.255.255.255 UGH   600    0        0 wlp0s2f1u5
130.202.2.0     0.0.0.0         255.255.254.0   U     600    0        0 wlp0s2f1u5
192.168.3.0     0.0.0.0         255.255.255.0   U     100    0        0 enp1s7
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
</code>

This needs to be done every time you connect the ethernet cable.
ATLAS Support Center

User Tools

Site Tools

Page Tools
