Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was wondering if anyone could give me some evidence to whether or
not using a public IP range on a private network would in fact
confuse things, i.e. equipment,mailservers etc etc...
A client of mine, before they were a client, was given a
192.147.160.XXX internal IP structure which is a public range. To me
this just seems ugly and just asking for trouble. They have a Sonic
Wall firewall, which routes traffic to the sendmail server which sits
at 192.147.160.7. Yes maybe the firewall is smart enough to know that
its on the inside but somewhere along the traffic I bet theres some
confusion going on.
i dont see the problem? i wish i had a range of public IP addresses. All you need for the outside is a router that advertises your range and knows where to route traffic, after that, you can treat it like any other network, just with public IP's. It presents more security issues i guess....but it would allow you to run mulitple servers with different IPs rather than having to do port forwarding with 1 IP. Like for instance, I can only have 1 webserver that accepts requests on port 80 because I only have 1 IP, but if i owned a public range of IPs (lets say 192.147.160.xxx) i could have 200+ different web servers. You could even do some classless subrouting and add routers to your network, have many different domains......aaaahh the joys of network setup.....anybody hiring?
oh i wanna point out that the whole classless subrouting stuff can be done with private ips too, you can take a 10.---- and be as creative as you want, only thing is, those IPs wont be seen on the internet.....that's really the only major difference i can think of.
Robert, sorry, while all your info was great, i may have not specified my issue clearly. My client DOESNT own the class 192.147.160.xxx, they just happen to use that range on their INTERNAL network, when they should be using a range like 192.168.xxx.xxx. My question is, does that pose problems.
ooooooh i think i get it now.....sorry. Yes, that could pose a problem if the gateway they use doesnt SNAT the internal address to the actual address they were assigned. If they start sending out packets onto the internet with that range, then nothing will come back because internet traffic with those adresses wont get routed back to that network. Yes it is ugly, i agree, i'd suggest they change it if possible.
Last edited by Robert0380; 05-19-2003 at 05:14 PM.
According to ARIN, that IP space belongs to Verio. Is your customer using Verio or someone reselling Verio's IP space as their ISP? If not, it's probably time to renumber.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.