site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Dec 27, 2005, at 5:25 PM, Andrew Gallatin wrote: I've worked around this in the past by deleting the default route, and then setting the default route to point to the machine running the panic server.. This obviously will not work in all cases, but it may be enough to help you. Hi Drew, that will be OK for some scenarios but not for the general ones we have. Thanks.....Peter _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Peter Lovell writes: Hi Derek, what I'm seeing is that the client is not sending any arp request at all. It just starts out by sending UDP packets from 1069 to port 1069 on server, using the default router. And looking at kdp_udp.c, I don't see any ARP resolution code. It just takes whatever is the default gateway (set at kdp_set_gateway_mac, called from rt_setgate in route.c) and sends the request there. SInce we're on a managed network, I'm not at all optimistic about having any configuration changes made on the router. Drew The simple approach, which also works for only some of our usage, is to put the clients behind a mini-router. That will then forward the packets properly, which the "big network" router refuses to do. In the slightly longer term we'll just fix the kernel. We're already custom-building so this will not be the massive pain it would be for most people. This email sent to site_archiver@lists.apple.com