Are the server and client on the same network segment?
Have you tried looking for the packets with tcpdump? For bootpd to
see them they would have to have made their way to the application
layer already. Many other things could have gone wrong by then.
On Tue, Nov 03, 1998 at 04:38:53PM +0100, Ole Myren R|hne wrote:
> I am trying to use a 2.1.126 linux machine as a bootserver for a
> machine that emits bootp request packets with the source address and
> the dest address set to all-ones (255.255.255.255); this seems to be a
> Using bootpd -d shows that the packets never get to the bootpd server
> and no answere is possible. When testing the bootpd server with bootpc
> on another linux box, the source address is sensible and things work
> as expected.
> I suspect that the packets with the funny source address get dropped
> as martians somewhere in the kernel code. From the traffic on this
> list I realize that earlier 2.1 kernels had a
> /proc/sys/net/ipv4/ip_bootp_agent - but this no longer exists... Any
> hint is apprechiated!
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to firstname.lastname@example.org
> Please read the FAQ at http://www.tux.org/lkml/
-- Eric Brunson * _ o * Faster and faster, email@example.com * / //\ until the thrill of speed firstname.lastname@example.org \>>| * overcomes the fear of death email@example.com \\,
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org Please read the FAQ at http://www.tux.org/lkml/