On Fri, 2011-02-18 at 16:34 -0500, grarpamp wrote:
> I bcc'd the fwcutter author for inclusion of the patch in the next
> release.
Thanks a lot. I'll commit it to git.
--
Greetings Michael.
___
freebsd-net@freebsd.org mailing list
http://lists.freebs
>> Doesn't FreeBSD have some sort of ndiswrapper function for this?
>> http://www.broadcom.com/support/802.11/linux_sta.php
> NDISulator, ndis(4).
Hmm, maybe that only applies to the Windows driver bundles as
distributed by the vendors (Dell, HP, Lenovo, etc). Or from Microsoft
itself as part of t
On Feb 18, 2011, at 1:12 PM, Oliver Lehmann wrote:
> that unfortunally requires QT for whatever reason (yeah KDE - but
> QT for a proxy??) I do not have this on my router of course :(
Most of this stuff uses subnet-local broadcasts to perform device discovery.
It would probably be a lot easier t
On Fri, Feb 18, 2011 at 9:54 PM, grarpamp wrote:
> Doesn't FreeBSD have some sort of ndiswrapper function for this?
NDISulator, ndis(4).
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
I diffed the source of b43-fwcutter, v12 to v13.
And also between v12 + fbsd port patches and v13 native.
It all looks clean, both compile, and v13 produces digest identical
output files to v12 + fbsd port when used as in the bwi and bwn
kmod ports.
The current fwcutter port can thus be bumped to
John-Mark Gurney wrote:
First, UPnP is advertised over SSDP... Those port 1900 packets are the
TV trying to find a media server, but no one responds to them. I have
not tried to get UPnP working across subnets (yet, but I plan to in the
future), but you could look at:
http://frinring.wordpres
>> I have a BCM94312MCG, which driver should I choose and why?
>> The man pages are nearly identical.
>
> The FreeBSD bwn and bwi modules seem to be equivalent to the Linux
> b43 and b43legacy drivers. This page may or may not help:
> http://wireless.kernel.org/en/users/Drivers/b43
I'll see if I
Oliver Lehmann wrote this message on Fri, Feb 18, 2011 at 16:42 +0100:
> I've got a shiny new Sony TV with DLNA Support :)
> My fileserver is located in a different subnet so it is not accessibly
> by the TV.
> The TV itself detects my netbook which is in the same subnet (and runs
> Win7) as a DLNA
Hello,
I have a fairly straightforward network in a collocated facility. I have a
FreeBSD PF Bridging firewall (2 interfaces bridged, 1 interface for access).
The FreeBSD 8.0-RELEASE firewall provides inbound filtering through a Dell
PowerConnect 5448 switch, divided into two vlans.
My network i
On Thu, 17 Feb 2011, grarpamp wrote:
I have a BCM94312MCG, which driver should I choose and why?
The man pages are nearly identical.
The FreeBSD bwn and bwi modules seem to be equivalent to the Linux
b43 and b43legacy drivers. This page may or may not help:
http://wireless.kernel.org/en/us
Hi,
I've got a shiny new Sony TV with DLNA Support :)
My fileserver is located in a different subnet so it is not accessibly
by the TV.
The TV itself detects my netbook which is in the same subnet (and runs
Win7) as a DLNA source.
I've now tried to setup igmpproxy because I thought this might sol
Back in FreeBSD 6.3 and 6.4 there was a bpf-bug in if_bridge.c.
This bug was sometimes a nice feature though, since it "normalised" the
traffic sent to bpf, making it easier to sniff, analyse and debug the
mirrored traffic.
My request is for the possibility to have "packet normalisation" tur
12 matches
Mail list logo
