On Friday 17 January 2003 11:37, Brock Nanson wrote:
The correct solution is to specify the 'dhcp' in
/etc/shorewall/interfaces
for the interface(s) being served by dhcpd.
I haven't done this. I'll try it. So far, it seems to be doing its thing.
It's gone for 10 minutes without logging
--On Thursday, January 16, 2003 4:52 PM -0800 Brock Nanson
[EMAIL PROTECTED] wrote:
Googling suggested that this was a firewall issue
so I played about with that for a while - finally got it to stop by
adjusting the Shorewall rules to ACCEPT UDP 67 and 68
between the Bering
box and
--On Friday, January 17, 2003 8:37 AM -0800 Brock Nanson
[EMAIL PROTECTED] wrote:
--On Thursday, January 16, 2003 4:52 PM -0800 Brock Nanson
[EMAIL PROTECTED] wrote:
Googling suggested that this was a firewall issue
so I played about with that for a while - finally got it to stop by
Hi Tom,
You asked what version I'm running... Not too sure - I don't have access
to the box at the moment. However, the snippet you included in your
message to the list jogged my memory. I was working on doing something
along the lines of WISP-Dist for a local group a year or so ago and was
--On Friday, January 17, 2003 01:31:45 PM -0800 Brock Nanson
[EMAIL PROTECTED] wrote:
The good news is I solved the problem! ;-) But I still don't know how
I was able to get the lease in the first place!
I don't know either -- sometime when I'm bored, I'll look into it since
I've seen
Hello,
I get a LOT of the following in my syslog:
Jan 16 23:27:38 firewall dhcpd: DHCPREQUEST for 192.168.1.2
from=20 00:80:c6:f8:62:c6 via eth1 Jan 16 23:27:38 firewall
dhcpd: DHCPACK on 192.168.1.2 to 00:80:c6:f8:62:c6= =20 via
eth1 Jan 16 23:27:38 firewall dhcpd: send_packet:
--On Thursday, January 16, 2003 4:52 PM -0800 Brock Nanson
[EMAIL PROTECTED] wrote:
Googling suggested that this was a firewall issue
so I played about with that for a while - finally got it to stop by
adjusting the Shorewall rules to ACCEPT UDP 67 and 68 between the Bering
box and my LAN.
--On Thursday, January 16, 2003 7:12 PM -0800 Tom Eastep
[EMAIL PROTECTED] wrote:
The correct solution is to specify the 'dhcp' in
/etc/shorewall/interfaces for the interface(s) being served by dhcpd.
I of course meant the 'dhcp' option
--
-Tom
--
Tom
