Page 1 of 1

ip dhcp-server: no such IP network on selected interface

Posted: Sun May 10, 2009 1:00 am
by minfrin
Hi all,

While using the setup tool in an attempt to configure dhcp, I am getting an error message that I do not understand.

First off, my ip addresses look like this:

# ADDRESS NETWORK BROADCAST INTERFACE
0 172.16.252.3/24 172.16.252.0 172.16.252.255 wlan-a-backbone
1 172.16.250.2/23 172.16.250.0 172.16.251.255 vlan-public
2 172.16.250.3/23 172.16.250.3 172.16.250.3 wlan-g-public

So I try use the setup wizard to setup dhcp:

Select interface to run DHCP server on

dhcp server interface: wlan-a-backbone
Select network for DHCP addresses

dhcp address space: 192.168.0.0/24

At this point I have no idea why it has tried to fill in "192.168.0.0/24" in this field, this network doesn't appear anywhere within this router (that I am aware of). I change it to the correct network value and continue:

dhcp address space: 172.16.252.0/24
Select gateway for given network

gateway for dhcp network: 172.16.252.3

When I press enter the following appears:

If this is remote network, enter address of DHCP relay

There is no such IP network on selected interface
dhcp relay: 172.16.252.3

I don't understand - the error message claims "no such IP network" without specifying which IP network, and it says "on selected interface" without specifying which interface is the selected interface.

The IP address on the interface wlan-a-backbone is 172.16.252.3, and this is definitely in the network 172.16.252.0/24, and is definitely on the interface wlan-a-backbone.

Does anyone have an idea of what this router is really trying to tell me?

Regards,
Graham
--

Re: ip dhcp-server: no such IP network on selected interface

Posted: Sun May 10, 2009 1:05 am
by minfrin
I continue on regardless, and I try to enter nothing as a DHCP relay, as I don't want to use a DHCP relay:

dhcp relay:
invalid value for argument relay

Ok, so it wants a dhcp relay. So I try the default value:

dhcp relay: 172.16.252.3
Select pool of ip addresses given out by DHCP server

addresses to give out: 172.16.252.50-172.16.252.254
Select DNS servers

dns servers: 209.212.96.1,209.212.97.1
Select lease time

lease time: 3d
failure: setup failed to add ip pool: pool has overlapping ranges

"Pool has overlapping ranges" makes no sense. The range "172.16.252.50-172.16.252.254" is a single range, it doesn't overlap by definition.

There is only one other IP pool on this router, and it too doesn't overlap:

# NAME RANGES
0 public-pool 172.16.250.20-172.16.251.254

Can anyone decode this cryptic behavior for me? Does the setup tool work, first of all?

Re: ip dhcp-server: no such IP network on selected interface

Posted: Sun May 10, 2009 4:43 am
by SurferTim
First off, my ip addresses look like this:

# ADDRESS NETWORK BROADCAST INTERFACE
0 172.16.252.3/24 172.16.252.0 172.16.252.255 wlan-a-backbone
1 172.16.250.2/23 172.16.250.0 172.16.251.255 vlan-public
2 172.16.250.3/23 172.16.250.3 172.16.250.3 wlan-g-public
One thing I see: vlan-public and wlan-g-public have the same localnets. I would recommend changing one of them. That is probably the reason the wlan-g-public network assignment is messed up. It should look like this:
2 172.16.250.3/23 172.16.250.0 172.16.251.255 wlan-g-public
but vlan-public has that address range already.

Re: ip dhcp-server: no such IP network on selected interface

Posted: Sun May 10, 2009 2:15 pm
by minfrin
One thing I see: vlan-public and wlan-g-public have the same localnets. I would recommend changing one of them. That is probably the reason the wlan-g-public network assignment is messed up. It should look like this:
2 172.16.250.3/23 172.16.250.0 172.16.251.255 wlan-g-public
but vlan-public has that address range already.
vlan-public and wlan-g-public are bridged together, initially in an attempt to expose the public net to a Linux machine, but the Linux machine couldn't see the VLAN. A wifi client connecting to the wlan could ping both IPs without a problem.

Re: ip dhcp-server: no such IP network on selected interface

Posted: Mon May 11, 2009 12:12 pm
by Chupaka
vlan-public and wlan-g-public are bridged together
then you should add address on bridge, not on bridge's ports