SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0001497: selectable Uplink for VPN - MantisBT Endian Bugtracker
Endian Issue Tracker

Please see now our new Bugtracker system: JIRA

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001497Endian FirewallNetwork related (VPN, uplinks)public2008-11-28 16:142010-05-26 17:10
Assigned To 
PlatformOSOS Version
Product Version2.2-rc3 
Target VersionFixed in Version 
Summary0001497: selectable Uplink for VPN
DescriptionWould be nice to have a selection for the VPN Interface.

I have two active uplinks and want that IPSec would only listen on the main uplink and OpenVPN on the second uplink.
TagsNo tags attached.
Attached Files

- Relationships
child of 0001935confirmedpeter-endian issues to fix with ipsec (openswan) 

-  Notes
peter-endian (administrator)
2008-12-09 20:29

use policy routing for outgoing openvpn connections in order to define that it should exit on uplink2. (source == LOCAL)

with ipsec it is currently not possible to define an uplink. it will always use the main uplink
aender (reporter)
2008-12-10 16:01

I mean not outgoing traffic.

I mean the OpenVPN and IPSec Server. Incoming traffic or listening port.

So it should be possible to have the OpenVPN Server listen only on uplink1 and IPSec Server listen only on uplink 2.
peter-endian (administrator)
2008-12-11 13:55

openvpn listens on every uplink interface, so the client decides where to connect by configuring the uplink1 ip address or the main ip address.
you can block the openvpn port on a specified uplink using the system access.

ipsec is more problematic. it's currently not possible to bind it on another uplink than main. The other uplinks cannot be used for ipsec.

- Issue History
Date Modified Username Field Change
2008-11-28 16:14 aender New Issue
2008-11-28 16:14 aender Assigned To => peter-endian
2008-12-09 20:29 peter-endian Note Added: 0001849
2008-12-09 20:29 peter-endian Status new => feedback
2008-12-10 16:01 aender Note Added: 0001861
2008-12-11 13:55 peter-endian Note Added: 0001865
2009-06-10 12:55 peter-endian Assigned To peter-endian =>
2009-06-10 13:10 peter-endian Relationship added child of 0001935
2010-05-26 17:10 christian-endian Status feedback => closed
2010-05-26 17:10 christian-endian Resolution open => fixed

Copyright © 2005-2008 Endian, SRL. All rights reserved.

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker