Ich hab schon WAN und nicht WLAN gemeint, darum versteh ichs auch nicht x)
Also hier die Ausgaben:
sudo dhclient -4 -v -d eth0
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:16:e6:8d:b5:8b
Sending on LPF/eth0/00:16:e6:8d:b5:8b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x7dd98762)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x7dd98762)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0x7dd98762)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0x7dd98762)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0x7dd98762)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x7dd98762)
route -n
Kernel 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
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:e6:8d:b5:8b
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::216:e6ff:fe8d:b58b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7159 errors:0 dropped:216 overruns:0 frame:73
TX packets:1849 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1046533 (1.0 MB) TX bytes:322096 (322.0 KB)
Interrupt:16
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:7163 errors:0 dropped:0 overruns:0 frame:0
TX packets:7163 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:499916 (499.9 KB) TX bytes:499916 (499.9 KB)
host heise.de 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
heise.de has address 193.99.144.80
heise.de has IPv6 address 2a02:2e0:3fe:1001:302::
heise.de mail is handled by 10 relay.heise.de.
ping -c 2 -W 2 193.99.144.80 –> Interessant, dass ich beim einen versuch nur 50% packett loss hatte?
PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
--- 193.99.144.80 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
andy@ubuSrv01:~$ ping -c 2 -W 2 193.99.144.80
PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
--- 193.99.144.80 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms
andy@ubuSrv01:~$ ping -c 2 -W 2 193.99.144.80
PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
64 bytes from 193.99.144.80: icmp_seq=1 ttl=243 time=25.2 ms
--- 193.99.144.80 ping statistics ---
2 packets transmitted, 1 received, 50% packet loss, time 1001ms
rtt min/avg/max/mdev = 25.297/25.297/25.297/0.000 ms
andy@ubuSrv01:~$ ping -c 2 -W 2 193.99.144.80
PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
--- 193.99.144.80 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms
Grüsse