James G. Sack (jim) wrote:
DJA wrote:
As for capturing with tcpdump, how would I do that at the router?
Oh, sorry , I was thinking of the router as if it were a (say) linux box
you can do _anything_ on.
Well, since it involves broadcast, it may be adequate just to capture
traffic on your own workstation? If not maybe you could interpose a hub
and connect a linux box to the hub.
..jim
The router already has a switch in it. I've never used Tcpdump before,
so I'll have to research. Any tips?
As for the
echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
line, where is the best place to put this so it gets run at start up?
Of course, I'd much rather stop the router from sending the error, or
figure out why it can't see the port at the destination. Blocking both
incoming and outgoing ICMP at the firewall (part of the router) has no
affect. The bigger annoyance is that these error messages are spewed to
the console every second or so, making any console unusable.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
