| Summary: | [PATCH] wicontrol(9) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Seth Kingsley <sethk> | ||||
| Component: | bin | Assignee: | Bill Paul <wpaul> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 5.0-CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Seth Kingsley
2000-10-20 08:40:01 UTC
Responsible Changed From-To: freebsd-bugs->wpaul Bill Paul wrote wicontrol - this looks like a simple patch though. State Changed From-To: open->closed This is no longer a problem. The default behaviour is now to use wi0 if no interface is specified. On Fri, Oct 20, 2000 at 12:36:20AM -0700, sethk@osd.bsdi.com wrote: > FreeBSD veritech.osd.bsdi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #4: > Thu Oct 19 00:14:24 PDT 2000 > root@veritech:/usr/src/sys/compile/VERITECH i386 > >Description: > The wicontrol utility fails to detect that no interface has been > specified when using the -e option as it does for other options. > Pretty self-explanitory. I committed something this week that fixes this. In an interface name isn't specified it defaults to wi0. There's a similar fix in to ancontrol. This was MFC'd yesterday. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] |