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,
Both should be functionality that can be disabled in the source
network device.
Sounds like good advice. I'll work on the Linksys setup with their
web-based configuration program.
I'm still not understanding it all in depth, but your comments and the
earlier replies have given me a good base to work with.
Thank you.

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: Need Some help with Instrument Control toolbox
    ... No inherent sequence numbers, no inherent ACK or NAK, no inherent detection of lost data, no inherent protocol to follow to set up or close down a connection; if these are potential problems then you have to put them into the UDP packet yourself, re-inventing parts of TCP. ... The difficulty is that Matlab is not able to act as a TCP server -- which means that it is not able to respond when something else initiates a TCP/IP connection. ... Using the same source and destination port is not uncommon for simple interfaces, but such a configuration is not used if there need to be multiple systems talking to the same service: each distinct conversation needs to have its own source port. ...
    (comp.soft-sys.matlab)