Date: Wed, 4 Feb 2009 20:26:47 +0000 (GMT) From: Iain Hibbert <plunky@rya-online.net> To: Alexander Motin <mav@mavhome.dp.ua> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: pan profile support in freebsd Message-ID: <1233779207.215414.2993.nullmailer@galant.ukfsn.org> In-Reply-To: <4989F23F.8040102@mavhome.dp.ua> References: <1233365217.00068654.1233354838@10.7.7.3> <4988DCCC.80201@mavhome.dp.ua> <bb4a86c70902031622hdc5231g1c9ce33f17842a1e@mail.gmail.com> <4988EBAC.3080202@mavhome.dp.ua> <1233760229.131312.504.nullmailer@galant.ukfsn.org> <4989E0F7.3020301@mavhome.dp.ua> <1233775908.626621.2538.nullmailer@galant.ukfsn.org> <4989F23F.8040102@mavhome.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 Feb 2009, Alexander Motin wrote: > Iain Hibbert wrote: > > One thing that I have in mind is to make btpand shutdown the tap interface > > when exiting (as it marks it up when starting). Would that make it > > possible to use devd to trigger a reconnect if desired? I think its > > better to have a "event->action" model rather than hang it all together > > with scripts. > > It already removes UP status from interface, so there is action which could be > tracked by devd. Ah, I see. That is a difference in FreeBSD tap(4) device and I wondered about that but will put it on my list to see if its desireable for NetBSD, rather than modifying btpand to do the same. > No need to destroy interface if it was not created by you. no, thats all automatic > But from other side devd is more complicated and system-wide case that some > trivial custom shell script, so I would prefer to use it just for something > common, like running dhclient with adding something like ifconfig_tap1="DHCP" > to rc.conf alike to normal Ethernets. There may be trouble there because network is started before bluetooth, but adding a 'stay in foreground' switch should not be difficult. iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1233779207.215414.2993.nullmailer>