On Thu, 6 Aug 2015, Gleb Smirnoff wrote:
> As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers
> undergo change of not being an interface anymore. Historically in FreeBSD
> 802.11 stack, 802.11 devices called if_attach() and created an interface.
> Later this was generalized and
panic.
So, how is this supposed to work? Who is supposed to be creating the
enc0 interface?
Thanks,
Gavin
--
Gavin Atkinson
FreeBSD committer and bugmeister
GPG: A093262B (313A A79F 697D 3A5C 216A EDF5 935D EF44 A093 262B)
___
freebsd-net@freebsd
On Tue, 2010-01-12 at 11:45 +1100, Sam Wun wrote:
> Hi Gavin,
>
> The reason I want to stick with i386 is because about few years ago
> when I tried AMD release of FreeBSD, it didn't have the same level of
> proficiency as i386 release of FreeBSD - packagThat was my impression
> at that time. I ho
On Mon, 11 Jan 2010, Sam Wun wrote:
> This server is built with Xeon cpu processor, Intel based.
> Can FreeBSD 8+ fully compatible with this server like those ordinary
> Intel i386 machine?
Although it's hard to say (the Sun website doesn't realy give enough spec
details), I'd be surprised if it
On Tue, 10 Nov 2009, John Baldwin wrote:
On Tuesday 10 November 2009 4:45:03 pm Gavin Atkinson wrote:
I managed to get a panic when running wpa_supplicant:
System call ioctl returning with the following locks held:
exclusive sleep mutex an0 (network driver) r=0 (0xc58fc180) locked @
/usr/src
On Fri, 6 Nov 2009, John Baldwin wrote:
I have a patchset that converts all the remaining users of if_watchdog to
using a private callout instead. In some cases the the driver already used a
private timer to drive a stats timer and I merely hooked into that timer. In
other cases a new callout
On Sun, 21 Sep 2008, Gavin Atkinson wrote:
I'm attempting to backport the iwn(4) driver for the Intel 4965 driver from
-HEAD to RELENG_7 and am getting stuck with it at one particular point: WPA
authentication times out.
As a followup to this, with a bit of help from Sam Leffler, I&#
On Sun, 21 Sep 2008, Gavin Atkinson wrote:
I'm attempting to backport the iwn(4) driver for the Intel 4965 driver from
-HEAD to RELENG_7 and am getting stuck with it at one particular point: WPA
authentication times out.
I've includewd the output with all options within wlandebug
Hi all,
I'm attempting to backport the iwn(4) driver for the Intel 4965 driver
from -HEAD to RELENG_7 and am getting stuck with it at one particular
point: WPA authentication times out.
I've so far tried to both take the -HEAD driver and de-vapify etc. it, and
also to take a pre-vap version
The following reply was made to PR kern/126564; it has been noted by GNATS.
From: Gavin Atkinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/126564: [ath] doesn't work with my PCI-E X1 wireless
Date: Mon, 18 Aug 2008 15:11:58 +0100 (BST)
-- Forwar
The following reply was made to PR kern/123166; it has been noted by GNATS.
From: Gavin Atkinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: [Fwd: RE: kern/123166: [re] CARP messages filtered by Realtek
driver on > 6.2]
Date: Tue, 29 Apr 2008 09:13
On Mon, 1 Jan 2007, Rene Ladan wrote:
I build the wpi driver (version 20061109) on 7.0 CURRENT (20061229). It
works fine, but it hangs my laptop after 'a while'. The only thing that
keeps working is escaping to ddb. The laptop has the 4222 version of
the wpi chipset.
I'm working on the driv
On Thu, 28 Dec 2006, Steve Clement wrote:
It throws quite a lot of 702 errors at me, especially when there is heavy
traffic load!
Yes, I need to look into these at some point.
Also I am currently in Berlin at the CCC (events.ccc.de) and the WiFi traffic
is quite heavy and I don't get a packe
On Tue, 26 Dec 2006, Gabor Kovesdan wrote:
I don't have the knowledge to work on it, but I'd like to test your version.
I always had allocation issues with a wpi driver that was flying over and
over threads and could never get it to work, so I really would like to test
your one if you could upl
Hi all,
Is anybody actively developing this driver?
I've been debugging it for the last day or two and am now at the point
where it's pretty stable for me (at least, I no longer get deadlocks and
the issue of the firmware getting confused seems resolved). I have a load
of other changes I in
Hi,
It seems to me that assigning an IP address to a vlan device (parent
device bge0) isn't enough to get the interface working - I need to
manually bring the parent interface up.
Freshly rebooted system with no network configuration in /etc/rc.conf
wiggum# uname -a
FreeBSD wiggum.york.ac.uk 6.
On Sun, 2005-09-25 at 14:37 -0700, Brooks Davis wrote:
> On Thu, Sep 22, 2005 at 02:41:05PM +0400, Yar Tikhiy wrote:
> > Hi folks,
> >
> > As our ifconfig(8) is growing more options for special interface
> > types, inconsistencies sneak into their syntax. In particular,
> > -vlandev takes a usele
On Wed, 4 May 2005, Josef Karthauser wrote:
On Wed, May 04, 2005 at 06:13:22PM +0100, Gavin Atkinson wrote:
I believe I am seeing similar problems to you, though uptime for me is
generally measurable in days rather than minutes. I've found that
adding an explicit "allow all from any t
On Wed, 2005-05-04 at 15:24 +0100, Josef Karthauser wrote:
> It appear that ipfw doesn't work with bridge in 5.3 and 5.4. The
> symptoms are that the bridge stops forwarding packets altogether,
> for me a few minutes after it is set up. It takes a
>
> # net.link.ether.bridge_ipfw=0 && sleep 5 &&
On 15 Apr 2002, Arno J. Klaassen wrote:
> I did not pay much attention, but since a couple of weeks
> (the latest "daylight savings in Europe") mu ntp
> programs do not function anymore and host clocks
> drift further and further (both for machines
> I upgraded to -stable as for machines whic
Hi,
I have a problem I have so far been unsuccessful in solving. I want to
detect if a particular network interface has a link, before this interface
has an IP address configured.
>From looking at the source to ifconfig, which successfully does this, the
attached code should work, but doesn't.
21 matches
Mail list logo
