[pfSense Support] unexpected dhcp lease

2005-09-28 Thread Imre Ispanovits
Hi, 

I have a problem with pfSense's dhcp server since 0.85.x (I guess it wasn't an 
issue in 0.84.6).
I have two lan interfaces and  both serves as dhcp server, of course not 
overlapping. 
My problem is that on lan2 (opt2 - xl0) a dynamic ip address is always issued 
despite it 
shouldn't be because only fixed leases expected. This is the only address I 
have to
configure for the dhcp servers range. What's more strange for that mac address 
(00:12:79:ad:c6:fc)
is a fixed lease reserved on the other (fxp0) interface. Which as I see in the 
logs once offered,
but the other address picked up.
This never happened on the other interface.

 In syslog I have:

Sep 28 14:35:04 last message repeated 2 times   
Sep 28 14:35:03 kernel: arp: 192.168.2.254 is on xl0 but got reply from 
00:12:79:ad:c6:fc on fxp0   
Sep 28 14:34:49 last message repeated 5 times   
Sep 28 14:34:36 dhcpd: send_packet: Invalid argument

and in dhcp logs:

Sep 28 14:35:03 dhcpd: DHCPNAK on 192.168.2.254 to 00:12:79:ad:c6:fc via fxp0   
Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4) from 
00:12:79:ad:c6:fc (TRC-dc5100) via fxp0: wrong network. 
Sep 28 14:35:03 dhcpd: DHCPACK on 192.168.2.254 to 00:12:79:ad:c6:fc 
(TRC-dc5100) via xl0   
Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4) from 
00:12:79:ad:c6:fc (TRC-dc5100) via xl0  
Sep 28 14:35:03 dhcpd: DHCPOFFER on 192.168.0.22 to 00:12:79:ad:c6:fc via fxp0  
Sep 28 14:35:03 dhcpd: DHCPDISCOVER from 00:12:79:ad:c6:fc via fxp0 
Sep 28 14:35:03 dhcpd: DHCPOFFER on 192.168.2.254 to 00:12:79:ad:c6:fc 
(TRC-dc5100) via xl0 
Sep 28 14:35:03 dhcpd: DHCPDISCOVER from 00:12:79:ad:c6:fc via xl0  
Sep 28 14:34:51 dhcpd: DHCPRELEASE of 192.168.2.254 from 00:12:79:ad:c6:fc via 
fxp0 (found) 
Sep 28 14:34:51 dhcpd: DHCPRELEASE of 192.168.2.254 from 00:12:79:ad:c6:fc 
(TRC-dc5100) via xl0 (found) 
Sep 28 14:34:49 dhcpd: send_packet: Invalid argument
Sep 28 14:34:49 dhcpd: DHCPACK on 192.168.2.254 to 00:12:79:ad:c6:fc 
(TRC-dc5100) via fxp0  
Sep 28 14:34:49 dhcpd: DHCPREQUEST for 192.168.2.254 from 00:12:79:ad:c6:fc 
(TRC-dc5100) via fxp0   
Sep 28 14:34:49 dhcpd: send_packet: Invalid argument
##
My two lan inrefaces are as below:
interfaces
lan
iffxp0/if
ipaddr192.168.0.3/ipaddr
subnet24/subnet
media/
mediaopt/
bridge/
bandwidth100/bandwidth
bandwidthtypeMb/bandwidthtype
/lan
opt2
descrLAN2/descr
ifxl0/if
bridge/
enable/
bandwidth100/bandwidth
bandwidthtypeMb/bandwidthtype
ipaddr192.168.2.4/ipaddr
subnet24/subnet
gateway/
spoofmac/
mtu/
/opt2
/interfaces

and dhcp servers :
dhcpd
lan
range
from192.168.0.250/from
to192.168.0.250/to
/range
defaultleasetime/
maxleasetime/
denyunknown/
failover_peerip/
gateway/
staticmap
mac00:14:c2:0b:95:49/mac
ipaddr192.168.0.21/ipaddr
descrlvc-felsorec/descr
/staticmap
staticmap
mac00:08:02:d8:1f:eb/mac
ipaddr192.168.0.130/ipaddr
descrI.I. nc6000/descr
/staticmap
staticmap
mac00:12:79:ad:c6:fc/mac
ipaddr192.168.0.22/ipaddr
descrdc5100 teszt/descr
/staticmap
staticarp/
enable/
dnsserver192.168.1.5/dnsserver
dnsserver192.168.1.1/dnsserver
/lan
opt2
range
from192.168.2.254/from
to192.168.2.254/to
/range
defaultleasetime/
maxleasetime/
failover_peerip/
gateway/
staticmap
mac00:08:02:d8:ae:23/mac
ipaddr192.168.2.130/ipaddr
descrKris nc6000/descr
/staticmap
staticarp/
denyunknown/
enable/
dnsserver192.168.3.3/dnsserver
dnsserver192.168.3.1/dnsserver
/opt2
/dhcpd


-- 
This email is made from 100% recycled electrons


Re: [pfSense Support] unexpected dhcp lease

2005-09-28 Thread Bill Marquette
Are these two logical networks on the same physical network?  I'm
noticing the request came in on both fxp0 and xl0 - that seems kinda
odd.

Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4)
from 00:12:79:ad:c6:fc (TRC-dc5100) via fxp0: wrong network.
Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4)
from 00:12:79:ad:c6:fc (TRC-dc5100) via xl0

--Bill

