I dont really know if its a RED50 related or a gerenal mistake or if I am missing something...
I am trying to connect a RED50 to an UTM9 (9.004-33) hostet at Amazons EC2 with an elastic IP.
Config File + Connect works fine. But since elastic IPs are 1:1 natted to the private IP of the UTM, the RED server sends out private IPs at the RED config. So that ping and further connections are failing.
Isnt there a way to "use first public IP address" like at the DynDNS client.
2012:11:23-23:38:29 mx04 red_server[7698]: A34007E00000000: PING remote_tx=0 local_rx=0 diff=0
2012:11:23-23:38:29 mx04 red_server[7698]: A34007E00000000: PONG local_tx=0
2012:11:23-23:38:32 mx04 red_server[31567]: SELF: New connection from 91.67.***.*** with ID A34007E00000000 (cipher AES256-SHA), rev1
2012:11:23-23:38:32 mx04 red_server[31567]: A34007E00000000: already connected, releasing old connection
2012:11:23-23:38:32 mx04 red_server[31567]: A34007E00000000: disconnecting
2012:11:23-23:38:32 mx04 red_server[7778]: SELF: Starting REDv2 protocol
2012:11:23-23:38:32 mx04 red_server[7778]: A34007E00000000: connected OK, pushing config
2012:11:23-23:38:32 mx04 red_server[7778]: A34007E00000000: Sending PEERS+10.252.106.211+10.252.106.211
2012:11:23-23:38:35 mx04 red_server[7778]: A34007E00000000: command 'PING 0'
2012:11:23-23:38:35 mx04 red_server[7778]: A34007E00000000: PING remote_tx=0 local_rx=0 diff=0
2012:11:23-23:38:35 mx04 red_server[7778]: A34007E00000000: PONG local_tx=0
2012:11:23-23:38:52 mx04 red_server[7778]: A34007E00000000: command 'PING 0'
2012:11:23-23:38:52 mx04 red_server[7778]: A34007E00000000: PING remote_tx=0 local_rx=0 diff=0
2012:11:23-23:38:52 mx04 red_server[7778]: A34007E00000000: PONG local_tx=0
