From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problems with Core 70 and OpenVPN N2N
Date: Fri, 12 Jul 2013 00:06:39 +0200 [thread overview]
Message-ID: <1373580399.10320.44.camel@hughes.tremer.info> (raw)
In-Reply-To: <C575C225-8F3B-4697-9F7A-89B2D6E7DDEE@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
Could you provide the iptables ruleset that is loaded?
This should not be caused by the latest NAT changes in core update 70.
But that's just a wild guess.
-Michael
On Thu, 2013-07-11 at 20:33 +0200, Erik K. wrote:
> Hi all,
> have tried today Core 70 and OpenVPN N2N and i have had problems to establish the connection.
>
> The infrastructure:
>
> IPFire (remote) <--> Router <--> [ Internet ] <--> (local) Router <--> (local) IPFire
>
> So both sides with double NAT. The log messages gives me the following back
>
> Jul 11 18:17:35 ipfire Testn2n[13565]: UDPv4 link remote: 192.168.20.2:5329
> Jul 11 18:19:09 ipfire Testn2n[13808]: TLS Error: client->client or server->server connection attempted from 192.168.20.2:5329
> Jul 11 18:18:01 ipfire Testn2n[13565]: event_wait : Interrupted system call (code=4)
> have never seen this message (in the middle) before...
>
> So i looked to the configuration file on the TLS-client where the "Remote Host/IP" was stated with the 192.168.20.2 (red0 IP), i changed it then to the remote IP (in versions before Core 70 this was not necessary) and the following log output was stated.
>
> Jul 11 20:22:49 ipfire Testn2n[6875]: Expected Remote Options hash (VER=V4): '9e986809'
> Jul 11 20:22:49 ipfire-bbach Testn2n[[6875]: UDPv4 link remote: 172.11.xx.xx:5329
> Jul 11 20:23:50 ipfire Testn2n[[6875]: [UNDEF] Inactivity timeout (--ping-restart), restarting
>
>
> Looks like a closed firewall. Portforwarding from both upstream routers to IPFire was made, outgoing FW was in mode 0 .
>
> May some one have an idea what´s causing this problem ?
>
>
> Greetings
>
>
> Erik
>
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2013-07-11 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 18:33 Erik K.
2013-07-11 22:06 ` Michael Tremer [this message]
2013-07-12 9:04 ` Erik K.
2013-07-12 11:24 ` Michael Tremer
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=1373580399.10320.44.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox