Bruce M. Simpson wrote:
I have just committed a change in bms_netdev which enforces strict
and better defined semantics for the IP_SENDSRCADDR option in
udp_output().
I have just committed this change in -CURRENT.
After testing it with 'ipbroadcast', it looks good apart from sockets
which
Bruce M. Simpson wrote:
Dealing with dhclient is a separate issue -- here, something like
IP_SENDIF needs to be introduced, as we are truly in an 'ip
unnumbered' situation -- ie the ifnet MAY not yet have been assigned
an IPv4 address at all, and IP_SENDSRCADDR implies that you are source
ro
Andre Oppermann wrote:
I have some WIP here too. I'll send it to you later this afternoon.
Thanks, I look forward to seeing it, re Issue #2 IP_SENDSRCADDR.
Dealing with dhclient is a separate issue -- here, something like
IP_SENDIF needs to be introduced, as we are truly in an 'ip unnumbere
Bruce M. Simpson wrote:
Thunderbird ate my homework. Reposting.
The FreeBSD mailing list server seems to drop my attachments, so I've
uploaded it here:
http://people.freebsd.org/~bms/dump/broadtest.c
Regards,
BMS
___
freebsd-net@freebsd.org mailin
Thunderbird ate my homework. Reposting.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hello,
In preparation for tightening up our handling of INADDR_BROADCAST sends,
I ran some brief tests today on the network stack with the attached test
code.
I found some inconsistencies when run against 6.2-RELEASE;
1. IP_ONESBCAST breaks if SO_DONTROUTE is specified.
One thing appears to
