Eddie using port 89 even after specifying TCP port 443 in preferences

[arjubaburaj 0]

Hey, I'm trying out Eddie to try and get out from a internal network. The complication is that only port 443 is allowed in the firewall. Even after configuring Eddie to use TCP 443, in the logs I noticed that Eddie is trying to access port 89 of the remote server which obviously will be blocked. Any workarounds.?

 

*I tried it out on a test environment. Apparently, this issue is only for the connection establishment phase. Once established, Eddie can happily take the traffic out through whatever ports is specified in the preferences.

 

 

[go558a83nk 352]

AirVPN servers don't use port 89.  Post a log here so we can see what's up.

[arjubaburaj 0]

here:

 

. 2017.12.19 15:23:13 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4

. 2017.12.19 15:23:13 - OpenVPN > Route addition via IPAPI succeeded [adaptive]

. 2017.12.19 15:23:13 - Interface Local Area Connection 2 metric changed from Automatic to 3, layer IPv4

. 2017.12.19 15:23:13 - Interface Local Area Connection 2 metric changed from Automatic to 3, layer IPv6

. 2017.12.19 15:23:13 - DNS leak protection with packet filtering enabled.

. 2017.12.19 15:23:14 - Flushing DNS

I 2017.12.19 15:23:17 - Checking route

. 2017.12.19 15:23:17 - curl: (7) Failed to connect to hydra_exit.airservers.org port 89: Bad access

. 2017.12.19 15:23:17 - Checking route (2° try)

. 2017.12.19 15:23:18 - curl: (7) Failed to connect to hydra_exit.airservers.org port 89: Bad access

. 2017.12.19 15:23:18 - Checking route (3° try)

. 2017.12.19 15:23:21 - curl: (7) Failed to connect to hydra_exit.airservers.org port 89: Bad access

E 2017.12.19 15:23:21 - Checking route failed.

. 2017.12.19 15:23:21 - OpenVPN > Initialization Sequence Completed

! 2017.12.19 15:23:21 - Disconnecting

. 2017.12.19 15:23:21 - Sending management termination signal

. 2017.12.19 15:23:21 - Management - Send 'signal SIGTERM'

. 2017.12.19 15:23:21 - Connection terminated.

[go558a83nk 352]

oh, you're connected just fine.  it's checking route that's failing.

 

In advanced settings disable the option to "check if the tunnel works" but I suggest you do use network lock, if you're not already.