On Sun, Sep 27, 2026 at 11:03:12PM -0400, Ed Heil wrote:
> I also tried removing "inet autoconf" from the /etc/hostname.iwm0 file, and 
> replacing it with:
> 
> inet 10.0.0.179 255.255.255.0 NONE
> 
> I just arbitrarily picked 179 because it's higher than the most recently 
> handed out address I know of, 174.  

You generally can't just set a static IP and expect it to work.  The router is
not expecting this, and could easily filter out the packets that don't match
the MAC address that it associated with that IP, (if any).

When dhcp and static allocation are both used on a lan, the usual approach is
to allocate a small subnet of addresses for dynamic allocation and leave the
rest for static.  The router is configured for this and knows about it.

But this seems pointless in your setup, (and the router might not even expose
a control to do it), because the correct solution is to fix the dhcp problem.

> This makes "ifconfig" think I have that address, but I when I try to "ping"
> the router or a linux box on my network, which I happen to know the IP of, I
> get "sendmsg: Host is down".  However, if I use tcpdump, I still see a lot
> of chatter from random devices on my network (including the linux box I was
> unable to successfully ping or ssh to).

This is because tcpdump runs the device in promiscuous mode, so you'll see all
traffic even without an IP configured.

Reply via email to