Forum - AYIYA Incorrect Hash received :: SixXS - IPv6 Deployment & Tunnel Broker

AYIYA Incorrect Hash received

Shadow Hawkins on Saturday, 15 December 2012 11:42:16

Hi, starting from this morning my syslog is showing some messages like: [AYIYA-tun->tundev] [213.254.12.34]:5072 : Incorrect Hash received I'm successfully connected to the "itgate" PoP and my tunnel is always up and running - i just don't know if there is something i could do about that problem, or maybe the PoP is doing some maintainance task or such and i should not be concerned. Thanks

AYIYA Incorrect Hash received

Shadow Hawkins on Saturday, 15 December 2012 12:19:58

new logs:

Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : Dropping invalid AYIYA packet Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : idlen: 4 != 4 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : idtype: 1 != 1 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : siglen: 5 != 5 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : hshmeth: 2 != 2 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : autmeth: 1 != 1 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : nexth : 43 != 41 || 59 Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : opcode : 1 != 1 || 2 || 3

AYIYA Incorrect Hash received

Jeroen Massar SixXS Staff

on Saturday, 15 December 2012 20:31:23

Dec 15 13:16:00 nadir aiccu[6980]: [AYIYA-tun->tundev] [213.254.12.34]:5072 : nexth : 43 != 41 || 59

Interesting, you are receiving Routing Header (43) packets over your interface. I am a bit surprised that they show up on your end though as one should only get 41 (IPv6) or 59 (IPv4) packets.

AYIYA Incorrect Hash received

Shadow Hawkins on Saturday, 15 December 2012 14:36:50

Latest log with incorrect hash is at: Dec 15 14:03:07 and now it's 15 dic 2012, 15.35.15, CET Guess it's ok now - still, if you have some info about what happened it would be nice to know.

AYIYA Incorrect Hash received

Jeroen Massar SixXS Staff

on Saturday, 15 December 2012 20:33:39

Incorrectly hashed packets should never happen, it indicates that the sending entity is using a wrong password to sign the AYIYA packet. This could only happen when: - either end has a differing password - somebody is trying to fake packets and have the wrong password - packet corruption is happening The latter is the most likeliest cause.

AYIYA Incorrect Hash received

Shadow Hawkins on Sunday, 16 December 2012 11:11:47

Hi, it's happening again, same modality.

--- ipv6.google.com ping statistics --- 33 packets transmitted, 33 received, 0% packet loss, time 32047ms rtt min/avg/max/mdev = 42.192/43.581/50.847/1.833 ms

Is there something i can do?

AYIYA Incorrect Hash received

Jeroen Massar SixXS Staff

on Monday, 17 December 2012 08:00:33

Is there something i can do?

If you think you have a problem, then look at the "Reporting Problems Checklist" on the contact page and provide as much details as possible.

Please note Posting is only allowed when you are logged in.