No need not to be on LAN anymore ??

[Roman2K]

Hi !

I just saw that in the requirements page it is not written anymore that we must have an internet IP address exclusively for the PC running DA.

Is it true ?? It would be so great !

[DirectAdmin Sales]

As per http://www.directadmin.com/install.html our software does require at least one IP address, and by this we mean an external (real) IP bound to your primary ethernet device.

Mark

[Roman2K]

Originally posted by DirectAdmin Sales
As per http://www.directadmin.com/install.html our software does require at least one IP address, and by this we mean an external (real) IP bound to your primary ethernet device.

Mark
Ok thank you. But when will you think about changing this annoying system ?

[jmstacey]

I don't personally see this happening anytime soon (if ever), since it is the most reliable way to protect DirectAdmin's investment and hard work.

It is not that big of a deal since you can setup your router, firewall etc so that it assigns the external IP addresses to the server and yet still protects you.

Probably could word that better...

[nobaloney]

Jon, if you buy a "cheap" router designed for home use it's unlikely you can turn off NAT and just forward the public IP#s.

I haven't found a "cheap" router that'll forward without NAT.

Roman2K, what do you mean by annoying? It seems reasonable to me that a webserver be hosted on the Internet with a public IP#. While it does limit the user of the server for most Intranets, I don't see that as the market JBMC is going after; most Intranets seem to run on Windows.

Jeff

[jmstacey]

Of course not with a cheap router. Why would you be using one designed for home use in this type of environment. (other than the cheapness)

Eitherway, your right and their not cheap per-say.
But if you've got an extra computer laying around you can set that one up to work as a router with a little work.

[nobaloney]

Roman2K hasn't responded yet so we don't know his/her reasoning.

Most people don't know how to manage their own router built from open source solutions.

Our Routers are built on SuperMicro hardware and a BSD software stack.

Jeff

[Roman2K]

Hi,

Sorry but I don't understand the english very well.

Anyway I understood you said me to configure my router/firewall to assign the public IP address to the server PC.

The problem is I don't know how to do this. I have a router Linksys WRT54GS and the server PC has an internal IP address (style 192.168.1.x) and all the needed ports forwarded.

Do you know how to assign the public IP address to the server PC (so it will not have 192.168.1.x but 82.234.206.99) and still have the rest of the network working as actually ?


It seems reasonable to me that a webserver be hosted on the Internet with a public IP#
Because I not rich enough to have 2 public IP address but only one and 4 PC behing by NAT (the server PC is one of the 4).

Thank you in advance.

EDIT : say me if you want me to know other things.

[nobaloney]

Edited 06/05/05:

You may not be able to do it with your router.

If the manual doesn't say anything about it, you probably can't do it.

Jeff

[bdk]

I know it isn't to the point of the original post but it is possible to turn off NAT on a Linksys to allow public IPs to be used behind it, ones that are assigned by your ISP or another provider that can issue IPs.

I work for an ISP and I do it all the time when a customer wants a routed network on their connection. It works great.

But if you do not have a business account w/ your ISP, you most likely won't have the option to purchase a routed network.

[Roman2K]

Yes it would be great but I'm a "private individual" ("particulier" in french : not an enterprise) in France and have only one public static IP address :(.

[nobaloney]

[QUOTE]Originally posted by bdk
it is possible to turn off NAT on a Linksys to allow public IPs to be used behind it[/b]
After I read your post I logged into my new Linksys router (one provided by Vonage as we got more phone lines from them) and you're right; the new Linksys routers do offer the ability to route public IP#s.

So I've edited my post to be more general.

Thanks for the heads up.

Jeff