This is F-17/64 bit.

The dd-wrt router assigns dhcp addresses on our LAN. However this
computer 192.168.1.9., if I let NetworkManager assign an address via
dhcp it insists on assigning 192.168.1.10, the next unused dhcp
address no matter what I enter under NM edit Automatic. If I go to
NM edit and assign the address as Manual it becomes 192.168.1.9 as
expected. Obviously the simple solution is to stay with the latter case.

My question then is, is this to be expected due to two dhcp servers
trying to assign an address, or am I doing something wrong?.

Bob

.

--
http://www.qrz.com/db/W2BOD


box9

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 04:28 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
> This is F-17/64 bit.
>
> The dd-wrt router assigns dhcp addresses on our LAN. However this
> computer 192.168.1.9., if I let NetworkManager assign an address via
> dhcp it insists on assigning 192.168.1.10, the next unused dhcp
> address no matter what I enter under NM edit Automatic. If I go to
> NM edit and assign the address as Manual it becomes 192.168.1.9 as
> expected. Obviously the simple solution is to stay with the latter case.
>
> My question then is, is this to be expected due to two dhcp servers
> trying to assign an address, or am I doing something wrong?.
>
Having two DHCP servers with overlapping IP ranges is A Bad Thing.

My router is set to do DHCP in the range .100 to .199. My PC has a
static address set via NM as .10. All static IP addresses (for me) are
in the range .10 to .50. My wife has .51 to .98. Thus, peace and
harmony are preserved.

Another option is to set a reserved address on the router for your
computer so it always gets .9 and let NM use NetworkManager. That's
probably the way I should have set up my network, but I'm too lazy to go
back and fix things.


--
-- Steve


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/07/12 17:37, Steven Stern types:

On 07/10/2012 04:28 PM, Bob Goodwin - Zuni, Virginia, USA wrote:

This is F-17/64 bit.

The dd-wrt router assigns dhcp addresses on our LAN. However this
computer 192.168.1.9., if I let NetworkManager assign an address via
dhcp it insists on assigning 192.168.1.10, the next unused dhcp
address no matter what I enter under NM edit Automatic. If I go to
NM edit and assign the address as Manual it becomes 192.168.1.9 as
expected. Obviously the simple solution is to stay with the latter case.

My question then is, is this to be expected due to two dhcp servers
trying to assign an address, or am I doing something wrong?.


Having two DHCP servers with overlapping IP ranges is A Bad Thing.

My router is set to do DHCP in the range .100 to .199. My PC has a
static address set via NM as .10. All static IP addresses (for me) are
in the range .10 to .50. My wife has .51 to .98. Thus, peace and
harmony are preserved.

Another option is to set a reserved address on the router for your
computer so it always gets .9 and let NM use NetworkManager. That's
probably the way I should have set up my network, but I'm too lazy to go
back and fix things.




Ok, so there's nothing I can do without changing my system address
assignments which began before I started using NetworkManager. I
will just assign the NM address manually.

It works either way but I like to see the device names I have
assigned in the DHCP client list and when it assigns a new address I
lose the name, it's blank.

Thanks for the help.

Bob



--
http://www.qrz.com/db/W2BOD

box9

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Bob Goodwin - Zuni, Virginia, USA <bobgoodwin <at> wildblue.net> writes:

>
> On 10/07/12 17:37, Steven Stern types:
> > On 07/10/2012 04:28 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
> >> This is F-17/64 bit.
> >>
> >> The dd-wrt router assigns dhcp addresses on our LAN. However this
> >> computer 192.168.1.9., if I let NetworkManager assign an address via
> >> dhcp it insists on assigning 192.168.1.10, the next unused dhcp
> >> address no matter what I enter under NM edit Automatic. If I go to
> >> NM edit and assign the address as Manual it becomes 192.168.1.9 as
> >> expected. Obviously the simple solution is to stay with the latter case.
> >>
> >> My question then is, is this to be expected due to two dhcp servers
> >> trying to assign an address, or am I doing something wrong?.
<SNIP>
>
> Ok, so there's nothing I can do without changing my system address
> assignments which began before I started using NetworkManager. I
> will just assign the NM address manually.
>
> It works either way but I like to see the device names I have
> assigned in the DHCP client list and when it assigns a new address I
> lose the name, it's blank.
>
> Thanks for the help.
>
> Bob
>
You will find that *BOTH* the DHCP client and DHCP server cache previous
addresses. A client that has had an address will request the same address.
Even if the client doesn't ask for the same address, the server will check its
cache to see if a particular address was previously assigned and will re-assign
the same address.

Found this out the hard way when trying to get DHCPv6 working. Still have some
similar oddities to you that I need to clean out caches to make go away.

Cheers,
Dave



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/07/12 20:36, David G. Miller types:

You will find that *BOTH* the DHCP client and DHCP server cache previous
addresses. A client that has had an address will request the same address.
Even if the client doesn't ask for the same address, the server will check its
cache to see if a particular address was previously assigned and will re-assign
the same address.

Found this out the hard way when trying to get DHCPv6 working. Still have some
similar oddities to you that I need to clean out caches to make go away.

Cheers,
Dave





Yes, I believe I was seeing that too. The problem began after I had
temporarily run an old Apple Mac portable on the Ethernet switch, I
gave it the address 192/168.1.10 which was the next in line but then
it persisted in assigning that number to this computer. The
computers in my room all run through an Ethernet gigabit switch
connected to an access point so that I see any problems that might
crop up with the "wifi" system I think NM sees the switch as the
client and that's confusing things.

Bob.

--
http://www.qrz.com/db/W2BOD


box9

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org