IPLeak showing a non-AirVPN public IP despite connection

[Innovathorr 0]

Hi, I've got similar issue,
IPLeak says I'm on AirVPN Server (Exit, Ross, Montreal) but my public IP shows as 184.75.215.242 (Toronto, ON) -not AirVPN Exit Node, but some suspected network sharing device! 
I'm connecting from a corporate PC. Is it normal? How can I fix it?
Thank you!

Edited ... by Innovathrorr

[OpenSourcerer 1435]

@Innovathrorr Your post was moved into this thread. No matter how similar, issues don't need to have the same cause. This one definitely doesn't share it
 

28 minutes ago, Innovathrorr said:

184.75.215.242

That IP belongs to McAfee. McAfee belongs to Intel. It's kind of a long shot, but since it's a corporate PC, the theft protection (or some other feature of the Trusted Platform Module) might be active which might or might not prevent changing the routing table to prevent thiefs from blocking the connection to Intel or the company via VPN. Something like that. But it's quite likely the TPM prevents something.
Might be just a software, though. I don't know all the software you're running

[Innovathorr 0]

16 hours ago, OpenSourcerer said:

@OpenSourcerer
Thank you for your comment. Yes, the PC runs McAfee 😎. The IP lookup though says that exit is some amanah tech Inc. I guess it's not entirely private/free browsing then even under AirVPN.
I wonder if there's a way to circumvent it and make sure the exit is at AirVPN node without triggering alarms?
P/S What IP lookup are you using? it seems it's pretty accurate... Thank you!

[OpenSourcerer 1435]

And you are right, the ISP is Amanah Tech because that's whom the data centers belong to. It's a hosting and colocation provider, which means other organizations can rent servers there. These are marked by the org field in some IP API responses:

{
 "isp"          : "Amanah Tech Inc.",
 "org"          : "McAfee, Inc. - Plano",
 "as"           : "AS32489 Amanah Tech Inc.",
 "query"        : "184.75.215.242"
}
 

7 hours ago, Innovathrorr said:

I wonder if there's a way to circumvent it and make sure the exit is at AirVPN node without triggering alarms?

I wouldn't try honestly. Best thing you can do is not to use it privately.
 

7 hours ago, Innovathrorr said:

P/S What IP lookup are you using? it seems it's pretty accurate... Thank you!

I made a small Bash function for such lookups.

ip-api () 
{ 
    curl -s http://ip-api.com/$1
}

IP-API.com

[De Facto Pantalones 12]

I don't know if this would help, but if you're using Windows, try running Eddie with elevated privileges, "connect at startup", "activate network lock at start-up", and "start with system"?  Perhaps there is a McAfee setting to "Delay Real-Time Protection" you can change?  ¯\_(ツ)_/¯