Error Reject The Packet Received Unexpecting Payload Type 0
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse IPsec Tools Mailing Lists IPsec Tools Brought to you by: mit_warlord Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Bugs Support Requests Patches Feature Requests Code ipsec-tools-announce ipsec-tools-commits ipsec-tools-devel ipsec-tools-users ipsec-tools-users — User List for Discussion / Help You can subscribe to this list here. 2005 Jan Feb Mar Apr May (16) Jun (25) Jul (22) Aug (15) Sep (21) Oct (24) Nov (24) Dec (41) 2006 Jan (23) Feb (39) Mar (22) Apr (11) May (23) Jun (17) Jul (12) Aug (11) Sep (27) Oct (30) Nov (17) Dec (16) 2007 Jan (10) Feb (38) Mar (15) Apr (32) May (29) Jun (15) Jul (21) Aug (32) Sep (17) Oct (21) Nov (12) Dec (10) 2008 Jan (7) Feb (22) Mar (40) Apr (26) May (18) Jun (25) Jul (35) Aug (21) Sep (25) Oct (66) Nov (40) Dec (77) 2009 Jan (52) Feb (29) Mar (71) Apr (77) May (146) Jun (94) Jul (65) Aug (37) Sep (29) Oct (38) Nov (21) Dec (21) 2010 Jan (9) Feb (14) Mar (30) Apr (55) May (68) Jun (67) Jul (54) Aug (50) Sep (28) Oct (5) Nov Dec (5) 2011 Jan (5) Feb (4) Mar (8) Apr (3) May (10) Jun (5) Jul (6) Aug (17) Sep (12) Oct (9) Nov (4) Dec (12) 2012 Jan (22) Feb (20) Mar (16) Apr (17) May (1) Jun (7) Jul (10) Aug (10) Sep Oct (5) Nov (5) Dec (4) 2013 Jan (3) Feb (1) Mar (21) Apr (5) May (5) Jun (19) Jul (25) Aug (14) Sep (12) Oct (26) Nov (24) Dec (3) 2014 Jan (3) Feb (
by: [ date ] [ thread ] [ subject ] [ author ] Hi all, I'm trying to connect to a Sonicwall TZ170 (I believe), from my FBSD 6.2-Prerelease. I have a username, password and PSK (ie, Xauth PSK) from the SonicW's admin (who refuses to provide any help for non MS OS :-) ). I've installed ipsec-tools-0.6.6 because I believe (wrongly?) that ipsec in the base system doesn't support xauth ... is this correct? Anyway, I configured racoon.cfg and psk.txt to the best of my current abilities. I then get: # racoonctl vpn-connect SONICW_IP_ADDRESS Error: Peer not responding It https://sourceforge.net/p/ipsec-tools/mailman/ipsec-tools-users/?viewmonth=200607 seems my side is receiving a packet with DOI type 0 (as per wireshark, whatever that means...)... and racoon complains with; Jan 2 03:28:18 ayiin racoon: ERROR: reject the packet, received unexpecting payload type 0. (complete log after my signature at end of this mail) I'd love any help that will help me understand what am I doing wrong. I can't see *WHY* I wouldn't be able to connect https://lists.freebsd.org/pipermail/freebsd-questions/2007-January/138689.html to this Sonic, other than a problem between the chair and the keyboard :) Alternative ways of doing this same thing with other packages / base tools are greatly appreciated. thanks in advance!!! B Configuration gory details: 192.168.13.3 is my laptop's IP. hostname is ayiin. I have UDP/500 port forwarded to this machine, and my local firewall is open for this traffic (udp/500 from SOCNIW_IP_ADDRESS) my racoon.conf is: --- path include "@sysconfdir_x@/racoon"; path pre_shared_key "@sysconfdir_x@/racoon/psk.txt"; log debug; # Specify various default timers. timer { # These value can be changed per remote node. counter 5; # maximum trying count to send. interval 20 sec; # maximum interval to resend. persend 1; # the number of packets per send. # maximum time to wait for completing each phase. phase1 30 sec; phase2 15 sec; } remote SONICW_IP_ADDRESS { lifetime time 1 hour; exchange_mode main, aggressive; #ca_type x509 "ca.crt"; proposal_check obey; mode_cfg on; # accept config through ISAKMP mode config dpd_delay 20; # nat_traversal force; ike_frag on; # esp_frag 552; #script "/etc/racoon/phase1-up.sh" phase1_up; #script "/etc/racoon/phase1-down.sh" phase1_down; passive off; xauth_login "beto"; proposal { encryption_algorithm aes; hash_algorithm sha1; authentication_method hybrid_rsa_client; dh_group 2; } } sainfo anonymous { lifetime time 1 hour; encryption_algorithm aes; authentication_algorithm hmac_sha1; compression_algorithm deflate ;
means and how I might resolve this?It's being generated by Shorewall, when i connect using:racoon -d -d -d -v -F -f /etc/racoon/racoon.conf(Debug, Verbose, Foreground, cfgFile)I http://shorewall-users.narkive.com/bgjtH6N9/shorewall-error-reject-the-packet-received-unexpecting-payload-type-0 am using AuthMethod Hybrid RSA client, with a self-siged certificate.my racoon.conf has: exchange_mode aggressive;ca_type x509 "/etc/pki/tls/cert.pem";verify_cert off;proposal_check obey;mode_cfg on;dpd_delay 20; # DPD poll every 20 secondsnat_traversal force; https://bugzilla.redhat.com/show_bug.cgi?id=217306 # always use NAT-Tgenerate_policy on;ike_frag on; # use IKE fragmentationesp_frag 552;passive off;xauth_login "xyz";proposal {encryption_algorithm 3des;hash_algorithm sha1;authentication_method hybrid_rsa_client;dh_group 2;}}This is what racoon spits out:2008-07-25 16:54:01: DEBUG: authmethod is error reject Hybrid RSA client2008-07-25 16:54:01: DEBUG: add payload of len 48, next type 42008-07-25 16:54:01: DEBUG: add payload of len 128, next type 102008-07-25 16:54:01: DEBUG: add payload of len 16, next type 52008-07-25 16:54:01: DEBUG: add payload of len 8, next type 132008-07-25 16:54:01: DEBUG: add payload of len 20, next type 132008-07-25 16:54:01: DEBUG: error reject the add payload of len 16, next type 132008-07-25 16:54:01: DEBUG: add payload of len 16, next type 132008-07-25 16:54:01: DEBUG: add payload of len 16, next type 132008-07-25 16:54:01: DEBUG: add payload of len 16, next type 132008-07-25 16:54:01: DEBUG: add payload of len 8, next type 132008-07-25 16:54:01: DEBUG: add payload of len 16, next type 132008-07-25 16:54:01: DEBUG: add payload of len 16, next type 0[Note the next type 0]2008-07-25 16:54:01: DEBUG: 400 bytes from 192.168.20.221[500] to 61.8.154.116[500]2008-07-25 16:54:01: DEBUG: sockname 192.168.20.221[500]2008-07-25 16:54:01: DEBUG: send packet from 192.168.20.221[500]
Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug217306 - ifup-ipsec fails to establish a tunnel to PIX Summary: ifup-ipsec fails to establish a tunnel to PIX Status: CLOSED WONTFIX Aliases: None Product: Fedora Classification: Fedora Component: initscripts (Show other bugs) Sub Component: --- Version: 6 Hardware: All Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Bill Nottingham QA Contact: Brock Organ Docs Contact: URL: Whiteboard: bzcl34nup Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2006-11-26 16:14 EST by Bojan Smojver Modified: 2014-03-16 23:04 EDT (History) CC List: 2 users (show) rvokal triage See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2008-05-06 12:57:41 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Script to manually bring the tunnel up (737 bytes, text/plain) 2006-11-26 16:14 EST, Bojan Smojver no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Bojan Smojver 2006-11-26 16:14:12 EST Description of problem: If IPSec interface is configured like this: ------------------------------------ DEVICE=ipsec0 ONBOOT=no SRC=