Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
211
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 02:41:47 pm »
To summarize the earlier posts
Was this not done when setting up DHCP as shown in the attached screenshot? A Primary Nameserver was specified with the ip address of the router and resolving of names on the WAN works OK using nslookup. A Default Gateway Custom IP Address was also specified as the router ip address. If the nameserver element works why not the gateway element?
At the time of the first post in this thread, reaching the eBox web-GUI from a remote machine was problematical. To address this a lightweight GUI was locally installed.
Window Manager=Openbox
Various components of LXDE
Web Browser=Firefox
When the static ip address is allocated from the router the web can be browsed from the eBox machine in the usual manner. When the same static ip address is allocated from eBox the web cannot be browsed. A page load error is generated and Firefox is unable to establish a connection.
Is eBox preventing this in some way? The eBox firewall is currently disabled. nslookup of an external address is successful.
Quote from: Sam Graf
You're using just one DHCP server at a time, correct?Correct the router DHCP is disabled, eBox DHCP is enabled.
Quote from: Sam Graf
As I recall, if you've ever enabled the firewall module...This module has not been enabled on this installation.
Quote from: Saturn2888
Short version:
You need to assign a Gateway address for your eBox. Make it whatever the eBox IP is 192.168.2.1 I'm guessing. Don't forget to make a local DNS server too if you want.
Was this not done when setting up DHCP as shown in the attached screenshot? A Primary Nameserver was specified with the ip address of the router and resolving of names on the WAN works OK using nslookup. A Default Gateway Custom IP Address was also specified as the router ip address. If the nameserver element works why not the gateway element?
212
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 02:11:11 pm »Ah. I dunno how that would work but okay.I will wait for a while before I do anything further about this idea. This will give Sam Graf the opportunity to comment as he has contributed to the thread. If anyone at eBox has been following this they might advise whether there is/is no need to raise it in the Feature Requests Section.
Now to re-read the posts about using a web browser from the eBox machine.
213
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 01:38:07 pm »If it's fixed, you don't have to put it under the "Ranges" section...I understand this point, and as I mentioned in a previous post in the thread my idea is not neccessary to use eBox. I find it a more intuitive way of working and therefore am more comfortable with it.
I have used a variation of the idea in the past. In an earlier post Sam Graf described the way in which he has used the idea previously, all of which which leads me to conclude that it might be used by a sufficient number of people to suggest it to the eBox staff for consideration.
From my non-programmers perspective all that is required is for eBox not to assume (as is does currently) that a pre-defined block of addresses is only for dynamic allocation. I have no idea how much work this represents but I do recognise how desirable the feature might be.
214
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 01:00:35 pm »
Do these help? The idea is to pre-define the groups for both static and dynamic addresses. Dummy data has been used to create the screen shots and then edited to show where the difficulty lies.
215
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 12:50:07 pm »
Your idea to use screenshots is a good one. I am having trouble getting mine to display. I place the path and filename (jpg) between the image tags but they do not show. What am I missing? Any suggestions?
216
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 11:18:17 am »This functionality already exists. Now I'm really confused.On reading the post again I can see where it was ambiguously worded and edited it in an attempt to clarify it. Due to cross posting I have not studieed your screen shots yet.
217
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 10:28:33 am »This functionality already exists. Now I'm really confused.Can you show how to specify a range of static ip addresses where the range exceeds the number of addresses to be allocated at the moment? Some of the specified range will remain unallocated currently and some of the range will be allocated.
e.g.
range=x.x.x.2 - x.x.x.30
number of leases required=17
218
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 29, 2009, 09:44:18 am »...leaving the DHCP range in the "middle" of the address space, following the lead of the default range. Then I would use the unallocated addresses below the DHCP for one purpose and the addresses above for another, effectively slicing my address pie into three pieces.This is a very neat extention of what I wanted to achieve, but is only available as a product of the imaginative use of the unallocated address space. I wonder if it might be improved further?
Currently eBox allows the specification of a block of addresses that can be dynamically allocated via DHCP where the block exceeds the number of addresses presently required. It does not allow a static address to be created within a pre-specified block where the block is greater than the number of addresses currently required. If eBox allowed the specification of different types of blocks that incorporated unallocated addresses, (both dynamic and static), the eBox interface would become more 'self-documenting' and thereby more user friendly. Using your example it would be possible for the eBox DHCP interface to show the following:
RANGES
Name From To
Actives - Fixed x.x.x.2 x.x.x.30
Dynamically Allocated x.x.x.50 x.x.x.150
Servers - Fixed x.x.x.230 x.x.x.250
I have no idea what might be involved in making a change such a this but am in favour of 'self-documenting' and therefore see this as a desireble development. I am considering suggesting it via the Feature Request system and would like to refer to your post describing the way in which it was previously used. Is this OK with you?
Apr 29 - Edited by SAMK in an attempt to clarify ambiguities.
219
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 06:30:08 pm »
A final point related to this...
At the of the first post in this thread, reaching the eBox web-GUI from a remote machine was problematical. To address this a lightweight GUI was locally installed.
Window Manager=Openbox
Various components of LXDE
Web Browser=Firefox
When the static ip address is allocated from the router the web can be browsed from the eBox machine in the usual manner. When the same static ip address is allocated from eBox the web cannot be browsed. A page load error is generated and Firefox is unable to establish a connection.
Is eBox preventing this in some way? The eBox firewall is currently disabled. nslookup of an external address is successful.
At the of the first post in this thread, reaching the eBox web-GUI from a remote machine was problematical. To address this a lightweight GUI was locally installed.
Window Manager=Openbox
Various components of LXDE
Web Browser=Firefox
When the static ip address is allocated from the router the web can be browsed from the eBox machine in the usual manner. When the same static ip address is allocated from eBox the web cannot be browsed. A page load error is generated and Firefox is unable to establish a connection.
Is eBox preventing this in some way? The eBox firewall is currently disabled. nslookup of an external address is successful.
220
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 04:53:12 pm »
Hi Sam Graf,
In general I attempt to remember as little as necessary, hence the naming of the ranges in the experiment previously mentioned. The address allocated to the LAN workstation was from the 2nd group (addresses 100 upwards). I am attempting to establish if this was a coincidence, or by design on the part of eBox.
Does having 2 ranges within a single larger range allow eBox to only dynamically allocate addresses from this second group, effectively ignoring the 1st range? If this is the case (either by accident or design), creating the two groups assists in my desire to remember as little as needed and provides an aid to quickly identifying the nature of the address. It might be that a member of the eBox staff is able to provide the confirmation of its behviour.
Ultimately it is not strictly needed but is something I have used in the past and find very useful.
Many thanks for your input.
...you need to assign only one DHCP/dynamic address range. All addresses outside that range are by definition unallocated and can be assigned statically as needed.I understand and fully agree with this point. It is likely to be the method I adopt.
In general I attempt to remember as little as necessary, hence the naming of the ranges in the experiment previously mentioned. The address allocated to the LAN workstation was from the 2nd group (addresses 100 upwards). I am attempting to establish if this was a coincidence, or by design on the part of eBox.
Does having 2 ranges within a single larger range allow eBox to only dynamically allocate addresses from this second group, effectively ignoring the 1st range? If this is the case (either by accident or design), creating the two groups assists in my desire to remember as little as needed and provides an aid to quickly identifying the nature of the address. It might be that a member of the eBox staff is able to provide the confirmation of its behviour.
Ultimately it is not strictly needed but is something I have used in the past and find very useful.
Many thanks for your input.
221
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 03:18:23 pm »
As an experiment the following ranges have beed added within the available range created by eBox:
Web-GUI-->DHCP
Add Range
Add Range
On LAN Workstation
QUESTIONS
01 How does eBox decide which of the ranges to allocate a lease from?
02 What is the purpose of eBox being able to create multiple ranges within a larger available range?
Web-GUI-->DHCP
Add Range
- Name=Reserved
- From=192.168.2.4
- To=192.168.2.99
Add Range
- Name=Unreserved
- From=192.168.2.100
- To=192.168.2.250
On LAN Workstation
- ip address allocated via DHCP=192.168.2.100
QUESTIONS
01 How does eBox decide which of the ranges to allocate a lease from?
02 What is the purpose of eBox being able to create multiple ranges within a larger available range?
222
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 01:17:41 pm »
Hi Saturn2888
Thanks for your input
Thanks for your input
To help explain, what sixstone means is that when you are statically assigning addresses in the DHCP server, you don't want to have those also dynamically assigned.Fully agreed.
...Which means you don't have to setup a range of IPs which includes 192.168.2.2 because it'll be in your fixed-address list.What I wish to achieve is to reserve a block of successive fixed ip addresses. Initially the list of reserved addresses will exceed the number of leases required. From this block I can then maually allocate a name and MAC address within eBox to a device I wish to add to the network as and when the need arises.
...You will need to set up the fixed addresses mapping in the table...I have attempted to do this but all fields require populating before they can be saved. Providing dummy information of Address=192.168.2.x Name=Unallocated and MAC=xx:xx:xx:xx:xx:xx is not allowed as the MAC address is seen by eBox as invalid.
223
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 12:14:46 pm »You just forgot to add a range or a fixed IP address mapping to your DHCP configuration. If you don't do so, the DHCP will not serve any lease.Hi sixstone,
I assumed that web-gui-->DHCP Available Range=192.168.2.1 - 192.168.2.254 indicated that these addresses were ready to lease out.
Having defined a range the client now obtains an address.
I wish to define two ranges and would welcome some advice on how this is best done in eBox.
Range 1
Fixed address allocated against MAC address
192.168.2.2 - 192.168.2.49
Reserved whether or not a name and MAC address is known to eBox and only issued when a name and MAC address is declared within eBox.
Is it possible to reserve a range without entering each name and address?
Range 2
Dynamic address
192.168.2.50 - 198.168.2.250
Unreserved and allocated upon request.
224
Installation and Upgrades / Re: Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 09:59:19 am »Please post the contents of /etc/dhcp3/dhcpd.conf
As Requested:
Code: [Select]
# extra options
# RFC3442 routes
option rfc3442-classless-static-routes code 121 = array of integer 8;
# MS routes
option ms-classless-static-routes code 249 = array of integer 8;
ddns-update-style none;
option domain-name-servers 192.168.2.1;
default-lease-time 1800;
max-lease-time 7200;
shared-network eth0 {
subnet 192.168.2.0 netmask 255.255.255.0 {
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1;
default-lease-time 1800;
max-lease-time 7200;
}
}
225
Installation and Upgrades / Request Help Moving DHCP from Router to eBox
« on: April 28, 2009, 09:28:53 am »
Having trouble getting a working configuration for DHCP in eBox and am hoping to to get some advice. The LAN workstation does not recieve an ip address from the eBox Machine.
Router
ip address=192.168.2.1
DHCP Status=Disabled
eBox Machine
Single NIC installed=eth0
Module Status
DHCP
From the eBox Machine
ifconfig=192.168.2.3
ping 192.168.2.1=Successful
nslookup www.bbc.co.uk=Successful
From the LAN Workstation (Dynamic IP DHCP)
ifconfig=ip address not allocated
From the LAN Workstation (Static IP Locally Set)
ifconfig=192.168.2.108
ping 192.168.2.1=Successful
ping 192.168.2.3=Successful
nslookup www.bbc.co.uk=Successful
I've gone 'snow-blind' on this and simply cannot see the answer.
Router
ip address=192.168.2.1
DHCP Status=Disabled
eBox Machine
Single NIC installed=eth0
Module Status
- DHCP=Enabled
- DNS=Disabled
- DHCP=Running
- eth0=Static
- 192.168.2.3
- 255.255.255.0
DHCP
- Custom Gateway=192.168.2.1
- Domain=Blank
- Custom Nameserver=192.168.2.1
- IP Address=192.168.2.3
- Subnet=192.168.2.0/24
- Available Range=192.168.2.1-192.168.2.254
From the eBox Machine
ifconfig=192.168.2.3
ping 192.168.2.1=Successful
nslookup www.bbc.co.uk=Successful
From the LAN Workstation (Dynamic IP DHCP)
ifconfig=ip address not allocated
From the LAN Workstation (Static IP Locally Set)
ifconfig=192.168.2.108
ping 192.168.2.1=Successful
ping 192.168.2.3=Successful
nslookup www.bbc.co.uk=Successful
I've gone 'snow-blind' on this and simply cannot see the answer.