Problem occures when then server receives a message on the alternate ip.
The port on which it sends the message is ok; but the field in the
SOURCE-ADDRESS is wrong.
I have tested this on some public servers with twinkle as a client.
I have attached a wireshark output; see frame 18 (line 296 and line 280):
Src Port: stun (3478) as reported by wireshark and is correct behavior
Port: 3479 as reported by SOURCE_ADDRESS and is wrong
Nobody/Anonymous
Network
None
Public
| Filename | Description | Download |
|---|---|---|
| stun_bug1 | wireshark output | Download |
| Field | Old Value | Date | By |
|---|---|---|---|
| File Added | 340899: stun_bug1 | 2009-08-28 10:03 | rpistolea |