Re: StrongVPN config instructions for IRLP
It sounds like I could go either way then. My original plan was to assigntoggle quoted messageShow quoted text
an AMPRnet public IP address in the 22.214.171.124/8 range (I have an adequate
allocation) so the IRLP node would have a different IP address from the
router. Traffic would just route there via the tunnel.
I can possibly work around that using tap, although I already have the
standard IRLP audio ports pointing to my secondary node's private IP address
when it's parked at home.
Ponder, ponder. I appreciate the detailed response.
From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of David
Cameron - IRLP
Sent: Friday, June 21, 2019 4:03 PM
Subject: Re: [IRLP] StrongVPN config instructions for IRLP
I agree that the tap interface is ideal for what we are doing. It mirrors
plugging the remote node right into the same switch that the server is
plugged into - Total transparent. Of course that means you see all the
broadcast traffic from the LAN segment.
The tun interface is nice because you can have better and more control over
the bandwidth usage, but then you have to perform some fancy routing and
forwarding to make it work.
The tap interface also helps because you don't have to worry about routing
that makes your source IP different from the destination IP.
On 2019-06-21 14:23, Jim MacKenzie wrote:
Thanks Dave. I'll have a good look at this and do a tinker or two.