All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Martin <dan.martin@thecloud.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IP Tunneling
Date: Wed, 27 Apr 2005 10:45:01 +0000	[thread overview]
Message-ID: <ece05e9186274ed7dc769e34040807bf@thecloud.net> (raw)
In-Reply-To: <marc-lartc-98373938216783@msgid-missing>

If I'm going over stuff covered already on this list, please let me 
know!!  Sorry... this is my first post!!

If you've just used the iptunnel command, you'll also need to use 
ifconfig with the pointopoint type to set up an interface to route 
traffic through.  The IP address's on either end of the point to point 
interface should be the IP's you want to route traffic between once 
you've reached the subnets at each end of the tunnel.  If you want to 
route more traffic across the link you use "ip route add 10.0.0.0/24 
dev ipiptunnelname" or similar.

Also, you can view the traffic either encapsulated, by running tcpdump 
on your physical interface, or un-encapsulated by running it on your 
pointopoint interface.

Dan!

On 27 Apr 2005, at 09:22, Taylor, Grant wrote:

>> Hello
>> I have looked at SSH tunneling, but what I know I think that's not the
>> best solution for me. After some research, IPIP or GRE tunnel seems 
>> to fit
>> me best. But I don't find any good documentation, neither the LARTC 
>> howto
>> is brings up my problem.
>> I'd figured out that I will use iptunnel or similar to set up an
>> IPIP-tunnel, like:
>> iptunnel add dev tunl1 mode ipip local a.b.c.d remote e.f.g.h
>> and the same on the other side (just switching local and remote 
>> addresses)
>> to tunnel the public IP address e.f.g.h (on the /25-box) to tunl0 at
>> a.b.c.d (my public IP at home). But the connection betweeen me and the
>> remote host freezes, so I guess that's not enough. What more do I 
>> have to
>> do?
>
> Is the ""freeze that you are talking about data through the tunnel or 
> is it the initialization it's self?  If it is the former, check to 
> make sure that your firewall is not blocking traffic that would be 
> flowing through the tunnel.  Namely if your filter table FORWARD chain 
> policy is set to DROP and you don't have an explicit allow for traffic 
> flowing through the tunnel interface you will not be able to get 
> things to work.  I'll have to play with GRE / IPIP tunnels to see if I 
> can offer any advice.
>
>
>
> Grant. . . .
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-04-27 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-15 21:50 [LARTC] IP tunneling papyrus
2000-10-15 23:10 ` bert
2005-04-26 10:53 ` [LARTC] IP Tunneling phonic
2005-04-27  5:25 ` Taylor, Grant
2005-04-27  7:38 ` phonic
2005-04-27  8:22 ` Taylor, Grant
2005-04-27 10:45 ` Dan Martin [this message]
2005-04-27 10:53 ` phonic
2005-04-27 11:02 ` phonic
2005-04-27 11:13 ` phonic
2005-04-27 18:19 ` Damjan
2005-04-27 18:32 ` phonic
2005-04-28  1:58 ` Taylor, Grant
2005-04-28 11:14 ` Damjan
2005-04-28 16:46 ` Taylor, Grant
2005-04-29  2:22 ` Dan Martin

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=ece05e9186274ed7dc769e34040807bf@thecloud.net \
    --to=dan.martin@thecloud.net \
    --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.