- Posts: 4
- Thank you received: 0
Destination Net Unreachable
18 years 2 months ago #16829
by whale
Destination Net Unreachable was created by whale
Hi
i have small lan network with 2 computers: one with inernet and lan
and second only lan. when i ping the lan card i get
icmp_seq=4 Destination Net Unreachable
i read this article
www.firewall.cx/icmp-dest-unreachable.php
this is exact situation mentionend there but how to solve this problem
thanx
i have small lan network with 2 computers: one with inernet and lan
and second only lan. when i ping the lan card i get
icmp_seq=4 Destination Net Unreachable
i read this article
www.firewall.cx/icmp-dest-unreachable.php
this is exact situation mentionend there but how to solve this problem
thanx
18 years 2 months ago #16832
by Arani
Picking pebbles on the shore of the networking ocean
you have cracked half the case already by reading the material, the point of interest here is the code 4 which relates to "Fragmentation needed or DF Set".
here DF stands for Don't Fragment, which is an essentially a 3 bit section in the entire IP packet structure. the first bit is not used as it is reserved. the second bit is used to specify if the packet can be fragmented or not and is called the DF bit. setting the value for this bit to 0 would mean YES you can fragment it. setting the value to 1 would mean, no you cannot fragment this packet. the third bit is related to the second bit. this bit stands for More Fragments. if the second bit is set to 0, which means you can fragment this packet, then the first packet of the entire big packet will have a value 1. coupled with the DF value as 0 this means that this particular IP packet can be fragmented, and you are expecting more fragment packets from the original big packet. the last packet of the entire original packet will have the last bit set to 0. this coupled with DF set to 0 means, either this is a fragmentable packet and this particular packet is the only packet of that fragment, or this is a fragmentable packet, and this is the last fragment of the big packet.
by design, ICMP packets have the DF value set to 1. this means that ICMP packets cannot be fragmented. this is because ICMP is a network management protocol, hence fragmentation could compromise packet content in various ways.
now by the looks of it, it seems your ICMP packets are going through a channel which cannot take the full size of the ICMP packets, but cannot even fragment the incoming IP packet containing the ICMP segment, simply because the DF field in the IP packet is set to 1. hence no ping packet i.e ICMP packets can get through that 'bottleneck'.
ways to solve the problem, first step:
find the bottleneck
a more detailed network structure could help us diagnose where it is, so if possible post a simple picture of your lan structure.
here DF stands for Don't Fragment, which is an essentially a 3 bit section in the entire IP packet structure. the first bit is not used as it is reserved. the second bit is used to specify if the packet can be fragmented or not and is called the DF bit. setting the value for this bit to 0 would mean YES you can fragment it. setting the value to 1 would mean, no you cannot fragment this packet. the third bit is related to the second bit. this bit stands for More Fragments. if the second bit is set to 0, which means you can fragment this packet, then the first packet of the entire big packet will have a value 1. coupled with the DF value as 0 this means that this particular IP packet can be fragmented, and you are expecting more fragment packets from the original big packet. the last packet of the entire original packet will have the last bit set to 0. this coupled with DF set to 0 means, either this is a fragmentable packet and this particular packet is the only packet of that fragment, or this is a fragmentable packet, and this is the last fragment of the big packet.
by design, ICMP packets have the DF value set to 1. this means that ICMP packets cannot be fragmented. this is because ICMP is a network management protocol, hence fragmentation could compromise packet content in various ways.
now by the looks of it, it seems your ICMP packets are going through a channel which cannot take the full size of the ICMP packets, but cannot even fragment the incoming IP packet containing the ICMP segment, simply because the DF field in the IP packet is set to 1. hence no ping packet i.e ICMP packets can get through that 'bottleneck'.
ways to solve the problem, first step:
find the bottleneck
a more detailed network structure could help us diagnose where it is, so if possible post a simple picture of your lan structure.
Picking pebbles on the shore of the networking ocean
18 years 2 months ago #16834
by whale
Replied by whale on topic Re: Destination Net Unreachable
this is my networking interfaces:
computer1:
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.8.87
netmask 255.255.255.0
network 192.168.8.0
broadcast 192.168.8.255
gateway 192.168.8.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 212.160.102.2 194.204.159.1
auto eth1
iface eth1 inet static
address 10.0.0.1
netmask 255.255.255.0
network 10.0.0.0/24
Computer2
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.0.0.2
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255
gateway 10.0.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 212.160.102.2 194.204.159.1
computer1:
when i ping 192.168.8.87 i get:
64 bytes from 192.168.8.87: icmp_seq=1 ttl=64 time=0.104 ms
but
when i ping 10.0.0.1 od 10.0.0.2 i get
From 192.168.8.1 icmp_seq=1 Destination Net Unreachable
computer2:
when i ping 192.168.8.87 i get:
64 bytes from 192.168.8.87: icmp_seq=1 ttl=64 time=0.11 ms
but
when i ping 10.0.0.1 od 10.0.0.2 i get
From 192.168.8.1 icmp_seq=1 Destination Net Unreachable
Idon't know where to look for solution. please help me
computer1:
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.8.87
netmask 255.255.255.0
network 192.168.8.0
broadcast 192.168.8.255
gateway 192.168.8.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 212.160.102.2 194.204.159.1
auto eth1
iface eth1 inet static
address 10.0.0.1
netmask 255.255.255.0
network 10.0.0.0/24
Computer2
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.0.0.2
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255
gateway 10.0.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 212.160.102.2 194.204.159.1
computer1:
when i ping 192.168.8.87 i get:
64 bytes from 192.168.8.87: icmp_seq=1 ttl=64 time=0.104 ms
but
when i ping 10.0.0.1 od 10.0.0.2 i get
From 192.168.8.1 icmp_seq=1 Destination Net Unreachable
computer2:
when i ping 192.168.8.87 i get:
64 bytes from 192.168.8.87: icmp_seq=1 ttl=64 time=0.11 ms
but
when i ping 10.0.0.1 od 10.0.0.2 i get
From 192.168.8.1 icmp_seq=1 Destination Net Unreachable
Idon't know where to look for solution. please help me
18 years 2 months ago #16850
by nske
Are you sure the eth1 interface is up and configured as you mentioned? Could you post the output of "ifconfig" and "route -n"
Replied by nske on topic Re: Destination Net Unreachable
Since 10.0.0.1 is attached to a local interface, the computer shouldnt go through a gateway to reach it!when i ping 10.0.0.1 or 10.0.0.2 i get
From 192.168.8.1 icmp_seq=1 Destination Net Unreachable
Are you sure the eth1 interface is up and configured as you mentioned? Could you post the output of "ifconfig" and "route -n"
18 years 2 months ago #16864
by whale
Replied by whale on topic Re: Destination Net Unreachable
i've solved problem eth0 on second computer was incorrectly set. I've typed 10.0.0.2 but in fact was 10.10.10.2. i mistype here. thanx for help
Time to create page: 0.127 seconds