Static IP Clients to ebox gateway

[ic3000]

Hi again to all!

I have on a network that i manage some different servers that require a static IP.

My problem is that i'm using ebox as a gateway with dhcp to the network and my servers with a static ip cant reach the INTERNET using ebox as there gateway.

The ip's are out of the range i configured to the dhcp server and I've made entries to the mac addresses of the server so ebox assign static ips to them.

With this it works for a while, i think that when the lease time for a certain ip its reached, the servers that have a static ip loses the connection to internet and ebox...

Is there a way to have configured static ip's on a network using ebox as the gateway?

Thanks once again!

[nicolasdiogo]

hi,

i am not certain that i undertand what you have done.
but i would try something like this;

set your server to have dynamic ip, then
set ebox to give a static IP to each server.
you can do this by getting each server MAC address

you should have at least two interface correctly configured - 1 internal and 1 external.
you would also need a DNS for your internal network alread setup (eg: mynet.lan)

on eBox, click on DHCP and choose your internal interface from the drop-down list.

setup the common-options details

setup a new range for this interface (leave some room for the static IPs that you will give to your servers)

then add fixed addresses, for your servers, you will need;
name = normally the DNS name of this machine
MAC address = the value from your server interface
IP address = IP address that is used by DNS to find this machine

NOTE: DNS and DHCP work very closely together - make sure that you use the same IP values on both.

let me know if this is what you are looking for.

Nicolas

[ic3000]

Hi Nicolas!

Thank you for the reply!

What you described is exactly what i have now, but i need to have 2 server with static address just from the boot up of the machine without dhcp. I have a MS server 2003 with active directory and other machine that is a thin client server and for both i need to setup static addresses on the machine so they can work without problems expectatily the AD server that needs to work even if ebox gateway is down.

Is there a way for me  to have static addressees not assigned from ebox dhcp server but that can use ebox as there gateways!

Sorry for my bad english...

Thanks once more!

[Shazburg]

If you need your servers to keep a static IP regardless of your eBox server being up or not, you can either setup DHCP on a network router or just program the servers themselves with static IP addresses.

As for eBox as the gateway, there is no magic here. When you program the static IP addresses, you set the gateway to whatever internal IP address you use to access eBox with. It should match one of these:

192.168.x.x
172.16.x.x - 172.31.x.x
10.x.x.x

[nicolasdiogo]

yep,

as Shazburg says, you will need to configure each machine independently.

for your linux clients, see this:
http://www.cyberciti.biz/tips/howto-ubuntu-linux-convert-dhcp-network-configuration-to-static-ip-configuration.html

for windows:
http://www.hotcomm.com/FAQ/FAQ_staticIPXP.asp#static_assign

hope it solves the problem.

Nicolas

[ic3000]

Hi!

Thanks for your replies!

I don't have any problems setting up the static IP for the servers!

But when i configure those servers to use ebox for there gateway i don't have access to internet.

ebox DHCP clients can use the internet and connect to all the services on the ebox machine but the servers with static ip's cant use the internet or access the ebox machine services...

I think that this should be related to the firewall because i can see drooped network packages on firewall logs!

Do i need to setup some rules just for the static ips?

Tanks once again!

[nicolasdiogo]

could you post what are the ip range that eBox is providing to its clients?


in adition post the configuration of your servers with IP static; showing their respective:
IP address
mask
gateway

DNS servers as well


thanks

thanks,

[sixstone]

I think that this should be related to the firewall because i can see drooped network packages on firewall logs!

Do i need to setup some rules just for the static ips?

If you see that there is a firewall issue, then you have to allow those hosts to access the Internet through Firewall -> Packet Filter -> Filtering rules for internal networks.

Best regards,

[ic3000]

Thanks again for the replies!

My server is IP: 192.168.1.5 with gateway and primary dns on IP 192.168.1.254 with a mask 255.255.255.0

O DHCP range is from 192.168.1.100 to 192.168.1.200.

My DHCP clients have the same dns and gateway retrieved from ebox dhcp server.

I'm seeing dropped packages from 192.168.1.5 (that is my static ip) on firewall logs!

I've added a rule on the firewall that permits my object that is the ip 192.168.1.5 to any destination and service.

I think i have problems with the firewall modes because any change that i make is not being really available!

Iḿ using 1.2 Alpha just for testing i have done a normal setup but selecting all the packages manually!

Maybe this wasn't a good idea... i will setup again this machine and let you know my results shortly!

Thanks once more!

[sixstone]

Could you paste your firewall rules for internal networks? I'm assuming eBox is .254

Best,

[ic3000]

Hi have just installed a fresh ebox...

I haven't done any configurations now but my ebox version on dashboard says 1.1.20~svn13879...

Is this an older aplpha version?

Thanks again!

[nicolasdiogo]

it seems to be.

at least i am running version 1.0

an the main page show version 1.0-1

since you have reinstalled and not done anything.
why don't you reinstall using a standard ubuntu server iso - and then adding eBox after everything is working fine?

http://trac.ebox-platform.com/wiki/Document/Documentation/InstallationGuide#eBoxUbuntu8.04packages

[ic3000]

Hi Nicolas! Thank's for your reply!

I'm using and trying to test a alpha version of the next release of ebox that should be 1.2...

I think the problem is related to my specific configuration on ebox since i'm using the same network for external and internal adapters.

O ebox 1.0 i dont have problems configuring internal netwrk to 192.168.1.254 and 192.168.1.253 for the external adapter using a router just for ebox gateway on 192.168.1.1.

On this alpha it seems that this config wont work... i tested a new install and i finish with the exact same problem but if i do the same but having diferent networks for internal and external adapters it works ok.

I get an error just after the ebox network module loads talking something like an not initialised variable but it still works ok.

Thanks once again!

[nicolasdiogo]

i am no genius on network design, but having internal and external interfaces in the same network IP-mask does not seem a good idea.

why not try something a like external IP set by dhcp from your ADSL router, and internal ip on range 10.0.1.0/24

maybe SIXTONE will explain it better.