dhcpd is screwing with me...

[Forsaken <forsaken@targaryen.us>]

Ok, here's the situation - 

I have a router and a switch.

The switch is chopped up into 4 different vlans, only two of which are
relevant to this discussion -

Topology looks something like this:

                   Router
                      |
	Vlan1 ---- Switch --- Vlan2

Vlan1: 192.168.2.0/24
Vlan2: 192.168.3.0/24

The switch has a trunk line to the router, which has subinterfaces
setup to do intervlan routing. The individual ports for each vlan are
restricted to that vlan.

Vlan1 are my workstations, Vlan2 are my servers. I've setup dhcpd on a
server in Vlan2. It has a single NIC with a static IP of 192.168.3.7. 

The router is configured with the ip helper-address on the subinterface
for Vlan1, so it should relay dhcp requests. 

The problem I'm having is that I haven't gotten that far, because dhcpd
won't start. 

This is what my dhcpd.conf looks like:

ddns-update-style none;
option domain-name "boo.local";
option domain-name-servers 192.168.3.7,192.168.1.1;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet 192.168.3.0 netmask 255.255.255.0 {
        range 192.168.3.100 192.168.3.200;
        option routers 192.168.3.1;
        option broadcast-address 192.168.3.255;
        option subnet-mask 255.255.255.0;
}
subnet 192.168.2.0 netmask 255.255.255.0 {
        range 192.168.2.100 192.168.3.200;
        default-lease-time 86400;
        max-lease-time 86400;
        option routers 192.168.2.1;
        option broadcast-address 192.168.2.255;
        option subnet-mask 255.255.255.0;
        option domain-name-servers 192.168.3.7;
}

Whenever I try to start dhcpd, I get the following:

root@fire:/etc/dhcp3# /etc/init.d/dhcp3-server start
dhcpd self-test failed. Please fix the config file.
The error was: 
Internet Systems Consortium DHCP Server V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Address range 192.168.2.100 to 192.168.3.200, netmask 255.255.255.0
spans multiple subnets!

I'm at something of a loss. Everything I can find on the subject says
that this should work fine even if the server is single-homed, as long
as your router will do dhcp relay correctly. I can't help but think I'm
missing something simple. I've tried setting up a 192.168.2.0/24
address as an alias on eth1 (the interface that has the 192.168.3.0/24
address), but it still refuses to start.

I'd prefer not to multi-home the server. I figure there has to be a way
to get this working the way I want it, otherwise there wouldn't be a
need for dhcp relay agents to exist, but I just can't figure out what
I'm overlooking.

Thanks in advance for any help!