How to change my WAN IP?

Question

How to change my WAN IP?

Hello,

Here is my problem.

I have a vacation home. I have an old Dell sending motion detection of four IP cameras. I access the Dell via MS Remote Desktop connection. As a precaution, I programmed McAfee to only allow LAN ip's and the one from my remote. Even though I have a domain name, I had to use the actual IP address as the program does not allow DNS input.

At my present location, I run a Mac mini Mavericks and have Server 3.2.2 installed. My ISP is Verizon and for the past 3 years I had the same IP assigned to me, unchanged. The day I came back, I had no problem accessing the remote. Then no luck the next day. It seems that my ISP changed all local IP address. Of course I can no longer access the remote.

All I need to do is to spoof my previous IP address to get in. After that, I can put my new IP address or disable McAfee altogether.

Could any kind soul tell me how to accomplish this? Thanks.

Mac mini, OS X Mavericks (10.9.5)

Posted on Feb 19, 2015 4:56 PM

Reply

Answer 1

greg sahli

Level 7

25,508 points

Feb 19, 2015 6:50 PM in response to Nicholas Neuhaus

You can't control your ISP (although you may be able to pay more for a permanent IP address).

Read here about using the DynDNS service to keep track of your wan IP address:

http://www.alliedtelesis.com/media/fount/how_to_note_alliedware/howto_config_ddn s.pdf

http://www.howtogeek.com/66438/how-to-easily-access-your-home-network-from-anywh ere-with-ddns/

Reply

Answer 2

Feb 19, 2015 7:30 PM in response to greg sahli

Well now, Greg, this was a real gratuitous reply. I guess you did not read the post. I know all about dynamic and static IP addresses. That was NOT my question. And there are definitely ways of spoofing an IP address. It is done all the time via proxy servers. Basically what I was asking from users more knowledgeable than I am, if it was possible to setup my mini or my mini server to act as a proxy to take care of my problem. The proxy servers designed to mask your IP address assigns you random IP address. That would not help me.. I am not interested in hiding my IP. I just want to access my remote on a one time basis. As I explained, I want to spoof my IP address to the one I had previously for three years. I know it can be done, I just don't have enough knowledge on how to do it.

Reply

Answer 3

greg sahli

Level 7

25,508 points

Feb 20, 2015 5:52 AM in response to Nicholas Neuhaus

OK, sorry. I don't know how to do "that." 😐

What I offered solves your issue, and has nothing to do with masking your IP, unless by masking you mean that using your domain name always points to your correct IP address.

Reply

Answer 4

Feb 20, 2015 7:58 AM in response to greg sahli

OK, No, you still don't understand. I have no problem with my domain name or the many IP address that I monitor being redirected. To gain access to my remote computer the IP address must match the one that I specify which is my previous IP address. The program, MS Remote Desktop Connecting has my present IP address that my remote does not recognize and rejects access. I need in order to gain access to have my location transmit my previous IP address to the remote.

I think the concept is simple, I just don;t know how to go about it. People who spoof IP addresses must have a proxy, otherwise the spoofed IP address does not is useless to them because it does not return to their real IP address. I don't have that problem, because I am not interested in that process. I just need a one shot access to my remote. Simple.

Reply

Answer 5

Eric Root

Level 10

685,483 points

Feb 20, 2015 8:35 AM in response to Nicholas Neuhaus

Try System Preferences/Network and set IPv4 to manually, then enter the IP address.

Reply

Answer 6

BobHarris

Level 9

57,331 points

Feb 20, 2015 11:59 AM in response to Nicholas Neuhaus

The problem with spoofing your source IP address, is that return messages are sent to the IP address you specify.

You cannot change your current Verizon IP address unless you get Verizon to do that (which for a fee I'm sure they will).

If you setup a VPN server at your vacation home, and make a VPN connection from your current location, it is possible your connections to the devices inside the vacation home will appear as local connection requests. I do not know anything about Windows VPN server packages (assuming the DELL is running Windows).

You might be able to use ssh tunnels to again look like a local connection request with the ssh tunnel sending the results to your current location. And again, I do not know what is available for Windows ssh packages.

Of course all of this assumes McAfee would allow those connections from a random IP address, or just block them as well, since they do not come from your pre-coded fixed IP address that Verizon has changed.

Reply

Answer 7

Drew Reece

Level 6

10,684 points

Feb 20, 2015 12:34 PM in response to Nicholas Neuhaus

You seem to be confusing proxies & routers.

I don't think proxies are not intend to do this 'ip spoofing' as you claim. Routers are the usual way to isolate & forward connections to other devices via IP routing. Once the internet is involved it becomes very difficult to do what you aim. Your router should be setup to assign the Dell the same local IP address to allow the inbound connection to work (the ISP shouldn't be involved in local addresses).

As others are trying to explain (but your default answer is set to 'no') spoofing the IP doesn't seem like it will ever work… you can't spoof a public IP that you do not have control over (your WAN IP). You can add local routes, but the internet is between you & the destination so the packets can't get to where they need to be.

Your fundamental problem appears to be 2 things.

1. That the ISP has changed your remote IP - that is your main issue at the moment

2. Your remote access software doesn't support domain names - frankly that makes it a terrible app, try other ones.

Once you find one with domain name support you can use dyndns as already stated. Please take time to think before telling us we are all wrong, we do have similar systems running that work without your issue because we use dyndns or other services. The issues you are having are because you seem to be ignoring the standard way to setup remote access to networks that move IP's.

Perhaps we all know less than you, if that is the case I apologise it just looks like the setup is incorrect.

Reply