Drivers for newer WiFi cards have proved elusive, and I've heard of several
failed attempts.
It is not a great solution, and 64-bit x86 only, but this might be
interesting: https://github.com/Netgate/musenki
It is very early in development and isn't quite complete, but work is
moving fast. I
There is some curiosity in this at Netgate (my employer), but I have
it as a free-time project, and there has not been a lot of this.
The good news is that FreeBSD is a supported DPDK target, and I have
seen compatibility patches being accepted. So that's a promising
start.
I have gotten parts
On Mon, Aug 27, 2012 at 5:30 AM, Bernard Higonnet bthigon...@gmail.comwrote:
Hello,
I have two machines running 9.0 and which use DHCP. The DHCP server is on
a third machine using dnsmasq, also under 9.0, and provides an explicit
default router address.
dnsmasq is sending the right stuff,
On Sat, Aug 20, 2011 at 9:47 PM, h bagade baga...@gmail.com wrote:
Hi all,
I am trying to use pf nat rules with pool support on FreeBsd 8.0, working
together with ipfw as the main firewall. According to the natting concepts
i
faced in manuals and docs, nat concept is to map the source
Hi,
Today I updated a 9.0-CURRENT system acting as an access point and it
stopped working. From a Windows 7 machine it complains that there is a
network key mismatch. I've checked it, changed it, and still no dice. I
took the debug output from hostapd and find two odd things: first there is
a
to -net and Rui directly?
I saw some hostapd broken-ness when I tried -head last week but i
haven't had time to dig up details for Rui. It seems you just have.
:-)
Thanks!
ADrian
On 25 November 2010 07:57, David Cornejo d...@dogwood.com wrote:
Hi,
Today I updated a 9.0-CURRENT system
That brief description was a big help in itself, thank you.
One question: should the BSSID in the legacy mode be the same as the
MAC address of the main WDS node? Or can it be a random number?
thanks,
dave c
On Wed, Mar 25, 2009 at 5:31 PM, Sam Leffler s...@freebsd.org wrote:
David Cornejo
Aloha,
I'm trying to get WDS running - I am working my way through the stuff
in /usr/src/tools/tools/net80211/scripts, but it really only gives
examples and doesn't explain the why of it - is there a more verbose
how to somewhere that would help me understand this?
thanks,
dave c
hi,
i would like to bridge a wireless client to ethernet (in 8-CURRENT) -
the last bug in the if_bridge man page says this is a no-no.
the question is whether this could be worked around - don't need the
highest performance, so maybe netgraph or even a userland daemon would
work. i don't have
control over the AP.
thanks,
dave c
On Mon, Aug 4, 2008 at 12:48 PM, Sam Leffler [EMAIL PROTECTED] wrote:
David Cornejo wrote:
hi,
i would like to bridge a wireless client to ethernet (in 8-CURRENT) -
the last bug in the if_bridge man page says this is a no-no.
the question is whether
I eventually reinstalled the OS from a recent snapshot then updated it
to the latest CURRENT and it works fine now :-(
dave c
On 7/16/07, Bjoern A. Zeeb [EMAIL PROTECTED] wrote:
On Wed, 20 Jun 2007, David Cornejo wrote:
Hi,
the remote machine sees bad checksums - netstat indicates
it was the stock tree
On 7/16/07, Bjoern A. Zeeb [EMAIL PROTECTED] wrote:
On Mon, 16 Jul 2007, David Cornejo wrote:
I eventually reinstalled the OS from a recent snapshot then updated it
to the latest CURRENT and it works fine now :-(
Hmm I am using CURRENT from today and I culd see
At 08:27 AM 6/25/2007, Bill Moran wrote:
In response to Bill Moran [EMAIL PROTECTED]:
In response to Adam McDougall [EMAIL PROTECTED]:
On Tue, Jun 12, 2007 at 10:19:49AM -0400, Bill Moran wrote:
This one has got me pretty befuddled.
We're seeing some really odd behaviour with
PROTECTED] wrote:
On Tue, 19 Jun 2007, David Cornejo wrote:
Hi,
I am using CURRENT on a Soekris 4801 (sis ethernet). With a recent kernel
all TCP packets sent via sis0 have a bad checksum. Other systems using
other
interface types (though I don't have a broad selection to test) don't seem
Hi,
I am using CURRENT on a Soekris 4801 (sis ethernet). With a recent
kernel all TCP packets sent via sis0 have a bad checksum. Other
systems using other interface types (though I don't have a broad
selection to test) don't seem to suffer from this problem.
There was a thread in
This may not be related, but I have a Soekris 4801 running CURRENT
that with a GENERIC kernel exhibits the behavior where TCP connects
don't happen. If I switch to an old kernel config file, it works..
This failure happens between this box and a RELENG_6 (updated last
week), another CURRENT
as the author of the route code in olsr I can explain what I was trying to do:
for routing purposes what we need are point-to-point routes, the
subnets on the mesh interfaces are there only to facilitate
broadcasting the routing packets. because of the way freebsd is
wired, to support
At 04:18 PM 9/4/2006, Sam Wun wrote:
Hi,
I am running a FreeBSD 5.4 stable as a network router.
I don't know any reason why one of the ethernet ports becomes half-duplex.
Here is its detail:
em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=bRXCSUM,TXCSUM,VLAN_MTU
I have a setup where an interface seems to lose broadcast packets
somewhere and I'm hoping some kind soul couls lend a hand.
This is on 6-CURRENT from within the last few days.
One of my interfaces, sis1, is configured with an IP address of 10.0.2.1/24
I'm debugging some code, and in it's
19 matches
Mail list logo
