• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Multiple public Static IP addresses

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Are you quite sure that your router's external IP is correct? I've worked on /29 DSL networks very similar to yours where the external router interface is assigned a private IP on the ISP's network, and the network address + 1 is assigned to the internal interface, becoming the default gateway.

Also, if you're planning on running another NAT for desktop machines behind the first one, I don't see the point of running a one-to-one NAT for the servers. Just let the router route packets and be done with it. But these guys know a lot more than I do...
 

Are you quite sure that your router's external IP is correct? I've worked on /29 DSL networks very similar to yours where the external router interface is assigned a private IP on the ISP's network

Nope, it shows that one in the router configuration and it's what my ISP sent me in an e-mail.
 

Also, if you're planning on running another NAT for desktop machines behind the first one, I don't see the point of running a one-to-one NAT for the servers. Just let the router route packets and be done with it.

As far as I can see, this the most simple and efficient way for what I need.
 
I'm really trying to understand what you're asking for, so I re-read this entire thread and have found that nowhere have you told us what it is that you're trying to accomplish. Yes, you've said that you want to map external IPs address directly to internal IP addresses on specific machines.. but why?? What is it that you're trying to accomplish that requires this specific setup, and will not work via any of the other methods suggested thus far??

I mean, if this is just some exercise in doing something because you think it can be done, that's fine, but please say so.

My own workplace has hundreds of PCs, 3 dozen servers - 5 of which are webservers, intranet, email, etc and it's all behind a single external IP address. And everybody can still access the seperate websites and domains that they need to both internal and external as the case may be without issue.


 
Yes, but the only way you can run multiple physical webservers behind a single IP is to use alternative ports which in my opinion is just messy. It's not a problem for me to get multiple IP addresses, my ISP were very reasonable and helpful about it, and if my router is faulty then I'll just get a cisco one which in my opinion would be easier to configure, would provide better performance, and would be more reliable anyway.

I mean, why make things difficult for myself and struggle? It wasn't a problem for me to get more IP addresses for my servers and it's more flexible this way for any possbile future expansion. This really is something I will not go back on, I'll be happy with this setup when I get it working how I want it. I've contacted Zyxel support and hopefully they'll get back to me tomorrow and tell me if there's something i'm missing or if the router is glitchy.
 
I don't happen to agree that using alternative ports is messy, nor do I believe that you're giving yourself more flexibility with that arrangement, but it's your operation to configure, so I wish you luck!
 

I've solved the problem now. I contacted Zyxel support who, after a fashion, told me that the firmware version on my router (the latest version) had some known routing issues and suggested that I downgraded to the last version. I did this and now it works fine.
 
Originally posted by: nweaver
which makes it (dum dum dum) configuration...not hardware.

No, It's software actually. I'd configured it correctly, but the firmware was buggy.

EDIT: Still getting a cisco 837 to replace it though, Zyxel's tech support was wholly inadequate. I e-mailed them at 4pm on Friday and they took until midday on the following monday to get back to me.

 
Back
Top