Re: tap(4) should go UP if opened

2007-03-16 Thread Frank Behrens
Bruce M. Simpson <[EMAIL PROTECTED]> wrote on 14 Mar 2007 13:09: > Please try the attached patch, which puts this behaviour under a sysctl. It works well as expected. Many thanks! I created a PR http://www.freebsd.org/cgi/query-pr.cgi?pr=110383 with the hope the patch will be commited. Regards,

Re: tap(4) should go UP if opened

2007-03-14 Thread Frank Behrens
Bruce, many thanks for your fast response. Bruce M. Simpson <[EMAIL PROTECTED]> wrote on 14 Mar 2007 13:09: > The conditional in the second patch is a no-op as the open will be > forbidden if the user did not have privilege to open the tap. Bringing No. A process running with root rights can al

Re: tap(4) should go UP if opened

2007-03-14 Thread Bruce M. Simpson
Hi, Frank Behrens wrote: If we have no possibility to mark the interface as UP for the non-root process the net.link.tap.user_open=1 is useless, because we can not transmit any packets. With the patch the interface goes UP only, when the administrator allowed non-root user access. The co

Re: tap(4) should go UP if opened

2007-03-14 Thread Frank Behrens
Bruce M. Simpson <[EMAIL PROTECTED]> wrote on 9 Mar 2007 12:30: > However, we also support the creation of tap/tun instances by > non-super-users, so there is motivation for the change. Configuring a > tap interface to up by a non-superuser should only be permitted if the > interface itself was

Re: tap(4) should go UP if opened

2007-03-09 Thread Frank Behrens
Bruce, thanks for your answer! Bruce M. Simpson <[EMAIL PROTECTED]> wrote on 9 Mar 2007 12:30: > Frank Behrens wrote: > > How does tun(4) handle this? tun(4) is also set to down, when closed. It is > > not set to up, when > > ist is opened, but when an address is assigned by the user process. Th

Re: tap(4) should go UP if opened

2007-03-09 Thread Bruce M. Simpson
Frank Behrens wrote: How does tun(4) handle this? tun(4) is also set to down, when closed. It is not set to up, when ist is opened, but when an address is assigned by the user process. This is fine, because it needs always an ip address. tap(4) as layer 2 tunnel device does not need an ip addres

tap(4) should go UP if opened

2007-03-09 Thread Frank Behrens
I want to diskuss the tap(4) behaviour before I create a PR: The tap(4) interface does not go automatically in UP state (IFF_UP) when opened by a process. Therefore an additional command "ifconfig tapx up" is necessary, which can execute root only. On the other site the interface goes down aut