Hi,
On Sun, Nov 17, 2013 at 03:17:05PM -0500, Ryan Whelan wrote:
> Would it be difficult to modify OpenVPN so it allocated a TAP/TUN per
> client on connection, so each virtual interface was connected to a single
> client? (removing it on client disconnect/drop)
Significantly so. The code assu
What feature does "--remote-random-hostname" give you that having a
10second TTL on one DNS record wouldn't?
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 481 8171
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
Would it be difficult to modify OpenVPN so it allocated a TAP/TUN per
client on connection, so each virtual interface was connected to a single
client? (removing it on client disconnect/drop) This is going to be a
shared environment and the ability to apply security to individual
interfaces via a
Hi,
this is actually not only asking for an ACK, but also for users that
rely on the *old* behaviour ("foo.bar.gov" -> "foo-0x12345.bar.gov")
and would be surprised.
gert
On Sun, Nov 17, 2013 at 03:30:20PM +0100, Gert Doering wrote:
> Documentation examples, description and code were disagreeing
Hi,
On Sun, Nov 17, 2013 at 02:31:33AM -0500, Ryan Whelan wrote:
> The reason I'd been using tap was because the multicast router (mrd6)
> didn't seem to be working with tun. (the clients will be sending multicast
> traffic) I'm only slightly familiar with multicast and barely anymore
> familiar
