This is the first time I am encountering this, and it has me a bit confused as to how to set this up. I think I might need a new router to accomplish this.
I have a Cisco RV325
The local ISP has me setup with a Fiber line just installed. I am only familiar with configuring a small business router with a static IP block.
The configurations I have from my ISP for my static IP's is similar to the below.
Customer Layer 3 IP Information
(WAN BLOCK)
Link IP Address: 10.10.10.140/30
Gateway: 10.10.10.141
Layer 3 IP: 10.10.10.142
Layer 3 Subnet Mask: 255.255.255.252
Customer Usable IP Information
(LAN BLOCK)
Usable IP Block: 10.10.10.192/29
Usable IP Ranges: 10.10.10.193-198
Usable Subnet Mask: 255.255.255.248
If this were a typical ISP transparent bridge setup, I would have no problem setting up this internet connection.
I am confused as to how I would configure a link from router WAN port to switch and then set up my public IP block. I am starting to think it is not possible with the RV325.
I would need natting on one of the static IPs. Any suggestion on where to head in the right direction? Do I need to order a better router with more enterprise features?
Any push in the right direction would be incredibly helpful.
The only thing I can think of is setting up my WAN as a static IP, and then a VLAN with my subnets but then I can't figure out how to have my static IP block routed to my local network. I am just confused, and I haven't looked at routing information like this in ages.
Best Answer
This is indeed a typical config, and most likely doesn't require you to change your hardware.
On one hand, you have the /30 which will be used on the point to point WAN link between you device and the first IP device on the ISP's side. So you should set your device up with the IP they gave you (.142) and a default route pointing to the ISP's device at .141
Then, they are saying they have assigned a /29 block go you. What this means is basically that there is a static route on their side pointing to you WAN IP (.142) for that /29 range such that any traffic for that range is sent to your router. At that point it's up to you to decide how to use it.
You can either route it to another device on your network (a firewall, say) with a static route, or use it on the router itself for handling NAT rules. The range does not need to be associated with any physical interface on the device: the router will be receiving the traffic anyway, due to the ISP's static route, it just needs to know what to do with a packet reaching it with a dest IP in that range: route it further, or process it.