From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] printer problem, netmask & renumbering....
Date: Thu, 29 Mar 2012 13:11:43 -0400 [thread overview]
Message-ID: <4F7497CF.5010301@freedesktop.org> (raw)
My problems with my printers might be related to netmask problems.
We ended up putting the wireless into 192.168.1 this time.
This is a problematic renumbering if the goal is to preserve a
192.168.1.x to be existing, probably hard wired ethernet.
It's probably the case we should only renumber the one network, leaving
the netmask alone, leaving all the wireless network addresses alone.
I'll try a netmask change to see if that makes the printer work before
updating its firmware.
But not for a while; I forgot I had an eye appointment today and trying
to do this while my eyes are recovering from dilation is not my idea of fun.
- Jim
reply other threads:[~2012-03-29 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7497CF.5010301@freedesktop.org \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox