On Mon, Oct 15, 2012 at 10:28:15AM +0200, Gabriele Bulfon wrote:
>
> I tried adding the same /dev/tun to 2 different zones, and it didn't
> complain, both zones boot. One I start openvpn on one zone, I can't start
> it on the other zone (complaining that it can't create the interface
> because "file exists"...), so I stop openvpn on the first zone, and I can
> start it on ther other zone... Any other idea??
Is the name of both /dev/tun instances "tun0" or some other identical name in
each zone?
IF that's the case, you may need to get down/dirty into its open() kernel
code and have it take into account which zone you're in. If you look at the
rest of TCP/IP, the netstack_t data structure hold which zone's TCP/IP stack
you're using. You probably need tun/tap/whatever-it's-called to become
netstack-aware.
Dan
p.s. Dumb question: the tun/tap you're using is essentially IP over {,d}TLS,
right?
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
