How to move from public IP based network to private IP LAN but using WAP with public IP
Hello ExEx,
There is probably a very simple answer to this question but I can't quite figure it out!
I have a network comprising of 3 pcs and a Mac, no server, on a workgroup, all with manualy assigned public IPs.
We have a block of 8 IPs for our use on a subnet of 255.255.255.248 and a default gateway in the same public IP range for all the offices to share.
The office is in a serviced office block and we access the default gateway using their wireless access point.
We want to install a server and move onto a local private network IP addressing system for our office.
That is, we would like our pcs, Mac and server to be on the 192.168.0.0/24 range behind a hardware firewall.
However, we can only access the internet through the wireless access point with its public ip as the default gateway.
So I am thinking that I will need to install a router which will have a private ip on the internal NIC as the internal default gateway address, but on the external wireless interface connecting to their wap it will have to have the original public ip default gateway on the 255.255.255.248 subnet??
If this is the case what would be the appropriate hardware to use for this setup?
I do hope this makes sense but I am very happy to clarify this if it doesn't.
I am awarding 125 points for the most useful suggestion, however if this question is more difficult to answer than I imagine I am happy to increase the points value.
Look forward to hearing your suggestions.
Regards
Paul
There is probably a very simple answer to this question but I can't quite figure it out!
I have a network comprising of 3 pcs and a Mac, no server, on a workgroup, all with manualy assigned public IPs.
We have a block of 8 IPs for our use on a subnet of 255.255.255.248 and a default gateway in the same public IP range for all the offices to share.
The office is in a serviced office block and we access the default gateway using their wireless access point.
We want to install a server and move onto a local private network IP addressing system for our office.
That is, we would like our pcs, Mac and server to be on the 192.168.0.0/24 range behind a hardware firewall.
However, we can only access the internet through the wireless access point with its public ip as the default gateway.
So I am thinking that I will need to install a router which will have a private ip on the internal NIC as the internal default gateway address, but on the external wireless interface connecting to their wap it will have to have the original public ip default gateway on the 255.255.255.248 subnet??
If this is the case what would be the appropriate hardware to use for this setup?
I do hope this makes sense but I am very happy to clarify this if it doesn't.
I am awarding 125 points for the most useful suggestion, however if this question is more difficult to answer than I imagine I am happy to increase the points value.
Look forward to hearing your suggestions.
Regards
Paul
ASKER
Hi Zenith63
I've just checked in and seen your reply, thanks for posting so quickly.
That's exactly what i had in mind too. I also get to the point where I am trying to find the sort of hardware that can do what I want it to, and then I draw a blank. It is not possible to wire into their WAP, all the offices have to connect wirelessly to the gateway for internet access and, yes, it is slow and a pain, but we cannot do anything about it.
Would it be possible to use a WAP as a bridge from their external WAP to a router on our internal network. The bridge would be have one of our original public IPs on the 255.255.255.248 subnet and the external WAP IP as the gateway. The router would wire into the internal WAP and have one public IP on the same subnet and the external WAP IP as the gateway on the WAN side, and say 192.168.0.254 on subnet 255.255.255.0 on the LAN side. The PCs, etc would have the gateway set as 192.168.0.254?
Any ideas?
Regards
Paul
I've just checked in and seen your reply, thanks for posting so quickly.
That's exactly what i had in mind too. I also get to the point where I am trying to find the sort of hardware that can do what I want it to, and then I draw a blank. It is not possible to wire into their WAP, all the offices have to connect wirelessly to the gateway for internet access and, yes, it is slow and a pain, but we cannot do anything about it.
Would it be possible to use a WAP as a bridge from their external WAP to a router on our internal network. The bridge would be have one of our original public IPs on the 255.255.255.248 subnet and the external WAP IP as the gateway. The router would wire into the internal WAP and have one public IP on the same subnet and the external WAP IP as the gateway on the WAN side, and say 192.168.0.254 on subnet 255.255.255.0 on the LAN side. The PCs, etc would have the gateway set as 192.168.0.254?
Any ideas?
Regards
Paul
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, their WAP is isolated somewhere in the building, and it is shared by all the other offices, so hooking up directly to it isn't an option I'm afraid.
I shall do as you say and call tech support for some advice on how best to achieve a solution by bridging.
I will post back when I have spoken to them and let you know what they suggest.
Thanks for your help.
Paul
I shall do as you say and call tech support for some advice on how best to achieve a solution by bridging.
I will post back when I have spoken to them and let you know what they suggest.
Thanks for your help.
Paul
Now as to what router to get I'm not sure, I've never used any with a wireless WAN interface, it's just not the normally done thing. Is there no hope of getting a wired connection to the network? It will greatly improve performance and reliability. Is the WAP you're accessing nearby, like in your office? A lot of the bigger ones have LAN Ethernet ports that you could just hook into. I'd strongly recommend looking into getting this wired, you'll only regret it in the long run if you don't...