Bom dia, desde já continuo agradecendo a ajuda
Na realidade esta máquina não é um servidor de de rede, é um desktop comum usando KUBUNTU 15.04(kde 5.2-plasma)
root@Info:/home/info# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:a1:b0:69:48:39
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:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth1 Link encap:Ethernet HWaddr 00:27:0e:00:d0:ad
inet addr:192.168.2.106 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::227:eff:fe00:d0ad/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28209 errors:0 dropped:430 overruns:0 frame:0
TX packets:2412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3296354 (3.2 MB) TX bytes:299232 (299.2 KB)
Interrupt:20 Memory:e3200000-e3220000
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:791 errors:0 dropped:0 overruns:0 frame:0
TX packets:791 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:87046 (87.0 KB) TX bytes:87046 (87.0 KB)
wlan0 Link encap:Ethernet HWaddr 00:21:91:7e:b9:e4
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:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root@Info:/home/info# 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 00:a1:b0:69:48:39 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:27:0e:00:d0:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.2.106/24 brd 192.168.2.255 scope global eth1
valid_lft forever preferred_lft forever
inet 10.0.1.106/21 brd 10.0.7.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::227:eff:fe00:d0ad/64 scope link
valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:21:91:7e:b9:e4 brd ff:ff:ff:ff:ff:ff
root@Info:/home/info# cat /etc/network/interfaces
# interfaces(5) file used by ifup( 8) and ifdown( 8)
auto lo
iface lo inet loopback
root@Info:/home/info# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.254 0.0.0.0 UG 100 0 0 eth1
10.0.0.0 0.0.0.0 255.255.248.0 U 100 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1
192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 eth1
root@Info:/home/info# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=false
root@Info:/home/info# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=false
root@Info:/home/info# cat /etc/NetworkManager/system-connections/static
[ethernet]
mac-address=00:27:0E:00:D0:AD
[connection]
id=static
uuid=f24e8c7b-bf83-4a86-b175-6f2d122c6aa4
type=ethernet
permissions=user:info:;
[ipv6]
method=auto
[ipv4]
method=manual
dns=192.168.2.254;
address1=192.168.2.106/24,192.168.2.254
address2=10.0.1.106/21
o que estou achando muito estranho é que usando debian 8.x KDE ou linux mint 17.2 KDE sempre usei desta mesma forma sempre editando as conexões usado o "Editor de Conexão", do próprio network-manager, e sempre fucinonou tranquilamente, não sei o que está acontecendo com o kubuntu, tem algum macete, que eu aida não consegui pegar
mais algumas informações
10.0.0.243 no mesmo switche que eu, 10.0.0.254 e 10.0.0.242 no mesmo rack ahá 2 switches de mim
arping -I eth1 -f 10.0.0.243
ARPING 10.0.0.243 from 192.168.2.106 eth1
Unicast reply from 10.0.0.243 [00:25:11:74:B0:B7] 0.828ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)
ping -c5 10.0.0.243
PING 10.0.0.243 (10.0.0.243) 56(84) bytes of data.
64 bytes from 10.0.0.243: icmp_seq=1 ttl=128 time=0.252 ms
64 bytes from 10.0.0.243: icmp_seq=2 ttl=128 time=0.230 ms
64 bytes from 10.0.0.243: icmp_seq=3 ttl=128 time=0.260 ms
64 bytes from 10.0.0.243: icmp_seq=4 ttl=128 time=0.258 ms
64 bytes from 10.0.0.243: icmp_seq=5 ttl=128 time=0.257 ms
--- 10.0.0.243 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.230/0.251/0.260/0.017 ms
traceroute -m10 10.0.0.243
traceroute to 10.0.0.243 (10.0.0.243), 10 hops max, 60 byte packets
1 10.0.0.243 (10.0.0.243) 0.265 ms * *
tracepath -m10 10.0.0.243
1?: [LOCALHOST] pmtu 1500
1: 10.0.0.243 0.635ms reached
1: 10.0.0.243 0.626ms reached
Resume: pmtu 1500 hops 1 back 1
==========================================================================
arping -I eth1 -f 10.0.0.254
ARPING 10.0.0.254 from 192.168.2.106 eth1
Unicast reply from 10.0.0.254 [D4:CA:6D:22:5D:54] 0.747ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)
ping -c5 10.0.0.254
PING 10.0.0.254 (10.0.0.254) 56(84) bytes of data.
--- 10.0.0.254 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4033ms
traceroute -m10 10.0.0.254
traceroute to 10.0.0.254 (10.0.0.254), 10 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
tracepath -m10 10.0.0.254
1?: [LOCALHOST] pmtu 1500
1: no reply
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
==========================================================================
arping -I eth1 -f 10.0.0.242
ARPING 10.0.0.242 from 192.168.2.106 eth1
Unicast reply from 10.0.0.242 [00:30:48:E4:38:D3] 0.797ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)
ping -c5 10.0.0.242
PING 10.0.0.242 (10.0.0.242) 56(84) bytes of data.
64 bytes from 10.0.0.242: icmp_seq=1 ttl=128 time=0.510 ms
64 bytes from 10.0.0.242: icmp_seq=2 ttl=128 time=0.255 ms
64 bytes from 10.0.0.242: icmp_seq=3 ttl=128 time=0.238 ms
64 bytes from 10.0.0.242: icmp_seq=4 ttl=128 time=0.260 ms
64 bytes from 10.0.0.242: icmp_seq=5 ttl=128 time=0.258 ms
--- 10.0.0.242 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.238/0.304/0.510/0.103 ms
traceroute -m10 10.0.0.242
traceroute to 10.0.0.242 (10.0.0.242), 10 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
tracepath -m10 10.0.0.242
1?: [LOCALHOST] pmtu 1500
1: no reply
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
==========================================================================
será que pode ter alguma coisa a ver com rotas que derrepente no kunbuntu 15.04 deva ser colocada manualmente e nos outros testados era automático?
se precisar de qualquer informação adicional, por favor basta pedir