Hi All,
I've managed to get UDP broadcasts working w/o making any changes to
the FreeBSD stack of ecos.
Just wanted to detail out here the steps I've taken and get a feedback
from you guys on whether it's
proper or not...
I'm writing a DHCP server with limited-capability (which serves only 1
Mandeep Sandhu wrote:
I am able to send the broadcasts as I intended.
Are you using UDP or RAW sockets?
UDP
I've also setup my default route to point to eth0.
But when the UDP packet goes out, I see that it's corrupted.
I did not inspect it carefully, but the receiver was able
to
People!
Any comments about the below mail?
Thanks for your time.
Regards,
-mandeep
On Wed, Aug 12, 2009 at 6:49 PM, Mandeep
Sandhumandeepsandhu@gmail.com wrote:
Hi All,
I've managed to get UDP broadcasts working w/o making any changes to
the FreeBSD stack of ecos.
Just wanted to
Jay Foster wrote:
You can try the following patch that someone added
to my local source. It adds a CDL option
(CYGOPT_NET_INET_FORCE_DIRECTED_BROADCAST
I also stumbled upon the problem mentioned in the
older post and I'd like to confirm that the
patch from
I am able to send the broadcasts as I intended.
Are you using UDP or RAW sockets?
I've also setup my default route to point to eth0.
But when the UDP packet goes out, I see that it's corrupted.
Still debugging as to where the screwup is happening?
Thanks,
-mandeep
I'd vote for the
to send UDP broadcast to 255.255.255.255?
On 2009-06-16, Andrew Lunn and...@lunn.ch wrote:
On Mon, Jun 15, 2009 at 05:41:54PM +, Grant Edwards wrote:
I've been asked by one of my internal customers how to send a
UDP broadcast packet to IP address 255.255.255.255.
Hi Grant
If you have
Grant Edwards wrote:
On 2009-06-16, Jay Foster j...@systech.com wrote:
You can try the following patch that someone added to my local source. It
adds a CDL option (CYGOPT_NET_INET_FORCE_DIRECTED_BROADCAST) to modify this
behavior (the default being the same behavior you have now). Sorry it
