Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. tsaunat

    Return Packets disappearing

    I will look into route based tunnels as I have never set it up that way before. Thanks for the help!
  2. tsaunat

    Return Packets disappearing

    Also one other note I changed this to accept rather than tunnel and the traffic no longer was dropped. I'd perfer to be able to tunnel all traffic and all other traffic is tunneling fine just not this.
  3. tsaunat

    Return Packets disappearing

    Anybody have any ideas? Other traffic from these two IP's even traffic on this port is allowed. What does the message "L2 packet drop: mac for self, but session is not for self" mean? has it fallen out of a stateful session? Is there something wierd going on?
  4. tsaunat

    Return Packets disappearing

    It is policy based tunneling Hardware Version: 110(0) Firmware Version: 5.0.0r8.0 (Firewall+VPN) Sorry should have mentioned earlier UDP traffic will look at session info for more help.
  5. tsaunat

    Return Packets disappearing

    That bit of advice was extreamly helpful thanks. Now I'm getting in the debug log ****** 44564.0: <V1-Trust/ethernet1> packet received [38]****** ipid = 61652(f0d4), @d7802910 packet passed sanity check. v1-trust:146.63.202.84/4644->146.63.193.143/4999,17<Root> L2 packet drop: mac for...
  6. tsaunat

    Return Packets disappearing

    I have a policy to tunnel between our two data centers for the most part this seems to be working great, but one paticular type of traffic seems to be disappearing and I can't understand why. When I send udp 4644 traffic from my secondary datacenter to a specific server on my primary...

Part and Inventory Search

Back
Top