Re: Having problems with limited broadcast

Bruce M. Simpson wrote: Peter Steele wrote: ... I personally like this idea, but I'm not sure I can sell it to the others. Are there any restrictions to these 169.254.x.y addresses? 169.254.0.0/16 must never appear outside a link -- it is strictly scoped to that link. Currently the IPv4

Re: Having problems with limited broadcast

Bruce M. Simpson wrote: Peter Steele wrote: ... I personally like this idea, but I'm not sure I can sell it to the others. Are there any restrictions to these 169.254.x.y addresses? 169.254.0.0/16 must never appear outside a link -- it is strictly scoped to that link. P.S. I checked in a

Re: Having problems with limited broadcast

Peter Steele wrote: ... I personally like this idea, but I'm not sure I can sell it to the others. Are there any restrictions to these 169.254.x.y addresses? 169.254.0.0/16 must never appear outside a link -- it is strictly scoped to that link. Currently the IPv4 BSD stack has no concept

RE: Having problems with limited broadcast

> BTW: If you guys are already looking at scapy, you may also wish to give > pcs.sourceforge.net a look as an alternative. I didn't come across that in my research. I'll have to check it out. Thanks. Peter ___ freebsd-net@freebsd.org mailing list http

RE: Having problems with limited broadcast

>Peter, I understand your issue with the (apparent) restriction of the >169.254/16 range, though I'd point out that the IPv4-LL addressing >scheme is considered a fall-back plan by most systems implementors. >Your systems could look for DHCP first then failing that, drop back to >IPv4-LL and

Re: Having problems with limited broadcast

Bruce Walker wrote: It was trivial to do this in a completely portable way using libpcap and libnet. Sorry, typo: I actually meant to say libdnet -- a different but similar package. Also with Python bindings. http://libdnet.sourceforge.net/ -bmw

Re: kern/130189: [ndis] [patch] if_ndis typo 802.11 mode test

Synopsis: [ndis] [patch] if_ndis typo 802.11 mode test Responsible-Changed-From-To: freebsd-net->weongyo Responsible-Changed-By: weongyo Responsible-Changed-When: Fri Jan 9 01:19:18 UTC 2009 Responsible-Changed-Why: Grab it. http://www.freebsd.org/cgi/query-pr.cgi?pr=130189 _

Re: Having problems with limited broadcast

Peter Steele wrote: The folk who point out that link-local addresses could be used, have an interesting suggestion which might work for you. It's definitely interesting, but it is very likely that some of our customers will want to be able to set their own IP ranges and not be li

Re: Having problems with limited broadcast

Bruce M. Simpson wrote: The folk who point out that link-local addresses could be used, have an interesting suggestion which might work for you. Peter, I understand your issue with the (apparent) restriction of the 169.254/16 range, though I'd point out that the IPv4-LL addressing scheme is

RE: Having problems with limited broadcast

> The folk who point out that link-local addresses could be used, have an > interesting suggestion which might work for you. It's definitely interesting, but it is very likely that some of our customers will want to be able to set their own IP ranges and not be limited to 169.254/16. So we need a

Re: Having problems with limited broadcast

Peter Steele wrote: ... It's really a matter of time. We didn't anticipate limited broadcast being broken in FreeBSD and we're scrambling to come up with a solution. To be quite frank I haven't done anything with IPv6 before so it would be more research to get up to speed on this option. It seems

RE: Having problems with limited broadcast

>If this is all going over an L2 LAN, why not do the initial discovery >and general configuration exchange over IPv6? :P Link layer >network-scope addresses to the rescue. > >(think: just like apple wireless base stations and MacOSX hosts doing >configuration do..) It's really a matter of time. We

Re: Julian's source IP address spoofing - code review requested

2009/1/8 Julian Elischer : > I see you always call ether_demux when a packet is moved up.. s/you/you/ :) This is all your stuff IIRC, I just ported and commented as required. > hopefully that will also work if an interface is NOT ethernet? this is why i left the ethernet bridge interception st

Re: Having problems with limited broadcast

If this is all going over an L2 LAN, why not do the initial discovery and general configuration exchange over IPv6? :P Link layer network-scope addresses to the rescue. (think: just like apple wireless base stations and MacOSX hosts doing configuration do..) Adrian 2009/1/8 Peter Steele : >> T

Re: kern/130311: [wlan_xauth] [panic] hostapd restart causing kernel panic

Old Synopsis: [wlan_xauth] hostapd restart causing kernel panic New Synopsis: [wlan_xauth] [panic] hostapd restart causing kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 8 21:40:59 UTC 2009 Responsible-Changed-W

RE: Having problems with limited broadcast

> Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll > check it out. ZeroConf is an interesting concept. Unfortunately it restricts IPs to the 169.254/16 range and it is very likely some of our customers will want to be able to configure our boxes to an IP range of their own ch

Re: Julian's source IP address spoofing - code review requested

Adrian Chadd wrote: G'day all, I've finally gotten around to pulling apart some of Julian Elischer's work on the source IP address spoofing stuff and I've been testing it on my local squid-2 fork (cacheboy.) I'd appreciate some comments and review before I begin committing bits of it to freebsd

Julian's source IP address spoofing - code review requested

G'day all, I've finally gotten around to pulling apart some of Julian Elischer's work on the source IP address spoofing stuff and I've been testing it on my local squid-2 fork (cacheboy.) I'd appreciate some comments and review before I begin committing bits of it to freebsd-current. The work wi

RE: Having problems with limited broadcast

>Peter, leaving aside the issue of FreeBSD limited broadcast, have you >considered ZeroConf, and in particular the IPv4 Link-Level Addressing >portion of it to meet your basic "get the boxes addressed" requirement? > >http://www.zeroconf.org/ >http://files.zeroconf.org/rfc3927.txt > >I don't have

Re: VLAN interface management - unloading carrying driver hangs the machine

Fine with me, go do it and I'll take the driver code out :) Jack On Thu, Jan 8, 2009 at 12:18 AM, Yony Yossef wrote: > > Jack Vogel wrote: > > > > > > > > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > > > wrote: > > > > > > Yony Yossef wrote: > > > > > >

Re: kern/130189: [ndis] [patch] if_ndis typo 802.11 mode test

Old Synopsis: [patch] if_ndis typo 802.11 mode test New Synopsis: [ndis] [patch] if_ndis typo 802.11 mode test Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 8 08:30:39 UTC 2009 Responsible-Changed-Why: Over to maintainer(s

RE: VLAN interface management - unloading carrying driver hangs the machine

> Jack Vogel wrote: > > > > > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > > wrote: > > > > Yony Yossef wrote: > > > > Yony Yossef wrote: > > > > > > /sbin/ifconfig vlan3653 create > > > > Problem is when I