On 9/28/05, Imre Ispanovits [EMAIL PROTECTED] wrote:
 Hi,

 I have a problem with pfSense's dhcp server since 0.85.x (I guess it wasn't 
 an issue in 0.84.6).
 I have two lan interfaces and  both serves as dhcp server, of course not 
 overlapping.
 My problem is that on lan2 (opt2 - xl0) a dynamic ip address is always issued 
 despite it
 shouldn't be because only fixed leases expected. This is the only address I 
 have to
 configure for the dhcp servers range. What's more strange for that mac 
 address (00:12:79:ad:c6:fc)
 is a fixed lease reserved on the other (fxp0) interface. Which as I see in 
 the logs once offered,
 but the other address picked up.
 This never happened on the other interface.

  In syslog I have:
 
 Sep 28 14:35:04 last message repeated 2 times
 Sep 28 14:35:03 kernel: arp: 192.168.2.254 is on xl0 but got reply from 
 00:12:79:ad:c6:fc on fxp0
 Sep 28 14:34:49 last message repeated 5 times
 Sep 28 14:34:36 dhcpd: send_packet: Invalid argument
 
 and in dhcp logs:
 
 Sep 28 14:35:03 dhcpd: DHCPNAK on 192.168.2.254 to 00:12:79:ad:c6:fc via fxp0
 Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4) from 
 00:12:79:ad:c6:fc (TRC-dc5100) via fxp0: wrong network.
 Sep 28 14:35:03 dhcpd: DHCPACK on 192.168.2.254 to 00:12:79:ad:c6:fc 
 (TRC-dc5100) via xl0
 Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4) from 
 00:12:79:ad:c6:fc (TRC-dc5100) via xl0
 Sep 28 14:35:03 dhcpd: DHCPOFFER on 192.168.0.22 to 00:12:79:ad:c6:fc via fxp0
 Sep 28 14:35:03 dhcpd: DHCPDISCOVER from 00:12:79:ad:c6:fc via fxp0
 Sep 28 14:35:03 dhcpd: DHCPOFFER on 192.168.2.254 to 00:12:79:ad:c6:fc 
 (TRC-dc5100) via xl0
 Sep 28 14:35:03 dhcpd: DHCPDISCOVER from 00:12:79:ad:c6:fc via xl0
 Sep 28 14:34:51 dhcpd: DHCPRELEASE of 192.168.2.254 from 00:12:79:ad:c6:fc 
 via fxp0 (found)
 Sep 28 14:34:51 dhcpd: DHCPRELEASE of 192.168.2.254 from 00:12:79:ad:c6:fc 
 (TRC-dc5100) via xl0 (found)
 Sep 28 14:34:49 dhcpd: send_packet: Invalid argument
 Sep 28 14:34:49 dhcpd: DHCPACK on 192.168.2.254 to 00:12:79:ad:c6:fc 
 (TRC-dc5100) via fxp0
 Sep 28 14:34:49 dhcpd: DHCPREQUEST for 192.168.2.254 from 00:12:79:ad:c6:fc 
 (TRC-dc5100) via fxp0
 Sep 28 14:34:49 dhcpd: send_packet: Invalid argument
 ##
 My two lan inrefaces are as below:
 interfaces
 lan
 iffxp0/if
 ipaddr192.168.0.3/ipaddr
 subnet24/subnet
 media/
 mediaopt/
 bridge/
 bandwidth100/bandwidth
 bandwidthtypeMb/bandwidthtype
 /lan
 opt2
 descrLAN2/descr
 ifxl0/if
 bridge/
 enable/
 bandwidth100/bandwidth
 bandwidthtypeMb/bandwidthtype
 ipaddr192.168.2.4/ipaddr
 subnet24/subnet
 gateway/
 spoofmac/
 mtu/
 /opt2
 /interfaces

 and dhcp servers :
 dhcpd
 lan
 range
 from192.168.0.250/from
 to192.168.0.250/to
 /range
 defaultleasetime/
 maxleasetime/
 denyunknown/
 failover_peerip/
 gateway/
 staticmap
 mac00:14:c2:0b:95:49/mac
 ipaddr192.168.0.21/ipaddr
 descrlvc-felsorec/descr
 /staticmap
 staticmap
 mac00:08:02:d8:1f:eb/mac
 ipaddr192.168.0.130/ipaddr
 descrI.I. nc6000/descr
 /staticmap
 staticmap
 mac00:12:79:ad:c6:fc/mac
 ipaddr192.168.0.22/ipaddr
 descrdc5100 teszt/descr
 /staticmap
 staticarp/
 enable/
 dnsserver192.168.1.5/dnsserver
 dnsserver192.168.1.1/dnsserver
 /lan
 opt2
 range
 from192.168.2.254/from
 to192.168.2.254/to
 /range
 defaultleasetime/
 maxleasetime/
 failover_peerip/
 

Re: [pfSense Support] unexpected dhcp lease

2005-09-28 Thread Imre Ispanovits

On Wed, 28 Sep 2005 08:26:28 -0500
Bill Marquette [EMAIL PROTECTED] wrote:

 Are these two logical networks on the same physical network?  I'm
 noticing the request came in on both fxp0 and xl0 - that seems kinda
 odd.
Yes, both network cards are connected to the same switch, but I guess as the
deny unknown clients option is enabled on both interfaces (static arp as 
well) this shouldn't happen.
(Not to mention the netmasks.)
 
 Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4)
 from 00:12:79:ad:c6:fc (TRC-dc5100) via fxp0: wrong network.
 Sep 28 14:35:03 dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.4)
 from 00:12:79:ad:c6:fc (TRC-dc5100) via xl0
 
 --Bill
 

-- 
This email is made from 100% recycled electrons

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]