From: "Juda Barnes" <juda@pent900.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: [Masq] Tunnelling Via Linux
Date: Wed, 21 Nov 2001 11:55:04 +0000 [thread overview]
Message-ID: <marc-lartc-100634366615516@msgid-missing> (raw)
----- Original Message -----
From: "David Ranch" <dranch@trinnet.net>
To: "Juda Barnes" <juda@pent900.com>; <masq@indyramp.com>
Sent: Wednesday, November 21, 2001 5:39 AM
Subject: Re: [Masq] Tunnelling Via Linux
> >Well my ISP using That kind of Tunnel (See below)
> >
> >It is called 'NOS'
>
> Not really.. this is a basic IP/IP tunnel. Very old stuff.
Well the BASIC thats GREAT but i wouldnt able to set it up ;-(
i have allready read the Adv-Routing-HOWTO (About 6 times the part
5.2. )
and i have tried to
ifconfig tunl0 10.0.1.1 pointopoint 172.19.20.21
route add -net 10.0.2.0 netmask 255.255.255.0 dev tunl0
but it dont work :(
there are 3 ip factories and in that basic there are only 2
i need to supply the system : tunnel source 'Thats my ADSL Fixed IP'
tunnel dest 'Thats the Router Which host my Tunnel'
(' i think thats the pointopoint filled ' )
my ip on the tunnel 'the tunnel is 4 ips 11.201.0.8/30'
'my ip is 11.201.0.10 and the other
is 9 so i should be able to ping there '
Any idea ???
>
>
> >Tunnel2 is up, line protocol is up
> > Hardware is Tunnel
> > Internet address is 10.200.0.2/30
> > MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
> > reliability 255/255, txload 1/255, rxload 56/255
> > Encapsulation TUNNEL, loopback not set
> > Keepalive set (10 sec)
> > Tunnel source 62.219.161.125, destination 212.25.114.74
> > Tunnel protocol/transport IP/IP (NOS), key disabled, sequencing
disabled
> > Checksumming of packets disabled
> > Last input 00:00:00, output never, output hang never
> > Last clearing of "show interface" counters never
> > Queueing strategy: fifo
> > Output queue 0/0, 0 drops; input queue 0/75, 0 drops
> > 30 second input rate 2000 bits/sec, 4 packets/sec
> > 30 second output rate 0 bits/sec, 0 packets/sec
> > 300 packets input, 14322 bytes, 0 no buffer
> > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
> > 0 packets output, 0 bytes, 0 underruns
> > 0 output errors, 0 collisions, 0 interface resets
> > 0 output buffer failures, 0 output buffers swapped out
>
>
> Ultimately, I don't recommend IP/IP tunnels in a preference
> to GRE tunnels but Linux supports BOTH.
>
> http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO-5.html
>
> --David
>
.---------------------------------------------------------------------------
-.
> | David A. Ranch - Linux/Networking/PC hardware
dranch@trinnet.net |
>
----!
> `----- For more detailed info, see
http://www.ecst.csuchico.edu/~dranch -----'
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-11-21 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100634366615516@msgid-missing \
--to=juda@pent900.com \
--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.