* Well that and the WAN dhclient that's in progress.
Dhcp client has already been committed to the development branch which means itll be available in the next release (glendale) assuming the testing goes well. stig _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silvertip257 Sent: Sunday, January 13, 2008 6:55 PM To: Marat Nepomnyashy; vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] DHCP pool questions Why cannot I take addresses out of the beginning of the block like I'd rather it do? How can I (without rewriting/modifying source code)? That would really stink to have to statically assign everything to make it the way (that it makes sense). It's great and all that it actually does assign an address and ' works ', but why not start at the beginning? >From what Marat wrote, I understand that you've seen that behavior before - confirmed. Now, can it be changed? I won't try to start any wars here, but that would unfortunately be one reason I would not want to use Vyatta. Well that and the WAN dhclient that's in progress. I could have sworn (oh and I did commit it) that I added a config for a second dhcp pool (separate) for eth2, but voila it's gone when I check dhcpd.conf... Thanks, Mike On Jan 13, 2008 8:37 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: Hi Mike, As far as I know, it is normal for the ISC DHCP server that the Vyatta router is using to lease out addresses starting from the last address of the DHCP lease block, I've seen this before. Not quite sure myself why ISC does it this way, maybe there is an assumption that the IPs at the end of the block are less likely to be already taken... When you write "I have discovered that various parts have been separated from the main config", what do you mean? The DHCP server configuration file is '/opt/vyatta/etc/dhcpd.conf', not '/opt/vyatta/etc/dhcp.conf'. The configuration for eth2 should not show up there if you did not configure any DHCP leases for any of the subnets to which your the interface is connected. If you have additional questions, please send us snippets of your router configuration under hierarchies 'interfaces ethernet' and 'service dhcp-server'. Please also send the contents of '/opt/vyatta/etc/dhcpd.conf'. Thanks, Marat ----- Original Message ----- From: silvertip257 <mailto:[EMAIL PROTECTED]> To: vyatta-users@mailman.vyatta.com Sent: Saturday, January 12, 2008 4:36 PM Subject: [Vyatta-users] DHCP pool questions I've set up a complete vyatta system a few times, even with two versions (2.2 and 3.0). I'm currently working with 3.0 and I'm getting the same behavior as the last time. I setup a DHCP server on eth1, but when it hands out addresses, it always gives out the last address in the block (in this case 192.168.0.60 consistently). When finding the configuration, I have discovered that various parts have been separated from the main config - I don't know if it was that way in previous versions, but thought I'd mention it. Also, my DHCP server for eth2 does not show up in /opt/vyatta/etc/dhcp.conf ;; that's another issue that I'll have to solve after this one. My config for the DHCP server: shared-network Subnet1 { subnet 192.168.0.32 netmask 255.255.255.224 { not authoritative; default-lease-time 86400; max-lease-time 86400; range 192.168.0.34 192.168.0.60; } Thanks, Mike -- // SilverTip257 // ========================== ~ · · /V\ // \\ /( )\ ^`~´^ _____ _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users <http://mailman.vyatta.com/mailman/listinfo/vyatta-users> -- // SilverTip257 // ========================== ~ · · /V\ // \\ /( )\ ^`~´^ -- // SilverTip257 // ========================== ~ · · /V\ // \\ /( )\ ^`~´^
_______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users