tinc - Mar 2015 - Configuration advice on a single interface server

Is it possible to configure a bridge mode VPN with only a single physical
interface eth0. The scenario is that the proposed tinc server is assigned a
static 10.10.145.254/24 that is connected to a Cisco router. Incoming
traffic can be set up to be forwarded to this server.

Remote tinc client has a need to receive multicast hence the server must be
configured in bridge mode. However, I can't get my head around configuring
the bridge for the server, and the setup for the client.

Any advice will be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150318/e35a3383/attachment.html>

On Wed, Mar 18, 2015 at 10:38:24AM +0800, Terry T wrote:
> Is it possible to configure a bridge mode VPN with only a single physical
> interface eth0. The scenario is that the proposed tinc server is assigned a
> static 10.10.145.254/24 that is connected to a Cisco router. Incoming
> traffic can be set up to be forwarded to this server.
An example of how to set up tinc with a bridge on Linux can be found
here:

http://www.tinc-vpn.org/examples/bridging/
> Remote tinc client has a need to receive multicast hence the server must be
> configured in bridge mode. However, I can't get my head around
configuring
> the bridge for the server, and the setup for the client.
The setup on the client is trivial; just give the virtual network
interface an address in the same range as on the server's eth0. You can
even use DHCP if there is a DHCP server on the server's LAN.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150318/908e4981/attachment.sig>

Sorry, Guus

I know how to bridge an internal adapter to a tap device. My problem is
that this box only has one physical interface.

Internet ----->[Cisco router]------------[network switch]--------{PCs,
Linux VPN server}

A typical server bridge setup is for the LAN side of the adapter to be
bridged to the tap, and the external client connecting to its external
adapter be serviced by the vpn program. In my situation, my one physical
adapter is functioning both as an internal LAN adapter and also responsible
for servicing requests from the remote client.

On Wed, Mar 18, 2015 at 4:40 PM, Guus Sliepen <guus at tinc-vpn.org>
wrote:
> On Wed, Mar 18, 2015 at 10:38:24AM +0800, Terry T wrote:
>
> > Is it possible to configure a bridge mode VPN with only a single
physical
> > interface eth0. The scenario is that the proposed tinc server is
> assigned a
> > static 10.10.145.254/24 that is connected to a Cisco router. Incoming
> > traffic can be set up to be forwarded to this server.
>
> An example of how to set up tinc with a bridge on Linux can be found
> here:
>
> http://www.tinc-vpn.org/examples/bridging/
>
> > Remote tinc client has a need to receive multicast hence the server
must
> be
> > configured in bridge mode. However, I can't get my head around
> configuring
> > the bridge for the server, and the setup for the client.
>
> The setup on the client is trivial; just give the virtual network
> interface an address in the same range as on the server's eth0. You can
> even use DHCP if there is a DHCP server on the server's LAN.
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <guus at tinc-vpn.org>
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150318/870acc36/attachment.html>