From: Mike Goldman (whig_at_3dresearch.com)
Date: Thu Aug 15 2002 - 23:08:04 CEST
Here is a problem, and a workaround.
I have a Linux 2.4 server which creates a large number of alias
interfaces at startup time (i.e., eth0:0, eth0:1 ... eth0:n). Using the
Debian package of FreeSWan (Version: 1.96-1.2), and upon attempting to
bring up a connection with "ipsec auto --up <connection>" I will receive
the error, "we have no ipsecN interface for either end of this connection".
This will occur regardless of whether the eth0:n aliases are moved to a
separate ethernet interface (i.e., eth1:n). However, if FreeSWan is
started before the alias interfaces are created, there will be no
subsequent error of the stated type.
Therefore, those who have been having this error should know, make sure
you initialize FreeSWan before you create alias interfaces.
As for FreeSWan itself, I believe this is likely to be an overflow bug
where the number of available interfaces at startup exceeds some bound.
Hopefully this can be identified and fixed to prevent the workaround
from being necessary in the future.
_______________________________________________
Users mailing list
Users_at_lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users
This archive was generated by hypermail 2.1.4 : Fri Aug 16 2002 - 01:19:43 CEST