Hello, On Fri, 1 Feb 2008, Jim M wrote:
Sorry I wasn't clear. What my mind was thinking wasn't coming across. I hope this helps. I have a firewall that runs on a Sun Ultra 5. It is a dhcp client on the WAN side and a dhcp server inside the house. The firewall connects to a switch that has several things connected to it including other computers (running various operating systems), switches that service other parts of the house and a Linksys wireless G access point. I have a company HP laptop that runs Windows XP. The laptop has a built in 802.11 capability and a PCMCIA card. The card works fine, but the built in will get through the WAP fine, but won't get an IP address from the firewall. Is there some log file where I can look for error messages to try to troubleshoot this. Thanks again, and I hope this helps explain things. -------- Original Message -------- Subject: Re: dhcp error message From: Joachim Schipper <[EMAIL PROTECTED]> Date: Fri, February 01, 2008 8:46 am To: Jim M <[EMAIL PROTECTED]> On Thu, Jan 31, 2008 at 07:38:26PM -0700, Jim M wrote: > my /var/log/messages file is filled over and over with the line > (obviously the date/time varies) > > Jan 31 20:17:00 balrog dhclient: send_fallback: No route to host > > The machine is a firewall and has no graphic capabilities. It is a dhcp > client to get my the IP address for the home network and a dhcp server > for all the machines in the house. What does this error message mean? > The firewall works fine as the default router for all the wired Ethernet > machines in the house. But, I have laptop with built in 802.11 and a > PCMCIA card as well. When I use the PCMCIA card, everything works fine. > With the built in 802.11, however, it connects to the WAP, but does not > get an IP address from the firewall. I can't figure out why the > difference and would appreciate any advice on how to troubleshoot this. I'm not certain this is useful, but that *is* the message you get if pf blocks a packet. However, dhclient does some unusual stuff to be able to send packets even when the interface is down, and usually bypasses pf because of that. Otherwise, it's not really clear to me which host is which and which host is doing what, so I'm afraid I can't really help you. A little clarification sent to the list might be useful here. Joachim
that is a classic: dhcp uses UDP broadcasts which usually are not forwarded, your AP is not your dhcp-server and so the dhcp request will reach the AP but not your firewall.
Three solutions: dhcp relay agent on your AP (if possible) or configure your AP to forward broadcasts or use a dhcp server on your AP with a different IP range.
Try any search machine with "dhcp relay" and you will find answers. Regards Stefan Kell
