Package: strongswan
Version: 4.5.2-1.3
Severity: normal
You see here 4.5, but this report is about 4.6.4-6 version, because it totally
breaks down our network and I was compelled to downgrade it in order to restore
network connectivity.
It may be possible I am only one who encounter this problem, because of very
unusual configuration:
leftsubnet = 192.168.0.0/24
rightsubnet = 0.0.0.0/0
With this configuration I had a problem in version 4.5 also, but I have solved
it by deleting second default route from table 220. May be it is bad solution,
but it works. Meanwhile with 4.6 version I've got very different, strange and
fatal problem. With this configuration the machine where this strongswan is
running announces all address of local network 192.168.0.0/24 as it's own, so
all IP address becomes binded with the same MAC address and network stops
working: nobody can connect each other.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages strongswan depends on:
ii strongswan-ikev1 4.5.2-1.3
ii strongswan-ikev2 4.5.2-1.3
strongswan recommends no packages.
Versions of packages strongswan suggests:
pn network-manager-strongswan <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
