Re: blocking incoming udp packets

On Wed, 09 Jul 2008 13:06:15 -0500, comphelp@xxxxxxxxx (Todd H.)
wrote:

JClark <jclark@xxxxxxxxxxxxxx> writes:

Returning to the original question, a summary, as I see it (not
necessarily correctly):

It seems the router is sending udp packets to 255.255.255.255 (both
source and destination ports = 520, or to 192.168.1.255 (source port
ranging from 7000 to 7259, and destination port 162.

I have no idea what this all means.

UDP 162 is the SNMP trap port. If you're not familiar with simple
network management protocol, this traffic to 162 may simply be the
network device attempting to send traps to be logged by an SNMP
management station.

UDP 520 is RIP routing. The router is advertising routes with this
exceedingly simple, easy to spoof protocol.

Both should be functionality that can be disabled in the source
network device.

Best Regards,
Todd,
Some good news. I was able to disable RIP routing in the router, and
now all the traffic over UDP 520 has stopped.
Now I need to work on the SNMP 162. It isn't quite as clear.
But it seems I'm on the right track.
Many thanks again.

Jack
.

Relevant Pages

  • Re: blocking incoming udp packets
    ... It seems the router is sending udp packets to 255.255.255.255 (both ... and destination port 162. ... UDP 162 is the SNMP trap port. ... network device attempting to send traps to be logged by an SNMP ...
    (comp.security.firewalls)
  • Re: blocking incoming udp packets
    ... It seems the router is sending udp packets to 255.255.255.255 (both ... and destination port 162. ... UDP 162 is the SNMP trap port. ... network device attempting to send traps to be logged by an SNMP ...
    (comp.security.firewalls)
  • Re: blocking incoming udp packets
    ... It seems the router is sending udp packets to 255.255.255.255 (both ... and destination port 162. ... UDP 162 is the SNMP trap port. ...
    (comp.security.firewalls)
  • Re: VPN/RWW not able to establish connection
    ... I have been able to connect for the past several days, so I guess your "correct solution is one that works" is true. ... I did check Google and saw a reference that there was some handshaking going on that did use UDP port 50, but I can't find it now. ... If reconfiguration of your router requires a reboot then it's possible it was the reboot which fixed it and not the altered configuration. ... RWW requires TCP/IP ports 443 and 4125, PPTP VPN uses TCP/IP port 1723 and IP protocol 47. ...
    (microsoft.public.windows.server.sbs)
  • Re: CSocket : testing (easy ... RE: AliR)
    ... you must not be using UDP. ... UDP is usually blocked at firewalls, and any router ... truncated at any router to the minimum mandated by the Internet standards, ... The reason for CAsyncSocket is that if the remote program hangs, your program hangs also, ...
    (microsoft.public.vc.mfc)