[kwlug-disc] IP addresses and gateways--my google-fu seems to be lacking
unsolicited at swiz.ca
Sat Jan 18 00:34:33 EST 2014
OK, with WRT if you can get it's wifi to be a client of the other, then
you can forget the firewall distros, iptables, every other bit of
complexity, and return the netbook to it's normal client networking mode.
Bridge the WRT wi-fi and local lan. Plug all computers into lan ports.
Use DHCP for everything, or set static 192.168.1.x addresses and
192.168.1.1 (I presume the downstairs router) as the gateway, and you
should be good to go.
The only trick may be to make this wrt wi-fi a client of downstairs, but
I've found the wrt wiki site to be pretty good at documenting things.
Start with just the wrt. When you've got things how you think they
should be, just ssh in to the wrt and do a few pings - to an upstairs
computer, a downstairs one, the gateway itself, and 18.104.22.168 or other
favourite place on the internet.
One thing to watch for / change your expectations for, maybe - if you do
any VoIP, your latency to downstairs will likely be higher. You may have
some degraded performance from your past experience with the powerline
stuff. (I've not used powerline stuff to know how good/bad it is vis a
On 14-01-17 06:55 PM, R. Brent Clements wrote:
> So I was able to boot a firewall distro on the netbook, and configure
> a Linksys WRT54GL that I had laying around that already had Openwrt
> kamikaze on it, and also the netbook's Crunchbang linux to the same
> point, then I am stuck. I was able to get the router device talking
> on both networks in every case. For the record, the gui network
> configuration has a switch on the "routes" page that tells the os to
> only use that interface for destinations on its own subnet, and if you
> select that on all but one you can still access the internet on
> whichever one is left.
> Still trying to get any one of them to actually route packets from one
> interface to the next tho :-( I guess I need to spend some time
> actually learning iptables
> On Thu, Jan 16, 2014 at 6:12 PM, Khalid Baheyeldin <kb at 2bits.com> wrote:
>> On Thu, Jan 16, 2014 at 5:37 PM, Bob Jonkman <bjonkman at sobac.com> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> Brent wrote:
>>>> It seems like internet traffic is refusing to use the wireless link
>>>> when the wired one is connected, even tho there is no route to the
>>> There's a BIOS setting on my laptop that automatically disconnects the
>>> WiFi whenever I plug in a LAN cable. As far as Network Manager is concerned,
>>> I no longer have any WiFi radio hardware (or maybe it thinks I've switched
>>> it off with the button above the keyboard, I don't recall).
>>> I also don't recall what the wording of that setting is, but I can
>>> (and did) disable it. I'm loath to shutdown and poke at my BIOS just now
>>> to refresh my memory. Sorry.
>> Or ...
>> If your laptop has a little on-off switch for WiFi, then switch it off, then
>> connect the LAN cable.
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
More information about the kwlug-disc