Re: cloning network interfaces

2001-06-25 Thread Brooks Davis
On Mon, Jun 25, 2001 at 01:31:06AM +0900, Hajimu UMEMOTO wrote: > It seems fine to me. > I just tried it on my box. You forget to include prototype change of > in_gif_input() in sys/net/if_gif.h. It's defined in sys/netinet/in_gif.h and I forgot to include it in my diff. Sorry about that. > BT

Re: cloning network interfaces

2001-06-24 Thread Hajimu UMEMOTO
> On Fri, 22 Jun 2001 12:51:13 -0700 > Brooks Davis <[EMAIL PROTECTED]> said: brooks> Ok, after a week and a half of doing other things, I've got a patch brooks> together which adds interface cloning based on NetBSD's code. The brooks> difference is that you may pass an interface of the

Re: cloning network interfaces

2001-06-22 Thread Brooks Davis
On Wed, Jun 13, 2001 at 04:07:16AM +0900, Hajimu UMEMOTO wrote: > I like your idea. > I'm serving tunnel broker using DTCP (Dynamic Tunnel Configuration > Protocol) in our ISP. So, I'm grad if we have dynamic gif creation, > too. Ok, after a week and a half of doing other things, I've got a patc

Re: cloning network interfaces

2001-06-12 Thread Hajimu UMEMOTO
> On Mon, 11 Jun 2001 14:20:31 -0700 > Brooks Davis <[EMAIL PROTECTED]> said: brooks> On Sun, Jun 10, 2001 at 11:29:07PM +0900, Hajimu UMEMOTO wrote: > I think it is not BSD network way. Recent NetBSD has network > interface cloning. It uses SIOCIFCREATE and SIOCIFDESTROY. It may > goo

Re: cloning network interfaces

2001-06-11 Thread Brooks Davis
On Sun, Jun 10, 2001 at 11:29:07PM +0900, Hajimu UMEMOTO wrote: > I think it is not BSD network way. Recent NetBSD has network > interface cloning. It uses SIOCIFCREATE and SIOCIFDESTROY. It may > good to port it to FreeBSD. I've looked it over and I generally like it. There is one problem th

Re: cloning network interfaces

2001-06-11 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Robe rt Watson writes: >> http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff >> >> has been updated. I'm still thinking about adopting the NetBSD >> SIOIF{CREATE,DESTORY} interface. > >An advantage to also supporting the ioctl interface is that it permits >i

Re: cloning network interfaces

2001-06-11 Thread Brooks Davis
On Mon, Jun 11, 2001 at 02:40:54PM -0400, Robert Watson wrote: > An advantage to also supporting the ioctl interface is that it permits > interface cloning to be used on systems where devfs is not used, or where > there are parts of the system where devfs is unavailable (i.e., various > forms of c

Re: cloning network interfaces

2001-06-11 Thread Robert Watson
On Mon, 11 Jun 2001, Brooks Davis wrote: > On Mon, Jun 11, 2001 at 08:27:37AM -0700, Peter Wemm wrote: > > Personally, I'd prefer create/destroy instead of plumb/unplumb. The Solaris > > plumb command is for doing 'STREAMS plumbing' - ie: connecting all the > > streams pipes and modules togethe

Re: cloning network interfaces

2001-06-11 Thread Brooks Davis
On Mon, Jun 11, 2001 at 08:27:37AM -0700, Peter Wemm wrote: > Personally, I'd prefer create/destroy instead of plumb/unplumb. The Solaris > plumb command is for doing 'STREAMS plumbing' - ie: connecting all the > streams pipes and modules together. Creating/deleting interfaces on > BSD systems I

Re: cloning network interfaces

2001-06-11 Thread Peter Wemm
Brian Somers wrote: > > I went ahead and nuked the auto-creation and -D flag in favor of plumb > > and unplumb in the patch at: > > > > http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff > > > > This version includes a change to rc.network to plumb gif interfaces > > before calling gifcreate

Re: cloning network interfaces

2001-06-10 Thread Brooks Davis
On Sun, Jun 10, 2001 at 11:29:07PM +0900, Hajimu UMEMOTO wrote: > I think it is not BSD network way. Recent NetBSD has network > interface cloning. It uses SIOCIFCREATE and SIOCIFDESTROY. It may > good to port it to FreeBSD. I'll take a look at it. I'm not convinced the /dev/if_gif way is wro

Re: cloning network interfaces

2001-06-10 Thread Hajimu UMEMOTO
Hi, > On Fri, 8 Jun 2001 19:19:04 -0700 > Brooks Davis <[EMAIL PROTECTED]> said: brooks> Following Brian's suggestion, I've modified gif to create a /dev/if_gif brooks> device with is controlled by the IOCIFMANAGE ioctl which allows creation brooks> and deletion of specific devices and c

Re: cloning network interfaces

2001-06-10 Thread Brian Somers
> I went ahead and nuked the auto-creation and -D flag in favor of plumb > and unplumb in the patch at: > > http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff > > This version includes a change to rc.network to plumb gif interfaces > before calling gifcreate. This will still trip up users w

Re: cloning network interfaces

2001-06-09 Thread Brooks Davis
On Sat, Jun 09, 2001 at 07:02:14PM -0700, Brooks Davis wrote: > On Sat, Jun 09, 2001 at 09:24:22PM +0100, Brian Somers wrote: > > I think it'd be better to use the solaris ``plumb'' keyword. I can't > > recall how it works (something like ``ifconfig gif0 plumb'' - I > > haven't got a Solaris ma

Re: cloning network interfaces

2001-06-09 Thread Brooks Davis
On Sat, Jun 09, 2001 at 09:24:22PM +0100, Brian Somers wrote: > I think it'd be better to use the solaris ``plumb'' keyword. I can't > recall how it works (something like ``ifconfig gif0 plumb'' - I > haven't got a Solaris machine handy here), but it seemed cleaner, > making it more obvious wh

Re: cloning network interfaces

2001-06-09 Thread Brian Somers
> Ok, I've got the quick and dirty way working for testing (a nine line > clone handler works great for that), but I think Brian's suggestion is > probably best for a real solution especialy since it's rather easier to > check for permissions before allowing creation this way. My current > patch

Re: cloning network interfaces

2001-06-08 Thread Brooks Davis
Following Brian's suggestion, I've modified gif to create a /dev/if_gif device with is controlled by the IOCIFMANAGE ioctl which allows creation and deletion of specific devices and creation of wildcard devices. I've hacked ifconfig to support this in a general manner. If you know which one you

Re: cloning network interfaces

2001-06-07 Thread Brooks Davis
On Thu, Jun 07, 2001 at 12:19:53PM +0100, Brian Somers wrote: > > The quick and dirty way: > > > > Make a clone handler despite the fact that there is no /dev > > entry needed. You don't actually have to create a dev entry > > in the clone handler, you could just create the gif_inter

Re: cloning network interfaces

2001-06-07 Thread Brian Somers
> In message <[EMAIL PROTECTED]>, Brooks Davis writes: > > >With network devices that are also normal devices the way tun is, > >you do this by just implementing a dev_clone event handler so when the > >user attempts to open a non-existent instance it's created. The problem > >with gif is that t

Re: cloning network interfaces

2001-06-06 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Brooks Davis writes: >With network devices that are also normal devices the way tun is, >you do this by just implementing a dev_clone event handler so when the >user attempts to open a non-existent instance it's created. The problem >with gif is that there's no de