This can be caused by bad internet and/or cable connections or even overly aggressive firewalls
Updated on December 1, 2022
Shortcut Options
- Test the IPv6 connection to determine the default gateway IP, then compare it to the device’s configured gateway via netshell IP settings.
- Add a gateway: LAN settings > Internet Protocol Version 6 (TCP/IPv6) > Properties. Change Default Gateway to the correct address.
- To check if the error is resolved, enter a ping test in Command Prompt: C:UsersMe>ping -6 151.101.194.114.
This article explains how to fix a destination host unreachable error on Windows devices, as well as how to add the correct gateway address for a destination host, and how to confirm the error is resolved.
What Causes a Destination Host Unreachable Error?
There are many possible reasons for getting a “destination host unreachable” error, including things as simple as erroneously connected cables or an overly aggressive firewall.
As you can see from the details below, we’re trying to ping a specific network device IP address, but the response we’re getting doesn’t provide much detail beyond the error itself:
C:UsersMe>ping 151.101.194.114
Pinging 151.101.194.114 with 64 bytes of data:
Reply from 151.101.194.114: Destination host unreachable
So, what’s going on here? In simple terms, we’re trying to communicate with a device at the specified IP address, but the remote gateway is unable to direct our ping request to the host itself, and so it sends an echo message back to say that it can’t be found.
How to Fix a Destination Host Unreachable Error
In diagnosing the error, it’s useful to follow the steps to fix an IPv6 error first to see if they resolve your networking issues. If the problem persists, you need to look at your network infrastructure to establish where the issue is.
For this example, we’re going to check our Default Gateway settings, then follow the steps to fix them.
-
To start, we need to check our internet connection via a browser. For this example, we’ll check google.com to see if it loads on our device. If it does, we know there’s a problem on our local network, rather than a broader connection issue.
-
Next, we’re going to test our IPv6 connection to see if that’s where the issue lies. To do this, open the Command Prompt and use the following command to ping your original IP address, but type «ping -6» to isolate the IPv6 line.
C:UsersMe>ping -6 151.101.194.114
-
You should get a reply in the Command Prompt, which looks like this:
Pinging 151.101.194.114 with 64 bytes of data:
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
-
The above reply comes from IP address 151.101.194.1.241, which seems to relate to the remote gateway handling our request. To check this, run a traceroute using the following command:
C:UsersMe>tracert -6 -d 151.101.194.114
-
You should get a response, and it should resemble the following:
Tracing route 151.101.194.114 over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 151.101.194.1.241
2 151.101.194.1.241 reports: Destination host unreachable.
Trace complete.
-
From this, we can make a judgment that 151.101.194.1.241 is configured as the default gateway. To check if this is as it should be, we can look at our IP settings via the netshell. To launch netshell, enter the following command:
C:UsersMe>netsh
-
With netshell open, enter this command:
netshell>interface ipv6
netshell interface ipv6>showconfig
-
The response will show our Local Area Connection details, with a reference line for the Default Gateway. In our example we see the following:
Default Gateway 151.101.194.1.241
This confirms that 151.101.194.1.241 is currently configured as the default gateway, but when we look at our actual device’s IP address, we see it’s slightly different: 151.101.194.1.244.
How to Add the Correct Gateway Address for a Destination Host
From the information gained above, we can see we need to add the correct gateway address via our Local Area Network (LAN) settings. To do this, follow these steps.
-
Select Settings > Network and Internet > Network Connections.
-
Right-click the relevant Local Area Network. Then, select Properties.
-
From the list, select Internet Protocol Version 6 (TCP/IPv6). Next, select Properties.
-
In the Properties tab, change the Default Gateway to the correct address. So, in this example, we change «151.101.194.1.241» to «151.101.194.1.244.»
-
Press OK to save the changes.
Extra: How to Check if Destination Host Unreachable Error Is Resolved
-
To check if the issue is resolved, go back to the Command Prompt and exit the netshell using the following command:
netsh interface ipv6>exit
-
Now, we’re ready to try our ping test once more, using this command:
C:UsersMe>ping -6 151.101.194.114
-
Just as before, the ping should come back with a reply showing the new Default Gateway.
Pinging 151.101.194.114 with 64 bytes of data:
64 bytes from 151.101.194.114: icmp_seq=0 ttl=57 time=27.205 ms
64 bytes from 151.101.194.114: icmp_seq=1 ttl=57 time=14.109 ms
64 bytes from 151.101.194.114: icmp_seq=2 ttl=57 time=13.887 ms
64 bytes from 151.101.194.114: icmp_seq=3 ttl=57 time=13.954 ms
64 bytes from 151.101.194.114: icmp_seq=4 ttl=57 time=18.269 ms
-
As we can see, our ping test is now working and our connection is running as expected.
FAQ
-
What is the difference between “request time out” and “destination host unreachable?”
A request timeout error means that your request was received, but the host took too long to respond. A destination host unreachable error, on the other hand, means that your request couldn’t reach the host.
-
How does the ping command work?
The ping command is used to test the ability of the source computer to reach a specified destination computer. It sends Internet Control Message Protocol (ICMP) Echo request messages to the destination computer and waits for a response.
-
How do I ping a website?
To ping a website, open the command prompt and enter ping followed by the URL (i.e. ping lifewire.com). Alternatively, use a computer name or an IP address with the ping command.
Thanks for letting us know!
Get the Latest Tech News Delivered Every Day
Subscribe
This can be caused by bad internet and/or cable connections or even overly aggressive firewalls
Updated on December 1, 2022
Shortcut Options
- Test the IPv6 connection to determine the default gateway IP, then compare it to the device’s configured gateway via netshell IP settings.
- Add a gateway: LAN settings > Internet Protocol Version 6 (TCP/IPv6) > Properties. Change Default Gateway to the correct address.
- To check if the error is resolved, enter a ping test in Command Prompt: C:UsersMe>ping -6 151.101.194.114.
This article explains how to fix a destination host unreachable error on Windows devices, as well as how to add the correct gateway address for a destination host, and how to confirm the error is resolved.
What Causes a Destination Host Unreachable Error?
There are many possible reasons for getting a “destination host unreachable” error, including things as simple as erroneously connected cables or an overly aggressive firewall.
As you can see from the details below, we’re trying to ping a specific network device IP address, but the response we’re getting doesn’t provide much detail beyond the error itself:
C:UsersMe>ping 151.101.194.114
Pinging 151.101.194.114 with 64 bytes of data:
Reply from 151.101.194.114: Destination host unreachable
So, what’s going on here? In simple terms, we’re trying to communicate with a device at the specified IP address, but the remote gateway is unable to direct our ping request to the host itself, and so it sends an echo message back to say that it can’t be found.
How to Fix a Destination Host Unreachable Error
In diagnosing the error, it’s useful to follow the steps to fix an IPv6 error first to see if they resolve your networking issues. If the problem persists, you need to look at your network infrastructure to establish where the issue is.
For this example, we’re going to check our Default Gateway settings, then follow the steps to fix them.
-
To start, we need to check our internet connection via a browser. For this example, we’ll check google.com to see if it loads on our device. If it does, we know there’s a problem on our local network, rather than a broader connection issue.
-
Next, we’re going to test our IPv6 connection to see if that’s where the issue lies. To do this, open the Command Prompt and use the following command to ping your original IP address, but type «ping -6» to isolate the IPv6 line.
C:UsersMe>ping -6 151.101.194.114
-
You should get a reply in the Command Prompt, which looks like this:
Pinging 151.101.194.114 with 64 bytes of data:
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
Reply from 151.101.194.1.241: Destination host unreachable.
-
The above reply comes from IP address 151.101.194.1.241, which seems to relate to the remote gateway handling our request. To check this, run a traceroute using the following command:
C:UsersMe>tracert -6 -d 151.101.194.114
-
You should get a response, and it should resemble the following:
Tracing route 151.101.194.114 over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 151.101.194.1.241
2 151.101.194.1.241 reports: Destination host unreachable.
Trace complete.
-
From this, we can make a judgment that 151.101.194.1.241 is configured as the default gateway. To check if this is as it should be, we can look at our IP settings via the netshell. To launch netshell, enter the following command:
C:UsersMe>netsh
-
With netshell open, enter this command:
netshell>interface ipv6
netshell interface ipv6>showconfig
-
The response will show our Local Area Connection details, with a reference line for the Default Gateway. In our example we see the following:
Default Gateway 151.101.194.1.241
This confirms that 151.101.194.1.241 is currently configured as the default gateway, but when we look at our actual device’s IP address, we see it’s slightly different: 151.101.194.1.244.
How to Add the Correct Gateway Address for a Destination Host
From the information gained above, we can see we need to add the correct gateway address via our Local Area Network (LAN) settings. To do this, follow these steps.
-
Select Settings > Network and Internet > Network Connections.
-
Right-click the relevant Local Area Network. Then, select Properties.
-
From the list, select Internet Protocol Version 6 (TCP/IPv6). Next, select Properties.
-
In the Properties tab, change the Default Gateway to the correct address. So, in this example, we change «151.101.194.1.241» to «151.101.194.1.244.»
-
Press OK to save the changes.
Extra: How to Check if Destination Host Unreachable Error Is Resolved
-
To check if the issue is resolved, go back to the Command Prompt and exit the netshell using the following command:
netsh interface ipv6>exit
-
Now, we’re ready to try our ping test once more, using this command:
C:UsersMe>ping -6 151.101.194.114
-
Just as before, the ping should come back with a reply showing the new Default Gateway.
Pinging 151.101.194.114 with 64 bytes of data:
64 bytes from 151.101.194.114: icmp_seq=0 ttl=57 time=27.205 ms
64 bytes from 151.101.194.114: icmp_seq=1 ttl=57 time=14.109 ms
64 bytes from 151.101.194.114: icmp_seq=2 ttl=57 time=13.887 ms
64 bytes from 151.101.194.114: icmp_seq=3 ttl=57 time=13.954 ms
64 bytes from 151.101.194.114: icmp_seq=4 ttl=57 time=18.269 ms
-
As we can see, our ping test is now working and our connection is running as expected.
FAQ
-
What is the difference between “request time out” and “destination host unreachable?”
A request timeout error means that your request was received, but the host took too long to respond. A destination host unreachable error, on the other hand, means that your request couldn’t reach the host.
-
How does the ping command work?
The ping command is used to test the ability of the source computer to reach a specified destination computer. It sends Internet Control Message Protocol (ICMP) Echo request messages to the destination computer and waits for a response.
-
How do I ping a website?
To ping a website, open the command prompt and enter ping followed by the URL (i.e. ping lifewire.com). Alternatively, use a computer name or an IP address with the ping command.
Thanks for letting us know!
Get the Latest Tech News Delivered Every Day
Subscribe
I am using Linux oess (CentOS). I am working on a VM:
In the terminal, I’m trying to:
ping 8.8.8.8
to see my connectivity. It says:
Network is unreachable
Then I typed:
ifconfig:
inet addr: 192.168.56.101
Then:
sudo /sbin/route add -net 0.0.0.0 gw 192.168.56.101 eth0
Now I’m doing the same ping and it says:
Destination host is unreachable
for all the sequences.
What is the source of the problem?
route output:
Jeff Schaller♦
65.2k34 gold badges106 silver badges241 bronze badges
asked Sep 4, 2015 at 19:22
1
try DHCP for the network interface
sudo /etc/init.d/networking restart && sudo dhclient
Anthon
77k42 gold badges159 silver badges217 bronze badges
answered Sep 4, 2015 at 20:51
1
first things first.
can you ping 192.168.56.1 ? if so then you have an IP connection to the router, set this as your default route. otherwise try pinging 192.168.56.255 (broadcast) to see on what address you might get
replies. see arp -a to check what addresses you can find.
can you ping 8.8.4.4 (google) after changing the default route? if so you have internet access. if not check the router.
can you ping www.google.com? if not you might have a dns problem
do you get results from nslookup www.google.com ?
answered Sep 4, 2015 at 20:42
7
check the network card of the VM in the virtualization software. is it in «bridged» mode? or in a «NAT» or «host-only» mode?
in the last case change it to bridged and try $sudo dhclient
in the first case, see if the hypervisor itself can ping to its default gw and 8.8.4.4
answered Sep 4, 2015 at 21:41
1
There are two cases what a computer can do, when it has to forward an IP package:
-
First case: Say the destination IP of the incoming package is
10.20.30.40and the interface on which the package arrives is configured to be10.20.30.1 netmask 255.255.255.0. This is, the
packages destination subnet and the interfaces subnet are the same.
Then your OS will forward the package to the broadcast10.20.30.255
(it says «Here is a package that is addressed for someone in my own
hood, so please take it!»). -
Second case: Say the destination IP of the incoming package is
10.20.40.40and the interface on which the package arrives is configured to be10.20.30.1 netmask 255.255.255.0. Then the
destination address lies outside of the interfaces subnet. So it does
not know where to send it. So it forwards it to the default gateway
which in turn tries to find the destination.
In your case the default gateway is exactly the same as your interface IP. That means: When your computer does not know where to send a package it sends it to itself respectively to one of its own interfaces. That sounds strange — and it is. An interface gateway should be in the same subnet as the interface itself, but it should never BE itself. You need another default gateway in the same subnet to be happy.
If you don’t know your default gateway for this interface, so try to get a valid default gateway for this interface via DHCP configuration (configure this interface to be a DHCP client).
UPDATE:
In the case you are working in a VM (I see it is Virtual Box) try to find out the IP address of the «Virtual Box Host Only Adapter» on your host machine (command: ifconfig or ipconfig). Then configure the IP address of the VM host only adapter to be the default gateway of your VM guest.
UPDATE2:
On your host machine your should activate ipv4-forwarding and NAT to get internet access:
echo 1 > /proc/sys/net/ipv4/conf/all/forwarding
iptables -t nat -A POSTROUTING -o <interface on which you have the i-net access> -j MASQUERADE
UPDATE3:
If your want to use the «Host Only Adapter» then it may be possible, that you first have to create an «Host Only Network» under File->Preferences choosing the tab «Host Only Networks»…
answered Sep 4, 2015 at 20:54
fragwürdigfragwürdig
5223 silver badges6 bronze badges
5
(I cannot comment yet, hence a reply)
A router is a box that is separate from your computer. Where does the network cable from your computer go to? That might be your router. Can you post the name and identification numbers of that box? It might help us in assisting you.
My guess is that your router has the address 192.168.56.1 (if not, try 192.168.56.255) but that need not be true. See if you can ping it, and if you can open your router’s configuration page if you go to that IP address in a web browser.
If so, set that IP address as your gateway. The command you posted seems correct.
answered Sep 4, 2015 at 20:53
ejjlejjl
1896 bronze badges
2
Your Virtual Box network adapter is set to «Host-only».
Host-only networking allows your guest to access your host and your guest to access other guests. However, it does not allow network traffic to pass between the guest to the real physical network beyond the host, including the internet.
You are unable to ping 8.8.8.8 because that machine is neither your host nor one of your virtual machines. Change your Virtual Box network type to «NAT» or «Bridged» if you require access to the outside world.
answered Oct 7, 2017 at 17:53
Check your hw_address and add it to your DNS IP address:
$ arp -n
$ arp -s <ip_address> <hw_address>
NOTE: hw_address is your MAC address
slm♦
356k112 gold badges753 silver badges860 bronze badges
answered Jan 12, 2021 at 3:40
I see you receive the Destination Host Unreachable message when you ping 8.8.8.8 from your machine. It tells that the ping packets from your computer failed to find a route to the destination host.
Reasons to getting Destination Host Unreachable Error
There are a number of reasons to get this message on your machine. They are:
-
Wrong default gateway configuration
-
High intense firewall settings on your machine or at the remote host
-
Loose connection
Now let us check how to fix it.
The Solution
- Disable the Firewall
Disable the firewall and ping 8.8.8.8 from your machine. If you receive successful ICMP replies, you need to check the firewall settings.
- Power Cycle
Disconnect the power cables and Ethernet cables from the modem, router, and PC. Clean the cables, and reconnect them.
Power on the devices after two minutes.
Now ping 8.8.8.8 again and check for the issue. Reference: https://www.corenetworkz.com/2009/05/destination-host-unreachable-reason-and.html
answered Jul 13, 2021 at 11:21
2
I have two ubuntu computers on a local network and neither one of them can ping each other. Every time I try I get the «destination host unreachable» error message. Both computers are able to access the internet with any problems.
I have a ActionTech v1000h router from Telus. I’ve been in touch with one of their customer representatives and they said that there should’t be any reason why two devices cannot ping each other on the network.
I’m totally at a loss, do any of you guys have any ideas?
Computer 1:
ifconfig -a
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:10084 errors:0 dropped:0 overruns:0 frame:0
TX packets:10084 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:797420 (797.4 KB) TX bytes:797420 (797.4 KB)
wlan0 Link encap:Ethernet HWaddr c4:85:08:77:d3:f5
inet addr:192.168.1.77 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::c685:8ff:fe77:d3f5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:373068 errors:0 dropped:0 overruns:0 frame:0
TX packets:380158 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:103445020 (103.4 MB) TX bytes:112630337 (112.6 MB)
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 9 0 0 wlan0
sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Computer 2:
ifconfig -a
etho0 Link encap:Ethernet HWaddr 00:24:8c:ae:f6:91
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
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:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8414 (8.4 KB) TX bytes:8414 (8.4 KB)
wlan0 Link encap:Ethernet HWaddr 00:22:43:9b:7b:64
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::222:43ff:fe9b:7b64/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:252 errors:0 dropped:0 overruns:0 frame:0
TX packets:435 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:123143 (123.1 KB) TX bytes:65828 (65.8 KB)
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 9 0 0 wlan0
sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Edit: Example of the error when computer 1 tries to ping computer 2:
ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
From 192.168.1.77 icmp_seq=1 Destination Host Unreachable
From 192.168.1.77 icmp_seq=2 Destination Host Unreachable
From 192.168.1.77 icmp_seq=3 Destination Host Unreachable
From 192.168.1.77 icmp_seq=4 Destination Host Unreachable
From 192.168.1.77 icmp_seq=5 Destination Host Unreachable
From 192.168.1.77 icmp_seq=6 Destination Host Unreachable
^C
--- 192.168.1.2 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6031ms
pipe 3
Edit 2: arp -a of both computers
Computer 1:
? (192.168.1.254) at 20:76:00:f5:3b:70 [ether] on wlan0
Computer 2:
? (192.168.1.254) at 20:76:00:f5:3b:70 [ether] on wlan0
? (192.168.1.77) at <incomplete> on wlan0
Edit 3: nmap -sn 192.168.1.0/24 on computer 2
Starting Nmap 6.40 ( http://nmap.org ) at 2014-05-07 21:14 PDT
Nmap scan report for 192.168.1.2
Host is up (0.00024s latency).
Nmap done: 256 IP addresses (1 host up) scanned in 3.30 seconds
Edit 4: The tcpdump logs of both computers while the first ping 192.168.1.254 and then each other:
Computer 1:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes
22:45:01.661300 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:02.659393 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:03.659394 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:04.676872 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:05.675391 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:06.675396 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:07.692825 ARP, Request who-has 192.168.1.2 tell 192.168.1.77, length 28
22:45:48.379058 ARP, Request who-has 192.168.1.77 tell 192.168.1.254, length 28
22:45:48.379108 ARP, Reply 192.168.1.77 is-at c4:85:08:77:d3:f5, length 28
22:45:54.419388 ARP, Request who-has 192.168.1.254 tell 192.168.1.77, length 28
22:45:54.420875 ARP, Reply 192.168.1.254 is-at 20:76:00:f5:3b:70, length 28
Computer 2:
reading from file pc2.pcap, link-type EN10MB (Ethernet)
22:44:43.538367 ARP, Request who-has 192.168.1.254 tell 192.168.1.2, length 28
22:44:43.676705 ARP, Reply 192.168.1.254 is-at 20:76:00:f5:3b:70 (oui Unknown), length 28
22:45:02.107935 ARP, Request who-has 192.168.1.254 tell 192.168.1.2, length 28
22:45:02.107951 ARP, Reply 192.168.1.254 is-at 20:76:00:f5:3b:70 (oui Unknown), length 28
22:45:06.780619 ARP, Request who-has 192.168.1.77 tell 192.168.1.2, length 28
22:45:07.778419 ARP, Request who-has 192.168.1.77 tell 192.168.1.2, length 28
22:45:08.778419 ARP, Request who-has 192.168.1.77 tell 192.168.1.2, length 28
22:45:09.796214 ARP, Request who-has 192.168.1.77 tell 192.168.1.2, length 28
Edit 5: Setup static ips for both computers etho0 and connected them with an internet cable. Both computers can definitely ping each other through the ethernet cable! ifconfig -a eth0 results:
Computer 1:
eth0 Link encap:Ethernet HWaddr 68:68:68:00:62:a4
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::6a68:68ff:fe00:62a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4060 (4.0 KB) TX bytes:7629 (7.6 KB)
Computer 2:
eth0 Link encap:Ethernet HWaddr 00:24:8c:ae:f6:91
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::224:8cff:feae:f691/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:250 errors:0 dropped:0 overruns:0 frame:0
TX packets:130 errors:0 dropped:0 overruns:0 carrier:3
collisions:0 txqueuelen:1000
RX bytes:26501 (26.5 KB) TX bytes:20897 (20.8 KB)