I have a block of 5 (/29) static IPs from my ISP. I have the base address (x.x.x.121) set up and working fine through my hAP AC. I just installed a second server, and I wanted to configure it to accept inbound traffic on the highest address (x.x.x.125). I copied the NAT and hairpin NAT rules from the base address, changing the DST address and the To address to point to the new machine. However, so far I cannot access or ping the machine from WAN, even though it’s working well on the local subnet. I can’t rule out some issue with the ISP’s (AT&T U-verse) gateway settings. Any suggestions?
Update: After playing around a little further, I strongly suspect it’s a firewall issue within the ISPs gateway. Unfortunately they provide almost no documentation, so I’ll probably have to sit in the “customer service” queue for an hour. Still soliciting suggestions for ways to make sure and isolate the issue.
Can you plug a dummy switch (or switch/bridge in RB) in-between isp modem & RB, assign ip in that range and try getting in. If that works then it’s definitely issue with ISP.
SOLVED; it was AT&T’s problem. I spent an hour on the line with AT&T tech support only to be told bluntly that I couldn’t use my own router; I had to plug everything directly into their gateway if I wanted to use the additional IPs. Well, that wasn’t acceptable as the only way I could access my servers on the upper IPs was to use WAN, they would have been off my LAN. I want to set them up so that admin access is only possible off my local network. After 15 rounds with Google and DuckDuckGo I finally found this thread from others who have commiserated with much the same issue. By setting my hAP up as a “cascaded router” it seems to be recognizing the upper IP addresses now…no thanks to AT&T. I had asked the tech support guy about this specifically, and he was clueless. Good luck to others with U-Verse in future…