Linux-Hams archive - May 1997: Re: Unreachable code Protocol ?

Re: Unreachable code Protocol ?


Tue, 6 May 1997 08:34:07 +1000 (EST)


dg1ees typed:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
>
> Hello there,
G'day!

> i've got the folling problem.....
> Kernel 2.0.29 + modules-12
> module-utils-2.1.22b
> tnos-2.21
> tnc2/g3ruh:9k6 at /dev/ttyS0
> dg1ees: 44.130.18.12 AND
> dg1ees-svr:192.18.12.[1-254]
> Tnos/Linux connected via ptypf/ttypf
>
> IF i attach the tnc with tnos and Linux has got the 192# - i can acces the
> radio from tnos and linux.
>
> IF Linux kissattaches /dev/ttyS0 and Tnos hast got the 192# - than:
>
> Port c: AX25: DB0QS-9->DG1EES-1 <UI> pid=IP
> IP: len 64 44.130.18.100->44.130.18.12 ihl 20 ttl 16 prot IP
> IP: len 44 44.130.18.100->192.18.12.1 ihl 20 ttl 16 prot TCP
> TCP: ftp->nterm Seq xf94f9790 Ack x6d2b7001 ACK SYN Wnd 2048 Data 4
> 0000 ..._
See the second line in this packet? DB0QS-9 is IP tunnelling (putting IP
into an IP packet).

> Port c: AX25: DG1EES-1->DB0QS-9 <UI> pid=IP
> IP: len 112 44.130.18.12->44.130.18.100 ihl 20 ttl 64 tos 192 prot ICMP
> ICMP: type Unreachable code Protocol
> Returned IP: len 64 44.130.18.100->44.130.18.12 ihl 20 ttl 16 prot IP
> IP: len 44 44.130.18.100->192.18.12.1 ihl 20 ttl 16 prot TCP
> TCP: ftp->nterm Seq xf94f9790 Ack x6d2b7001 ACK SYN Wnd 2048 Data 24
> 0000 ..._....................
Then your system is saying IP over IP (protocol ID 4/94) what are you going
on about, I don't know anything about this.

> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
It's not a routing problem, it is a protocol problem. Either you have to
tell DB0QS-9 to route 192.18.12.1 directly or you have to masquerade
192.18.12.1 when it comes out the radio port or change the 192 number to a
44 number or you have to run some IP tunneling code.

> What does Protocol unreachable mean ? And what can i do to control the tnc
> with kernel-ax25 and tnos runs via pseudolink with 192# ?
pseudolink? You mean you've made this 192 number up? Then you should be
using 192.168 something. But we have lots of 44 numbers, why not make
everything a 44 number?

- Craig

-- 
  // /\   |  | |  Craig Small VK2XLZ     @home: terhi.victor@logonet.com
 ||==||===|==|=|  [44.136.13.17]         @play: ukw@fw21above.mobilkom.at
  \\ \/   |  | |  finger vfo@spencer-air.com for PGP key!