Good catch Aubrey.  Thanks a bunch!

Aubrey Wells wrote:
> Ah - you beat me to it, I was just in the middle of opening a bug. :) 
> I'll add my comments to yours as to what I discovered.
>
>
> ------------------
> Aubrey Wells
> Senior Engineer
> Shelton | Johns Technology Group
> 404.478.2790
> www.sheltonjohns.com
>
>
>
> On Oct 24, 2007, at 11:18 AM, Robyn Orosz wrote:
>
>> Hi Aubrey,
>>
>> I am seeing the same issue on my system.  I have opened a bug for this:
>>
>> https://bugzilla.vyatta.com/show_bug.cgi?id=2447
>>
>> Thank you for discovering this issue.
>>
>> One possible workaround is to assign an unused address directly 
>> beneath one of your ethernet interfaces and include this subnet in 
>> the DHCP server configuration.
>>
>> Example:
>>
>>    ethernet eth1 {
>>        hw-id: 00:0c:29:53:1e:6e
>>        address 10.10.10.10 { <-----------just an arbitrary address 
>> that won't conflict with any internal addresses
>>            prefix-length: 32
>>        }
>>        vif 10 {
>>            address 172.16.10.1 {
>>                prefix-length: 24
>>            }
>>        }
>>    }
>>
>>    dhcp-server {
>>        shared-network-name "DHCP-1" {
>>            subnet 10.10.10.10/32 { <---------just add this in and the 
>> DHCP server should commit fine w/o errors
>>            }
>>            subnet 172.16.10.0/24 {
>>                start 172.16.10.100 {
>>                    stop: 172.16.10.200
>>                }
>>                default-router: 172.16.10.1
>>            }
>>        }
>>    }
>>
>> Let me know if this works for you.  If this solution is not 
>> acceptable for some reason, you could also generate the dhcpd.conf 
>> file manually, remove the dhcp server configuration from the CLI, and 
>> then copy the dhcpd.conf file into /opt/vyatta/etc on boot and start 
>> the dhcpd on boot.  This would have to be in a script placed in 
>> rc.local.
>>
>> Thank you,
>>
>> Robyn
>>
>> Aubrey Wells wrote:
>>> Hello,
>>> I'm trying to get a dhcp server running on a vyatta router and i'm 
>>> having a little trouble. I want to run the server on a vlan 
>>> interface (53) off of int eth1. When I try to commit my config, it 
>>> tells me that the subnet I'm trying to use is not on any interfaces, 
>>> but it is. I think its because the subnet is on a vif. Relevant 
>>> output and config snips below:
>>>
>>> ### trying to add the dhcpd subnet ###
>>>
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># set 
>>> service dhcp-server
>>> [edit]
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># set 
>>> service dhcp-server shared-network-name Service
>>> [edit]
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># set 
>>> service dhcp-server shared-network-name Service subnet 172.16.254.0/24
>>> [edit]
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># commit
>>> [edit]
>>> Commit Failed
>>> DHCP server configuration error.  None of the DHCP lease subnets 
>>> attempted in commit are inside any of the ethernet interface subnets 
>>> configured on this system.  At least one DHCP lease subnet must be 
>>> inside an ethernet interface subnet.
>>> DHCP server configuration commit aborted due to error(s).
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>#
>>>
>>>
>>> ### my routing table showing the subnet is on int eth1.54 ###
>>>
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># run 
>>> show route
>>> [edit]
>>> Routes: 9/9, Paths: 9/9
>>> 0.0.0.0/0               [static(1)]     > to 4.x.x.5          via 
>>> eth0.50
>>> 4.x.x.4/30            [connected(0)]  > to 4.x.x.6          via eth0.50
>>> 8.x.x.0/29            [connected(0)]  > to 8.x.x.1          via eth1.51
>>> 8.x.x.8/29            [connected(0)]  > to 8.x.x.9          via eth1.52
>>> 8.x.x.16/28           [connected(0)]  > to 8.x.x.17         via 
>>> eth1.1192
>>> 8.x.x.32/27           [connected(0)]  > to 8.x.x.33         via eth1.53
>>> 10.11.80.0/24           [connected(0)]  > to 10.11.80.6         via 
>>> eth0.1180
>>> 127.0.0.0/8             [connected(0)]  > to 127.0.0.1          via lo
>>> 172.16.254.0/24         [connected(0)]  > to 172.16.254.1       via 
>>> eth1.54
>>>
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>#
>>>
>>> ### eth1 config ###
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]># show 
>>> interfaces ethernet eth1
>>>     hw-id: 00:11:43:30:89:b2
>>>     vif 51 {
>>>         address 8.x.x.1 {
>>>             prefix-length: 29
>>>         }
>>>     }
>>>     vif 1192 {
>>>         address 8.x.x.17 {
>>>             prefix-length: 28
>>>         }
>>>     }
>>>     vif 52 {
>>>         address 8.x.x.9 {
>>>             prefix-length: 29
>>>         }
>>>     }
>>>     vif 53 {
>>>         address 8.x.x.33 {
>>>             prefix-length: 27
>>>         }
>>>     }
>>>     vif 54 {
>>>         address 172.16.254.1 {
>>>             prefix-length: 24
>>>         }
>>>     }
>>>
>>> [edit]
>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>#
>>>
>>>
>>> Any ideas? I'm running the latest beta.
>>>
>>> *
>>> *
>>> *------------------*
>>> *Aubrey Wells*
>>> /Senior Engineer/
>>> Shelton | Johns Technology Group
>>> A Vyatta Ready Partner
>>> www.sheltonjohns.com
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> Vyatta-users mailing list
>>> Vyatta-users@mailman.vyatta.com
>>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users
>>>
>
_______________________________________________
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users

Reply via email to