David Horn wrote:
> I made a minor change to ifconfig to try kldloading the interface name
> specified on the create wlandev (ifconfig already tries for
> normal invocations, just needed to try with the wlandev interface)
> [...]
> This works nicely, however at startup, I still do not get
On Wed, Mar 18, 2009 at 5:37 AM, Oliver Fromme wrote:
> David Horn wrote:
> > I made a minor change to ifconfig to try kldloading the interface name
> > specified on the create wlandev (ifconfig already tries for
> > normal invocations, just needed to try with the wlandev interface)
> > [
Oliver Fromme wrote:
> ifconfig_bge0="up"
> cloned_interfaces="vlan103 vlan105"
> ifconfig_vlan103="inet 10.103.0.20/16 vlan 103 vlandev bge0"
> ifconfig_vlan105="inet 10.105.0.20/16 vlan 105 vlandev bge0"
Sorry, I forgot to paste one line:
network_interfaces="bge0 lo0"
That one is essentia
On Wed, Mar 18, 2009 at 11:50 AM, Oliver Fromme wrote:
> Oliver Fromme wrote:
> > ifconfig_bge0="up"
> > cloned_interfaces="vlan103 vlan105"
> > ifconfig_vlan103="inet 10.103.0.20/16 vlan 103 vlandev bge0"
> > ifconfig_vlan105="inet 10.105.0.20/16 vlan 105 vlandev bge0"
>
> Sorry, I forgot to
Ash Gokhale wrote:
I'm developing a kernel module that will be doing inspection and needed
access to raw network frames,
so I turned to netgraph as the solution.However it seems that netgraph
will not permit a module
to unload once it's participated in a mkpeer/connect operation.
Rebooting
David Horn wrote:
> Oliver Fromme wrote:
> >
> > network_interfaces="bge0 lo0"
>
> Ah. Ok, now I am understanding your scenario.
>
> I thought that using 'network_interfaces' with anything other than
> "AUTO" was in the process of being depreciated ?
Well, the manual page says so, bu
Oliver Fromme wrote:
David Horn wrote:
> Oliver Fromme wrote:
> >
> > network_interfaces="bge0 lo0"
>
> Ah. Ok, now I am understanding your scenario.
>
> I thought that using 'network_interfaces' with anything other than
> "AUTO" was in the process of being depreciated ?
Well, the
Pyun YongHyeon wrote:
Do you have ae(4) hardware? I'm not sure why stas@ removed WOL part
in the MFC but it could be lack of testing(CCed to stas@). I've
attached diff that includes WOL support from HEAD.
Thanks. I tested this OK on the EeePC 701 so I've committed it!
cheers
BMS
__
On Wed, Mar 18, 2009 at 12:26 PM, Oliver Fromme wrote:
> David Horn wrote:
> > Oliver Fromme wrote:
> > >
> > > network_interfaces="bge0 lo0"
> >
> > Ah. Ok, now I am understanding your scenario.
> >
> > I thought that using 'network_interfaces' with anything other than
> > "AUTO" was i
The following reply was made to PR kern/131153; it has been noted by GNATS.
From: Rui Paulo
To: bug-follo...@freebsd.org,
ad...@voicenet.com
Cc:
Subject: Re: kern/131153: [iwi] iwi doesn't see a wireless network
Date: Wed, 18 Mar 2009 22:58:10 +
This is an OpenPGP/MIME signed message (RF
On Wed, Mar 18, 2009 at 05:15:05PM +, Bruce Simpson wrote:
> Pyun YongHyeon wrote:
> >Do you have ae(4) hardware? I'm not sure why stas@ removed WOL part
> >in the MFC but it could be lack of testing(CCed to stas@). I've
> >attached diff that includes WOL support from HEAD.
> >
> >
>
> Thank
Synopsis: [ppp] [panic] crash & reboot on work with PPP low-speed connection
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 19 04:35:24 UTC 2009
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/qu
12 matches
Mail list logo
