| 1 |
On Wed, Oct 29, 2008 at 6:49 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
<snip> |
| 3 |
> More sophisticated routers allow you to set up on their CLI static LAN IP |
| 4 |
> addresses using the DUID string, instead of the client's MAC hardware |
| 5 |
> address. |
| 6 |
> |
| 7 |
> Previous versions of dhcpcd had the vram USE flag which copied the hardware |
| 8 |
> address into the DUID string and the dhcp servers would happily recognise the |
| 9 |
> original network device, while using the DUID string. Now the vram flag is |
| 10 |
> gone. Therefore, if you cannot set up static IP addresses with your router's |
| 11 |
> CLI using the client_indentifier string (like e.g. on Cisco and |
| 12 |
> Adtran/Netvanta routers), the only other solution would be to set it on the |
| 13 |
> client side. That's an inconvenient solution if you have a laptop which |
| 14 |
> connects to all sort of networks with different LAN IP addresses/ranges. In |
| 15 |
> that case you may have to run ifconfig and route manually each time you |
| 16 |
> connect to a network. |
| 17 |
> -- |
| 18 |
> Regards, |
| 19 |
> Mick |
| 20 |
> |
| 21 |
|
| 22 |
Or, actually, you could just give in and use a different dhcp |
| 23 |
client... one more forgiving of less RFC compliant servers. Just |
| 24 |
winging an admittedly untested idea... try "busybox udhcpc" and see if |
| 25 |
it gives you the right IP... and if so, try emerging net-misc/udhcp |
| 26 |
(different from BB's built in, but it's worked in all the same places |
| 27 |
as BB's has for me, which includes some very cheap routers) and |
| 28 |
setting your conf.d/net to use it over other clients. ( modules=( |
| 29 |
"udhcpc" ) ) |
| 30 |
|
| 31 |
-- |
| 32 |
Poison [BLX] |
| 33 |
Joshua M. Murphy |
Archives