All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help!! Cisco --> Linux   Tunneling via NOS Encapsulation
Date: Tue, 08 Jan 2002 19:01:49 +0000	[thread overview]
Message-ID: <marc-lartc-101051659831183@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101051384924316@msgid-missing>

On Tue, 8 Jan 2002, Juda Barnes wrote:

[snip]
> My problem is that my ISP use a   Cisco implemented IP over IP encapsulation called NOS (KA9Q/NOS Compatiable) , also named protocol 94
> 
> i have made some debugs and with the tunnel i have set up below  my computer (192.168.1.2) able to ping to the Cisco Machine
> But when the cisco send reply , my   machine send to the router     protocol unreachable
> 
> that means my linux box dont recognize the NOS protocol   , i have pass allmost the whole linux how to documents

I've searched the net for a little while and to me it seems like NOS is
a normal ipip tunnel but using ipprotocol 94 instead of 4

from linux/include/linux/in.h:

  IPPROTO_IPIP = 4,             /* IPIP tunnels (older KA9Q tunnels use 94) */

and IPPROTO_IPIP is used in ipip.c which is the IP-in-IP driver in linux.

So you machine sends out tunnelpackets it sends them out with ip protocol
4 which the cisco seem to accept but the cisco sends packets back to you
with ip protocol 94. I assume they have a generic ipip driver in Cisco's
IOS that listens for both ip protocol 4 and 94 and uses one of those
protocols depending on the configuration.

So if you change the value of IPPROTO_IPIP to 94 and recompile your kernel
it should work. But after this small change your machine won't be able to
set up tunnels to other Linux's which use protocol 4... but maybe you can
live with that. It's of course possible to fix it so that linux can use
both but that needs some hacking, something you can start looking at if
you're interested in kernelhacking.

Hope this helps.

/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2002-01-08 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 18:16 [LARTC] Help!! Cisco --> Linux Tunneling via NOS Encapsulation Juda Barnes
2002-01-08 19:01 ` Martin Josefsson [this message]
2002-01-09 10:34 ` [LARTC] Help!! Cisco --> Linux Tunneling via NOS Encapsula Jerome Petazzoni
2002-01-12 23:10 ` Juda Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-101051659831183@msgid-missing \
    --to=gandalf@wlug.westbo.se \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.