public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* odd issue with sending to broadcast address
@ 2002-02-18 19:13 Chris Friesen
  0 siblings, 0 replies; only message in thread
From: Chris Friesen @ 2002-02-18 19:13 UTC (permalink / raw)
  To: linux-kernel, netdev


It appears that there has been a change in the handling of sending packets to
the broadcast IP address between 2.2 and 2.4.

I have an embedded system that has only local LAN access, no default route to
the net as a whole.  We're running 2.2.17 currently, and we use bootpc to
configure the system.

We're now looking at converting to 2.4 and are running into a problem with
bootpc getting "Network is unreachable" errors.

After some digging, it appears to be due to the fact that I don't have a default
route specified, but this is on purpose.

strace shows that bootpc is trying to run sendto() with a destination of
255.255.255.255, and this works fine on 2.2 and fails on 2.4.  Is this the
desired 2.4 behaviour?

What is the appropriate configuration for my setup?  Do I just add a route to
255.255.255.255?  Can I set it up to broadcast out all devices automatically, or
do I need to do explicit failover management?  Should I be looking to fix bootpc
instead?

Thanks,

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-02-18 19:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-18 19:13 odd issue with sending to broadcast address Chris Friesen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox