Re: Mixing and Matching DHCP and static IPs
On Tue, Dec 26, 2017 at 02:31:05PM -0000, Dan Purgert wrote:
> >> No, the airstation having been given an address 192.168.1.x/24 will know
> >> that it can directly reach any host 192.168.1.1 through 192.168.1.254
> >> inclusive.
> >>
> >
> > Except for some reason it doesn't seem to (or, rather, that is what
> > APPEARS to be the case but without answering some of Pascal's earlier
> > questions I can't say for certain that is what is going on). We know
> > that 1.1 c an reach 1.3, but 11.anything doesn't seem to be able to,
> > even though they can reach 1.1 . I just don.t know why yet.
>
> Again, this points to the idea that perhaps the Airstation has a
> firewall preventing access to "bogus" networks. I assume that the
> Airstation does not have any capabilities to run ping / traceroute tests
> from somewhere in its administration menus?
>
> If it DOES allow that, it may be helpful to try pinging directly from
> the airstation.
I don't think I'm gonna have much luck with that. The Web interface is
fairly bog standard -- and what is there is in Japanese, which doesn't
help... I can read Japanese, but slowly, with errors... With all that
said, I have spent enough time squinting at that interface to be fairly
sure it doesn't offer that functionality.
>
> Also, since I probably missed it, what is the "firewall" device that's
> handing out the 1.0/24 network (make and model please)?
>
Yeah that was in the TLDR original post. It's a mini-ITX PC running LFS.
It came with Windows 10, and I ripped it out of Windows' evil clutches
and installed LFS on it. Before bringing the PI into the picture, this
box had been acting as my firewall, DHCP server for the AirStation, and
occasional VPN server for me for about a year with no problems.
Mark
Reply to: