Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread Yuri
On 09/14/2012 11:49, hiren panchasara wrote: Not sure if you looked at - man wpa_supplicant, which has -d for debugging -s for pumping messages to syslog wpa_supplicant ran with -d -d doesn't print any error messages and runs fine. 'netif start' is the one issuing a warning and preventing dhcl

Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread hiren panchasara
On Fri, Sep 14, 2012 at 11:32 AM, Yuri wrote: > On 09/14/2012 10:54, Glen Barber wrote: > >> Ok. Thanks for letting us know. >> > > Now wpa_supplicant starts and is operational, however '/etc/rc.d/netif > start' always issues this warning: > Starting wpa_supplicant > /etc/rc.d/wpa_supplicant: WA

Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread Yuri
On 09/14/2012 10:54, Glen Barber wrote: Ok. Thanks for letting us know. Now wpa_supplicant starts and is operational, however '/etc/rc.d/netif start' always issues this warning: Starting wpa_supplicant /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting Network: lo0 nd

Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread Glen Barber
On Fri, Sep 14, 2012 at 10:47:38AM -0700, Yuri wrote: > On 09/14/2012 00:09, Yuri wrote: > > > > It was some mismatch between kernel/userland/ndis driver. After I > > fixed the mismatch, wifi still doesn't get initialized during boot and > > 'netif start' ran by hand also doesn't start it. > > N

Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread Yuri
On 09/14/2012 00:09, Yuri wrote: It was some mismatch between kernel/userland/ndis driver. After I fixed the mismatch, wifi still doesn't get initialized during boot and 'netif start' ran by hand also doesn't start it. Never mind, it was an issue of /etc out of sync with the world. Yuri ___

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-14 Thread Вадим Уразаев
Ok, I will disable vlan_hwtso using ifconfig -vlanhwtso. Thanks. > Try disabling tso at the global level in the kernel. Under some > circumstances with some drives VLAN_HWTSO -> TSO. > -Garrett > ___ freebsd-net@freebsd.org mailing list http://lists.fr

Re: ISDN4BSD (HPS version) is going into ports

2012-09-14 Thread Andreas Longwitz
Hi, Problem 2: I tried to get more information for problem 1 with the analyze mode of isdndecode using the custom cable as decribed in cable.txt. I connected my ISDN phone to an "ISDN Basisanschluß" with my cable box between them (receiving side unit 8, sending side unit 9), >>

Re: moving pfil consumers to sys/netpfil

2012-09-14 Thread Gleb Smirnoff
On Fri, Sep 14, 2012 at 10:33:40AM +0200, Luigi Rizzo wrote: L> On Fri, Sep 14, 2012 at 11:23:50AM +0400, Gleb Smirnoff wrote: L> > On Thu, Sep 13, 2012 at 10:57:21PM +0200, Luigi Rizzo wrote: L> > L> On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote: L> > L> > On Thu, Sep 13, 2012 at 0

Re: moving pfil consumers to sys/netpfil

2012-09-14 Thread Luigi Rizzo
On Fri, Sep 14, 2012 at 11:23:50AM +0400, Gleb Smirnoff wrote: > On Thu, Sep 13, 2012 at 10:57:21PM +0200, Luigi Rizzo wrote: > L> On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote: > L> > On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote: > L> > L> Second: > L> > L>What i

Re: Why wpa_supplicant doesn't start with ndis0 interface?

2012-09-14 Thread Yuri
On 09/13/2012 17:45, Warren Block wrote: On a fast machine, there could be a race there. Best to load them in order in a single command: @rebootroot/sbin/kldload if_ndis.ko && /sbin/kldload bcmwl5_sys.ko It was some mismatch between kernel/userland/ndis driver. After I fixed the