F5F Stay Refreshed Power Users Networks Moving from public IP to Private

Moving from public IP to Private

Moving from public IP to Private

M
MavrosGR
Senior Member
579
07-12-2023, 12:31 PM
#1
Hello! I'm trying to figure out a way to switch your business network from public IPs on every device to private ones (like 192.168.x.x). The goal is to move everything to a Draytek device, keeping the original public IPs on the NetGEAR and gradually consolidating them. You have a BT line coming in, which should help with connectivity. Since your networking skills aren't top-tier, I'll keep it simple and focus on practical steps you can take.
M
MavrosGR
07-12-2023, 12:31 PM #1

Hello! I'm trying to figure out a way to switch your business network from public IPs on every device to private ones (like 192.168.x.x). The goal is to move everything to a Draytek device, keeping the original public IPs on the NetGEAR and gradually consolidating them. You have a BT line coming in, which should help with connectivity. Since your networking skills aren't top-tier, I'll keep it simple and focus on practical steps you can take.

C
critic_swag
Junior Member
20
07-13-2023, 12:55 AM
#2
Are you certain all computers have a public IP address? This implies your ISP provides sufficient IPs and you direct them via your router for each device. What does a typical "public IP" appear like? (You can share just the first two parts for safety.)
C
critic_swag
07-13-2023, 12:55 AM #2

Are you certain all computers have a public IP address? This implies your ISP provides sufficient IPs and you direct them via your router for each device. What does a typical "public IP" appear like? (You can share just the first two parts for safety.)

M
Machine3721
Member
52
07-13-2023, 04:12 AM
#3
It's definitely feasible, this was something before the Internet expanded so much. Long ago I even used a tiny subnet as a home user, since web servers didn't allow multiple subdomains on the same IP address back then. Companies are very hesitant to switch, especially because making such a change would be too slow and complicate things unnecessarily. It really needs to happen all at once.
M
Machine3721
07-13-2023, 04:12 AM #3

It's definitely feasible, this was something before the Internet expanded so much. Long ago I even used a tiny subnet as a home user, since web servers didn't allow multiple subdomains on the same IP address back then. Companies are very hesitant to switch, especially because making such a change would be too slow and complicate things unnecessarily. It really needs to happen all at once.

W
walee123
Senior Member
737
07-16-2023, 12:26 PM
#4
The firm was established around 1970 with just five employees. Over the decades it grew to 40, and during the pandemic we now have 85 members. Our membership ranges from the top eight to 254 participants.
W
walee123
07-16-2023, 12:26 PM #4

The firm was established around 1970 with just five employees. Over the decades it grew to 40, and during the pandemic we now have 85 members. Our membership ranges from the top eight to 254 participants.

I
IchZocke
Member
139
07-21-2023, 07:54 PM
#5
Oh, it's fascinating! I didn't encounter anything like this before. Just to clarify, I don't have any background on this setup.
I
IchZocke
07-21-2023, 07:54 PM #5

Oh, it's fascinating! I didn't encounter anything like this before. Just to clarify, I don't have any background on this setup.

S
SantaBaby
Junior Member
4
08-05-2023, 02:06 PM
#6
It would be challenging to proceed step by step since you’d essentially manage both a LAN and a WAN simultaneously. With managed switches, you might isolate the new LAN in its own VLAN and add clients individually, but coordinating communication between devices for specific purposes remains tricky. The router could handle NAT if it supports it, though compatibility issues may arise with certain software and heavy traffic. Since it was only designed for basic routing, I’m uncertain about its capacity for robust Internet NAT or internal Public-to-Private setups. I’d focus initially on devices requiring just internet access.
S
SantaBaby
08-05-2023, 02:06 PM #6

It would be challenging to proceed step by step since you’d essentially manage both a LAN and a WAN simultaneously. With managed switches, you might isolate the new LAN in its own VLAN and add clients individually, but coordinating communication between devices for specific purposes remains tricky. The router could handle NAT if it supports it, though compatibility issues may arise with certain software and heavy traffic. Since it was only designed for basic routing, I’m uncertain about its capacity for robust Internet NAT or internal Public-to-Private setups. I’d focus initially on devices requiring just internet access.

B
Backstaber970
Senior Member
435
08-06-2023, 05:13 PM
#7
It comes down to how the machines operate. If they're merely browsing the internet without directly managing servers, set up one of the routers with DHCP and place them in front of it. Choose any RFC 1918 private range you prefer. Owning the entire octet doesn't necessarily require using it. Some older ISPs demand every client device has a fixed IP address, which I question here. Unless all devices are running web services, simply move them through a router that handles DHCP.
B
Backstaber970
08-06-2023, 05:13 PM #7

It comes down to how the machines operate. If they're merely browsing the internet without directly managing servers, set up one of the routers with DHCP and place them in front of it. Choose any RFC 1918 private range you prefer. Owning the entire octet doesn't necessarily require using it. Some older ISPs demand every client device has a fixed IP address, which I question here. Unless all devices are running web services, simply move them through a router that handles DHCP.

B
blingblong14
Member
80
08-07-2023, 03:16 AM
#8
My ideas revolved around devices such as printers, possibly requiring a fixed setup. As you mentioned, it depends on what's present on the network.
B
blingblong14
08-07-2023, 03:16 AM #8

My ideas revolved around devices such as printers, possibly requiring a fixed setup. As you mentioned, it depends on what's present on the network.

S
Skydelis
Junior Member
6
08-08-2023, 08:17 AM
#9
Thanks for the responses. We're planning to switch to a new router/firewall using the 10.0.0.0 range. We'll still need to manually input IP addresses for our devices, but I've decided to go ahead and make the change.
S
Skydelis
08-08-2023, 08:17 AM #9

Thanks for the responses. We're planning to switch to a new router/firewall using the 10.0.0.0 range. We'll still need to manually input IP addresses for our devices, but I've decided to go ahead and make the change.