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)
I am trying to set up a static IP address for my Debian virtual machines. In my /etc/networking/interfaces file I added:
iface ens33 inet static
address 192.168.75.XXX
gateway 192.168.0.1
netmask 255.255.255.0
In the /etc/resolv.conf file I have added nameserver 8.8.8.8. I believe my issue is that unless I have the NetworkManager service enabled nothing shows up when I run route or ip route show. I tried adding a route to the routing table by running the following command: ip route add 192.168.75.0/24 via 192.168.75.XXX (my static ip) dev ens33. This populates the routing table and the table now looks like:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.75.0 0.0.0.0 255.255.255.0 U 0 0 0 ens33
When I run ping I still get the same error: “Destination Host Unreachable”. How can I fix this?
Spiff
100k17 gold badges173 silver badges226 bronze badges
asked Feb 15, 2021 at 21:25
4
In /etc/networking/interfaces, in each section, you set a netmask that defines the subnet your machine belongs to. Here: 255.255.255.0 means /24. IOW, the adresses on your subnet go from 192.168.75.1 to 192.168.75.254.
The gateway line specifies the address of the router that must be used to reach a machine that is outside that subnet. Obviously, the router must be a machine that is on the same subnet, i.e. that has an IP address between 192.168.75.1 to 192.168.75.254.
You have specified gateway 192.168.0.1. That means that the router is outside the subnet. That’s why you cannot ping any machine outside your sub-network 192.168.75.0/24 (“Destination Host Unreachable”).
You are using VMs. Your router is probably the IP address of your host. It depends on the configuration of your VM.
One last thing:
ip route add 192.168.75.0/24 via 192.168.75.XXX (my static ip) dev ens33
is wrong. If you want to declare a router manually (as opposed to the interfaces file) then use this command:
ip route add default via 192.168.75.YYY (the IP of your router) dev ens33
(default means “any address that has no known route”)
answered Feb 15, 2021 at 23:49
Destination host unreachable is a common ICMP error message when the ping packets from your machine could not find the destination machine.
It looks like some settings on your machine are blocking the ping packets from discovering the route to the destination IP.
Well, I see you fixed the problem by changing the network type to bridge mode. So I think I better write a general answer since your issue is solved.
The common reason to get the ping reply Destination Host Unreachable is due to the overprotective settings on the firewall. Unless you are running a bridging firewall, a simple misconfiguration can block proper ping packet working.
You can verify it by disabling the firewall and ping the destination IP again.
The second common reason is a loose network connection. Referred from this source.
We can fix this, by disconnecting both power cables and Ethernet cables from the modem, router, and PC. Reconnect them again and power on the devices. It is called power cycling.
answered Jul 11, 2021 at 20:15
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.9k34 gold badges108 silver badges245 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
77.8k42 gold badges164 silver badges221 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
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♦
360k114 gold badges760 silver badges868 bronze badges
answered Jan 12, 2021 at 3:40
(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
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
0
1
При попытке пинга с Убунты локальной машины центос пишет
ping 192.168.8.1
PING 192.168.8.1 (192.168.8.1) 56(84) bytes of data.
From 192.168.8.101 icmp_seq=1 Destination Host Unreachable
From 192.168.8.101 icmp_seq=2 Destination Host Unreachable
[58]+ Остановлено ping 192.168.8.1
ping 192.168.100.166
PING 192.168.100.166 (192.168.100.166) 56(84) bytes of data.
From 192.168.8.101 icmp_seq=1 Destination Host Unreachable
From 192.168.8.101 icmp_seq=2 Destination Host Unreachable
При попытке подключиться по ssh
ssh: connect to host 192.168.8.1 port 22: No route to host
ssh: connect to host 192.168.100.166 port 22: No route to hostНа центосе стоит 2 сетевые карты с этими айпи. И нету подключения к интернету.
- Печать
Страницы: [1] 2 Все Вниз
Тема: destination host unreachable при настройке инета. (Прочитано 15463 раз)
0 Пользователей и 1 Гость просматривают эту тему.
SwimKa
Собственно говоря при пинге шлюза(домашний роутер) выдает destination host unreachable. Так же почему то не хочет получать по DHCP ип от роутера. В случае через xwindow прописываю следующее
ip: 192.168.0.99
mask 255.255.255.0
шлюз 192.168.0.1
В DNS свои днс от провайдера и которые на роутере забиты.
В случае консоли правлю файл
/etc/network/interfaces
так же делаю
route add default gw 192.168.0.1
echo “nameserver DNS” >> /etc/resolv.conf
ifconfig eth0 down
ifconfig eth0 up
В обоих случаях тоже самое. Может ли быть какая то проблема с сетевой картой? помимо этой машинке там ещё к роутеру две виндовые подключены, на них все нормально.
athost
Вывод команд
lspci -k | grep -iA2 ether
ifconfig -a
cat /etc/network/interfaces
SwimKa
1 Какой ключ указать для lspci , ключа k нету.
2.
iface lo inet loopback
iface eth0 inet static
address 192.168.0.99
netmask 255.255.255.0
gateway 192.168.0.1
auto eth0
3. ifconfig -a
eth0 Link encap: Ethernet HWaddr: 00:20:ed:68:f6:a0
inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNIG MULTICAST MTU:1500 Metric:1
RX packets:0 errors:2 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
то что дальше нужно?
athost
Какой ты хочешь dhcp с роутера, если выставляешь статику? В какой сети находится роутер?
Проше всего включить dhcp-сервер на роутере, а в /etc/network/interfaces прописать
iface eth0 inet dhcp
SwimKa
Какой ты хочешь dhcp с роутера, если выставляешь статику? В какой сети находится роутер?
Проше всего включить dhcp-сервер на роутере, а в /etc/network/interfaces прописать
iface eth0 inet dhcp
DHCP включен на роутере. Виндовые машины получают от него нормально. От роутера 169 ип получал комп, (сейчас включил вообще никакой ип не получает), потому решил прописать статику, сейчас стоит статика. Находится он в сети класса C , т.к. маска 255.255.255.0. В сетевой карте может быть проблема?
athost
С сетевой все нормально.
Какой адрес у роутера?
SwimKa
С сетевой все нормально.
Какой адрес у роутера?
Lan 192.168.0.1
WAN соответственно провайдерский.
athost
Еще раз проверим
uname -a
lspci -k
ifconfig -a
ping 192.168.0.1
и проверь физический линк от компа к роутеру.
SwimKa
Еще раз проверим
uname -a
lspci -k
ifconfig -a
ping 192.168.0.1
и проверь физический линк от компа к роутеру.
Линк я проверял первым делом. Даже во второй комп включал, все работает.
1. Linux sm 2.6.24-26-generic #1 SMP Tue Dec 1 18.37:31 UTC 2009 i686 GNU/Linux
2. Нет ключа к
3.
eth0 Link encap: Ethernet HWaddr: 00:20:ed:68:f6:a0
inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
4.Сейчас просто не пингуется, 100 % потерь.
Кабель обжат direct. На другие компы его кидал все работает со статикой и с dhcp .
athost
А какой дистр? Попробуй lspci -v
Пользователь решил продолжить мысль 14 Февраля 2010, 18:09:57:
Проблема очень похожа на железячную, попробуй с другим патч-кордом, дыркой на роутере и сетевой картой;)
« Последнее редактирование: 14 Февраля 2010, 20:10:42 от athost »
SwimKa
А какой дистр? Попробуй lspci -v
Пользователь решил продолжить мысль 14 Февраля 2010, 16:09:57:
Проблема очень похожа на железячную, попробуй с другим патч-кордом, дыркой на роутере и сетевой картой;)
Сейчас десктопный стоит. 8.04.4. Сделал -v
Для ethernet контроллера напишу
Flags: bus master, medium devsel, latency32. IRQ 16
что ещё оттуда нужно? Собственно с виндовых роутер пингуется, фаерволл на нем отключен.
« Последнее редактирование: 14 Февраля 2010, 20:27:51 от SwimKa »
athost
Из тебя все клещами надо тянуть?
lspci -v | grep -iA9 ether
Я хочу посмотреть название модуля ядра, мать твою 
Пользователь решил продолжить мысль 14 Февраля 2010, 18:31:56:
Еще хочу, только не помню, стоят ли они по дефолту
sudo ethtool eth0
« Последнее редактирование: 14 Февраля 2010, 20:32:50 от athost »
SwimKa
Из тебя все клещами надо тянуть?
lspci -v | grep -iA9 ether
Я хочу посмотреть название модуля ядра, мать твою
Пользователь решил продолжить мысль 14 Февраля 2010, 18:31:56:
Еще хочу, только не помню, стоят ли они по дефолту
sudo ethtool eth0
Subsystem: Intel Corp. EtherExpress PRO/100 VE
Flags: bus master, medium devsel, latency32. IRQ 16
Memory at e4000000 (32-bit, non-perfectchable) [siza=4K]
I/0 ports at c800 [size=64]
Capabilities: [dc] Power Managmetn vers. 2
athost
Subsystem: Intel Corp. EtherExpress PRO/100 VE
Flags: bus master, medium devsel, latency32. IRQ 16
Memory at e4000000 (32-bit, non-perfectchable) [siza=4K]
I/0 ports at c800 [size=64]
Capabilities: [dc] Power Managmetn vers. 2
Скажи честно, ты надо мной издеваешься? Дай полный вывод команды.
SwimKa
Subsystem: Intel Corp. EtherExpress PRO/100 VE
Flags: bus master, medium devsel, latency32. IRQ 16
Memory at e4000000 (32-bit, non-perfectchable) [siza=4K]
I/0 ports at c800 [size=64]
Capabilities: [dc] Power Managmetn vers. 2Скажи честно, ты надо мной издеваешься? Дай полный вывод команды.
;DНет, сорри. Строчку просто пропустил.
1:08.0 Ethernet Controller: Intel corp. 82891BA/BAM/CA/CAM Ethernet Controller (rev 03)
Subsystem: Intel Corp. EtherExpress PRO/100 VE
Flags: bus master, medium devsel, latency32. IRQ 16
Memory at e4000000 (32-bit, non-perfectchable) [siza=4K]
I/0 ports at c800 [size=64]
Capabilities: [dc] Power Managment vers. 2
Пользователь решил продолжить мысль 14 Февраля 2010, 20:51:04:
sudo ethtool eth0
Supp ports [TP MII]
Supp link modes : все, полу, полный дюплекс 10 и 100 мбит
Advertised auto-negotiation yes
speed: 100 mb/s
Duplex full
Port MII
PHYAD 1
Transceiver internal
auto-negotiation on
Supp wake-on g
wake on g
Link detected yes
« Последнее редактирование: 14 Февраля 2010, 20:51:04 от SwimKa »
- Печать
Страницы: [1] 2 Все Вверх
