[haiku-commits] Re: haiku: hrev51067 - in src: add-ons/network_settings/openvpn preferences/network

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Thu, 06 Apr 2017 10:29:03 -0500

On 2017-04-06 10:25, kallisti5 wrote:

On 2017-04-06 04:14, Axel Dörfler wrote:
Am 06/04/2017 um 07:19 schrieb Adrien Destugues:
6516aed58b55: network preflet: Make InterfaceListItem dumber
  * Allows us to use InterfaceListItem for non-physical
    interface things (like a VPN connection)
Is there a reason a VPN connection is not a BNetworkDevice? That could
come in useful in many other places, so it sounds better than writing
ad-hoc code just in the network preferences?

I would assume that there is no other way to implement a VPN than to
have a BNetworkDevice. Or I surely hope so, at least...
Alex, what are you up to? :-)

Any kind of VPN connection will likely be centered around a definition
of what the vpn connection should look like.  Traditionally the network
devices created for a VPN connection are created when connecting, then
tore down when disconnecting.

aka... the network device won't exist until the vpn tunnel is constructed,
so how can BNetworkInterfaceItem exist before the interface exists?


With that said, I guess when we create a VPN connection we could create
an inactive interface that has the VPN information bound to it... then enable
it when the connection is active. I don't think we'll be able to use
things like OpenVPN as-is with that design though.

I guess i'm thinking about this stuff from a linux perspective on constructing
VPN tunnels.

 -- Alex

Other related posts: