Configuration Help. Ping says Destination unreachable.

[Guus Sliepen]

On Sat, Jun 07, 2003 at 12:58:43PM -0500, Shashank Khanvilkar wrote:

> However i have some configuration problem now. Here is the backgroud:
[...]
> [shashank at mia mia]# cat hosts/zidler 
> Address = 131.193.50.184
> #cipher = blowfish
> #Compression = 9
> #Digest = sha1
> #IndirectData = no
> Subnet = 192.168.2.0/24
> -----BEGIN RSA PUBLIC KEY-----
> MIGJAoGBAMIJu3jEzpzBwRSkcDTTKPvsYv1BfpSzEX7jy5eRB50riRO7cOeDG2BU
> zh0y8l5tSJ6IEgg7SAQdl3FeIUOUQQGP4evaIMcMsoYkoqO4Sw2vMFWizoNb0dCQ
> nDiOh7cW2Xw8cBwbo/cdn1jGROK10UsWHkRyAGqEo8ReMqWw9mTDAgMA//8=
> -----END RSA PUBLIC KEY-----

In this configuration file, you say that zidler can be reached at
131.193.50.184, and that on the VPN it has the subnet 192.168.2.0/24.
However:

> [shashank at mia mia]# ping 192.168.254.201
> PING 192.168.254.201 (192.168.254.201) 56(84) bytes of data.
> >From 192.168.254.201 icmp_seq=2 Dest Unreachable, Bad Code: 6

The ping command is a bit stupid here, code 6 is not bad at all, it
means that the subnet you sent the ping packet to is unknown. This is
correct, because you sent the packet to 192.168.254.201, which is not in
192.168.2.0/24.

Make sure the Subnets you specify in the host configuration file match
the actual subnets you use on the VPN. You either want to specify:

Subnet = 192.168.254.201/32

Or maybe your subnet was correct, but you configured the network
interface wrong in tinc-up, and what you want is:

ifconfig $INTERFACE 192.168.2.1 netmask 255.255.255.0

And consequently ping 192.168.2.1 instead of 192.168.254.201.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20030607/d2a4452b/attachment.pgp