Re: [OT] ICMP destination unreachable

From: David Goode (dgoode_at_us.checkpoint.com)
Date: 11/25/03

  • Next message: James Pifer: "Re: [OT] ICMP destination unreachable" 
    To: redhat-list@redhat.com
Date: Tue, 25 Nov 2003 12:29:46 -0600

    Leonard Miller wrote:

    > Can you send one of the packets? It is probably just trying to reach a
    > port
    > that is not listening.
    >
    > Leonard
    >
    >
    >>>>jamesredhatlist@obrien-pifer.com 11/25/03 01:06PM >>>
    >
    > Hoping someone can help out with what I think is a strange problem. I
    > have a Redhat 9 machine that has OpenNMS installed. I was playing with
    > OpenNMS for collecting SNMP traps. Right now I DO NOT have OpenNMS
    > running, at least the service is not started and I don't see it in the
    > list if I do ps -ef.
    >
    > If I run a packet capture with Ethereal I see SNMP traps coming in,
    > which I would expect. After each trap I see a destination unreachable
    > trap going from my machine back to the machine that sent the trap.
    >
    > 1) Any idea what could source for that could be?
    > 2) Besides that, the IPs that it says destination unreachable for are
    > all ping'able.
    >
    > Any ideas or suggestions?,
    > James
    >
    >

    Agreed, this is normal behavior assuming the port is not
    currently listening. This is the way the IP stack tells the
    other machine that the port in question is closed. Should be
    considered normal behavior. 

    -- 
-David Goode	
Check Point Software
Solutions Center
-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
  • Next message: James Pifer: "Re: [OT] ICMP destination unreachable"

    Relevant Pages

    • RE: SNMP trap listening on multiple ports in RHEL
      ... SNMP trap listening on multiple ports in RHEL ... A SNMP Network element send a trap to the standard port 162 in the RHEL ...
      (RedHat)
    • SNMP trap listening on multiple ports in RHEL
      ... A SNMP Network element send a trap to the standard port 162 in the RHEL ... machine.Only one trap handler can bind to this 162 port at a time. ... machine each independenly listening to its assigned port.All these ports ...
      (RedHat)
    • Re: Best Plan of action for 2 forest.......
      ... PortQry reports the status of a port in one of the following ways: ... ..LISTENING This response indicates that a process is listening on the target ...
      (microsoft.public.windows.server.active_directory)
    • Re: RealVNC
      ... If we are talking about RealVNC it goes this way ... Then there is default Java listening port on port 5800 on the client machine ...
      (microsoft.public.windows.server.sbs)
    • Re: RIP issue with HMC - security violation?
      ... using an UDP port, 520, which would normally imply that there was a Routing ... Information Protocol (RIP) process behind it capable of modifying the routing ... as a "listening" state for the application. ...
      (bit.listserv.ibm-main)