[conspire] corrected to HP LaserJet4M Plus Re: HP LaserJet4 - CUPS lists printer twice

Ruben Safir ruben at mrbrklyn.com
Tue Aug 25 13:20:13 PDT 2009

Too many words.   If it routes it is a router...

On Tue, Aug 25, 2009 at 01:18:02PM -0700, Rick Moen wrote:
> Just to elaborate on one of the other things I wrote:
> > Quoting Darlene Wallach (freepalestin at dslextreme.com):
> > 
> >> I spoke briefly with Daniel on Saturday. He reminded me I don't have
> >> a router and therefore no way to get an ip for the printer.
> > 
> > Eh?  There's no connection between routers and "getting an IP".  It's
> > possible that what Daniel is thinking about, however, is DHCP leases.
> What casual computer users commonly call a "router" these days is
> something like a Netgear or Linksys residential-gateway device, intended
> to connect a home or small office to broadband or other uplink
> connections, e.g., the famously hackable Linksys WRT54G and successors
> (http://en.wikipedia.org/wiki/Linksys_WRT54G_series).
> As an example of such devices, the WRT54G fulfills several separate
> functions:
> o  It's a four-port ethernet switch, plus fifth port for uplink.
> o  It's a wireless gateway (802.11b/g).
> o  It offers private IPs on the internal four ports, with NATed
>    service routed to a public IP (on a different network) assigned to the 
>    single uplink port -- in which sense, it's a router.
> o  It offers IP/port filtering on traffic NATed and routed to/from the 
>    uplink port (so-called "firewalling").
> o  It offers DHCP leases to the four inside ethernet ports and 
>    wireless network -- in which sense, it's a DHCP server.
> Now, one of the things I keep forgetting is how much computer users,
> these days, tend to take DHCP for granted.  People nowadays plug
> computers into wired networks (or connect to wireless ones) and just
> assume a DHCP daemon somewhere will automagically provide a suitable IP
> address, netmask, gateway IP, set of DNS IP addresses, and maybe even
> hostname and other useful information -- without the user getting
> involved at all.  That's indeed usually the case, and (usually) pretty
> useful.
> My impression, from your posts, is that you have an old-fashioned setup
> of one or more computer with static IP assignments (probably RFC1918
> private IPs) configured into them, and an ethernet hub.  Thus, no DHCP
> daemon anywhere.  (If you had reason to establish one, you could run the
> ISC DHCP daemon on your Linux machine -- but I doubt you need it.)
> That's actually a perfectly fine and satisfactory arrangement, is
> how most people did TCP/IP in most places for a long time, and is
> _still_ the obvious way to do things for any host (including a printer)
> that's intended to provide network services to other machines.  It
> remains my personal preference and habit.
> Once configured, a machine's static IP setup _stays_ configured.  It's
> simple, reliable, and there's essentially nothing to go wrong.
> _______________________________________________
> conspire mailing list
> conspire at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/conspire

http://www.mrbrklyn.com - Interesting Stuff
http://www.nylxs.com - Leadership Development in Free Software

So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world  - RI Safir 1998

http://fairuse.nylxs.com  DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002

"Yeah - I write Free Software...so SUE ME"

"The tremendous problem we face is that we are becoming sharecroppers to our own cultural heritage -- we need the ability to participate in our own society."

"> I'm an engineer. I choose the best tool for the job, politics be damned.<
You must be a stupid engineer then, because politcs and technology have been attached at the hip since the 1st dynasty in Ancient Egypt.  I guess you missed that one."

© Copyright for the Digital Millennium

More information about the conspire mailing list