I found out where my dhcp offers are going. It seems my dhcp offers are being
sent out my external port instead of my internal port.
Anyone ever have a problem where the internal port is setup as a server and for
some reason natd kicked in and sent the data out using the external ip?
Thanks,
On Sunday 02 September 2007 03:13:21 Joe wrote:
Gosh, I suddenly remember why I dropped yahoo webmail
Ok, no so true. I am watching tcpdump output from the two binaries. The
old binary sends its reply to 255.255.255.255, while the new one sends its
reply to 192.168.0.15. Same config
For some reason they are no longer showing up in tcpdump?
I can see the DHCP discover and the DHCP offers, but can't get tcpdump to
output them?
DHCPDISCOVER from AA:AA:AA:AA:AA:AA via xl0
DHCPOFFER on 192.168.0.13 to AA:AA:AA:AA:AA:AA (w2k-box) via xl0
This happens 4 times, but I can get
Hello, after running tcpdump for a while I discoverd what is going on with my
dhcpd server and why some clients are not able to get an IP address from it, in
particular windows clients. It turns out it is not just win2k but any windows.
It seems that the dhcpd server is replying to the subnet
Joe wrote:
Hello, after running tcpdump for a while I discoverd what is going on with my
dhcpd server and why some clients are not able to get an IP address from it,
in particular windows clients. It turns out it is not just win2k but any
windows.
It seems that the dhcpd server is
On Saturday 01 September 2007 23:30:27 Peter Boosten wrote:
Joe wrote:
Hello, after running tcpdump for a while I discoverd what is going on
with my dhcpd server and why some clients are not able to get an IP
address from it, in particular windows clients. It turns out it is not
just
I'd say thanks for the help, but telling someone that 'it works for me' is not
helpful.
I upgraded to 6.2p7 from 6.2p6 and this problem started happening, but only
with dhcpd.
In fact I can run the old dhcpd fine, but the new binary deos not run fine.
The old binary does a dhcp reply from
isc-dhcp3-server issues with windows 2000 client)
To: freebsd-questions@freebsd.org
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=0-1649509927-1188695601=:80192
Content-Transfer-Encoding: 8bit
Message-ID: [EMAIL PROTECTED]
