From: "Fiorangelo Peluso" <fiorangelo@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Forward + Routing
Date: Fri, 28 Nov 2003 09:03:56 +0000 [thread overview]
Message-ID: <marc-lartc-107001047918190@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106993512322200@msgid-missing>
Hi,
>** AND the opposite route back ON GATEWAY B1 TO Subnet A via GATEWAY B **
I already added this route! GATEWAY B1 can send packets to Subnet A
correctly... Seems just that packets outgoing from ipsec interface are not
routed anymore towards Subnet C via Gateway B1...
>If that doesn't work, you may need to ask the FreeS/WAN guys since it might
>be an erouting problem on GATEWAY B.
How?
Thanks
>From: Damion de Soto <damion@snapgear.com>
>To: Fiorangelo Peluso <fiorangelo@hotmail.com>
>CC: lartc@mailman.ds9a.nl
>Subject: Re: [LARTC] Forward + Routing
>Date: Fri, 28 Nov 2003 13:45:34 +1000
>
>Hi Fiorangelo,
>
>>Subnet A <-> GATEWAY A ------- VPN with FREE/SWAN --------- GATEWAY B <->
>>Subnet B <-> GATEWAY B1 (physically on Subnet B) <-> Subnet C
>>The question is: HOW DO I MAKE SUBNET C REACHABLE FROM SUBNET A?
>>
>>I created a new connection in ipse.conf specifying as leftsubnet just the
>>Subnet C. This way I can ping Subnet C from GATEWAY B but not from Subnet
>>A.. It seems to me that packets are not routed correctly if they came from
>>Subnet A! I already added a route to Subnet C on the GATEWAY B but it
>>seems to work only for packets from the Gateway and not for the forwarded
>>packets from Subnet A..
>You'll need a new ipsec.conf connection at GATEWAY A and GATEWAY B for
>Subnet A <-> Subnet C, (which I think you did)
>
>Then you need a route ON GATEWAY B TO Subnet C via GATEWAY B1 (which I
>think you did),
>** AND the opposite route back ON GATEWAY B1 TO Subnet A via GATEWAY B **
>
>If that doesn't work, you may need to ask the FreeS/WAN guys since it might
>be an erouting problem on GATEWAY B.
>
>That is assuming there is no NAT or Masquerading occuring anywhere.
>
>Regards,
>
>--
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Damion de Soto - Software Engineer email: damion@snapgear.com
>SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
> | Custom Embedded Solutions fax: +61 7 3891 3630
> | and Security Appliances web: http://www.snapgear.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> --- Free Embedded Linux Distro at http://www.snapgear.org ---
>
_________________________________________________________________
MSN Extra Storage: piena libertà di esprimersi e comunicare
http://www.msn.it/msnservizi/es/?xAPIDS4&DI\x1044&SU=http://hotmail.it/&HL=HMTAGTX_MSN_Extra_Storage
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-28 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 12:09 [LARTC] Forward + Routing Fiorangelo Peluso
2003-11-28 3:45 ` Damion de Soto
2003-11-28 9:03 ` Fiorangelo Peluso [this message]
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-107001047918190@msgid-missing \
--to=fiorangelo@hotmail.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.