Date: Mon, 1 Feb 2016 08:20:41 -0600 (CST) From: "Valeri Galtsev" <galtsev@kicp.uchicago.edu> To: "Ian Smith" <smithi@nimnet.asn.au> Cc: "Polytropon" <freebsd@edvax.de>, freebsd-questions@freebsd.org Subject: Re: "epilogue" script? Message-ID: <53364.76.192.184.12.1454336441.squirrel@cosmo.uchicago.edu> In-Reply-To: <20160201175827.E51785@sola.nimnet.asn.au> References: <mailman.107.1454155202.96392.freebsd-questions@freebsd.org> <20160131000408.N51785@sola.nimnet.asn.au> <63014.76.192.184.12.1454168056.squirrel@cosmo.uchicago.edu> <20160201175827.E51785@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, February 1, 2016 1:11 am, Ian Smith wrote: > On Sat, 30 Jan 2016 09:34:16 -0600 (CST), Valeri Galtsev wrote: > > On Sat, January 30, 2016 8:19 am, Ian Smith wrote: > [..] > > > We don't really know what Valeri wants to run, and whether it's one > or > > > more daemons, maybe including long-running background scripts, that > may > > > need start|stop|status control via service(8), or whether it's more > > > simply one or more one-off tasks to be run sometime after startup? > > > > It is rather simple thing which I need. I'm trying to set up openvpn, > and > > I need _after_ starting openvpn daemon to add tap0 interface to the > bridge > > then set IP on the bridge and on tap0 interface the same as that of > real > > interface which is member of this bridge. This is the only way I > managed > > to make openvpn really work (by trial and error). I'm kind of not > inclined > > to use openvpn's mechanism (which they seemingly have) to do it (it is > not > > a first time I spent this long setting up something on FreeBSD, but it > was > > the first time I spent this time... hm, not that productive. My > ignorance > > is to blame, still...) > > I know absolutely nothing about openvpn or tap interfaces so can't help > with that, except to suggest freebsd-net@ as the best place to ask. Thanks again, I will. I'm kind of puzzled by the need to set IP on all bridge members, whereas setting IP on the bridge itself should suffice. And I am kind of not able to overcome unrelated problem I create by adding physical interface to bridge: I have DHCP server on that same machine which (no matter whether DHCP server is jail or on host machine itself) gets blocked when I make physical interface member of a bridge, although it is my understanding that the bridge works on the same layer, so something is wrong with what I'm doing. Valeri > > cheers, Ian > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53364.76.192.184.12.1454336441.squirrel>