[Openswan Users] X-WRT (Openwrt) - cannot identify with either end of this connection

Chris Patch chrispatch at intrstar.net
Wed May 2 12:18:27 EDT 2007

This is from a post earlier, please forgive the crappy cut and paste:

I ran into this problem as well when trying to install Openswan on
Openwrt White Russian 0.9 using X-Wrt based firmware file.  I spend
quite a while on it until I searched for "ifconfig: inet: Unknown host"
without the ipsec reference.  I believe the problem is that the X-Wrt
firmware file includes Busybox 1.4.0 and the standard White Russian has
Busybox 1.0.0.  Apparently the ifconfig in Busybox 1.4.0 does not like
the inet parameter.

Some additional information can be found with this Busybox bug report


Apparently, Busybox 1.0.0 will accept ifconfig commands with the inet
parameter but will exit with error.  Busybox 1.4.0 will not accept them
at all and errors out with "ifconfig: inet: Unknown host".

An easy way to fix this is by removing the inet parameter from line 146
of the ifconfig command in /usr/lib/ipsec/_startklips.  See the
following diff.  After changing this line, everything works perfectly.
I believe reverting to Busybox 1.0.0 should also work, but apparently
the syntax is not correct for 1.0.0 either, it is just more forgiving.
I am not sure who the bug should be filed with but I may start with

--- _startklips.old     Sat Mar 31 00:00:10 2007
+++ _startklips Sat Apr  7 01:51:25 2007
@@ -143,7 +143,7 @@
                # attach the interface and bring it up
                ipsec tncfg --attach --virtual $virt --physical $phys
-               ifconfig $virt inet $addr $type $otheraddr netmask $mask
+               ifconfig $virt $addr $type $otheraddr netmask $mask $mtu

        # if %defaultroute, note the facts

-----Original Message-----
From: users-bounces at openswan.org [mailto:users-bounces at openswan.org] On
Behalf Of users-request at openswan.org
Sent: Wednesday, May 02, 2007 10:29 AM
To: users at openswan.org
Subject: Users Digest, Vol 42, Issue 2

Send Users mailing list submissions to
	users at openswan.org

Message: 4
Date: Tue, 1 May 2007 22:32:30 +1000
From: "Sergio Aguilera" <checho.aguilera at gmail.com>
Subject: [Openswan Users] X-WRT (Openwrt) - "inet: Unknown host" & "We
	cannot identify ourselves with either end of this connection"
errors -
To: users at openswan.org
Cc: Daniel Giddings <daniel.giddings at gmail.com>, epitaph at gmail.com,
	mbonny at gmail.com
	<230a5d770705010532y4ff1b8f2ie2e9cfddaa7cbe9d at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi All, I have been have some issues trying to setup an  IPSec VPN
between Mitsubishi R100 (Asus WL500g) with X-WRT (White Russian  0.9)
and a Billion 7404VGM Router.

I'm getting the following errors:

1-)  "ifconfig: inet: Unknown host" error when I start/restart IPSec

root at OpenWrt:/bin$ ipsec setup restart
ipsec_setup: rmmod: ipsec: Success

ipsec_setup: Stopping Openswan IPsec...

ipsec_setup: Starting Openswan IPsec 2.4.6...

ipsec_setup: insmod: a module named ipsec already exists

ipsec_setup: ifconfig: inet: Unknown host

2-) "We cannot identify ourselves with either end of this connection"
when I try and bring up a tunnel

root at OpenWrt:/etc/ipsec.d/private$ ipsec auto --up bonny
022 "bonny": We cannot identify ourselves with either end of this

The only clue that I have been able to find is on the following post
which talks about and issue with ifconfig in Busybox 1.4.0.

I'm clueless as to how I should attempt to fix this problem and I
would appreciate your help as I have now spent a long time trying to
get this sorted.



More information about the Users mailing list