[PLUG] Re: Linux 7.2 Printer Problem Solved

[Rick Konold]

I don't know why that did not work, one of my Linux boxes is 192.168.0.011.  
The .001 is usually reserved by convention for a server (?), but no reason 
why you could not use it.  I used it once for a Linux ws and it worked fine.
Rick Konold
Linux Advocate

On Wednesday 20 March 2002 19:42, you hammered the keyboard to write:
> So far so good. Everything changed over to addresses in the 192 range.
>
> I changed the HP Printer JetDirect Card to 192.168.200.200 with no problem.
> I changed a Windows 98 computer to 192.168.200.006 with no visible problem.
> Then I changed the Red Hat 7.2 computer to 192.168.200.081 and upon reboot
> it said the IP address was invalid.  I then changed it to 192.168.200.181
> and it seemed to work fine.
>
> Now my questions:  Is an IP address ending in .081, or .001 for that matter
> invalid?
>
> Does it need a number other than 0 (zero) as the first number in order to
> work?
>
> The Windows 98 computer seems to work fine, but I don't know if something
> down the road will stop working if this is an invalid address.  None of my
> books discuss this detail.
>
> Thanks
> Robert
>
> Jeme A Brelin wrote:
> > On Tue, 19 Mar 2002, Robert wrote:
> >> Now another question.  In Red Hat Linux for Dummies, Jon "maddog" Hall
> >> suggests giving the computer an IP address of 192.168.1.1 to
> >> 192.168.254.254.
> >>
> >> When I do this I loose access to my HP JetDirect card webpage (on the HP
> >> 4050 network printer). I use the Konqueror web browser to access it.
> >>
> >> The JetDirect IP is 169.254.164.209
> >>
> >> If I set the computers IP address to a 169 number it sees it fine, so
> >> that's what it is now.
> >>
> >> Is using a 169 number instead of a 192 a mistake?
> >
> > There are three "private" IP blocks set aside from the publicly routable
> > internet blocks:
> > 10.0.0.0/8
> > 172.16.0.0/12
> > 192.168.0.0/16
> >
> > (See RFC 1918 <URL: http://www.isi.edu/in-notes/rfc1918.txt > )
> >
> > If your network uses a subnet in one of the above blocks, it will not be
> > routable directly on the internet.
> >
> > Most people that use this private address space that want to communicate
> > with the wide internet do so via a process called Network Address
> > Translation.  This process requires a gateway host with access to both
> > the internet and the private network to pass all traffic between the two
> > networks, translating the private addresses to public ones.  This is
> > mostly useful because a large number of computers on a private network
> > can share one globally routable IP address.  It also helps prevent
> > unwanted inbound traffic because the machines inside the private network
> > are not directly addressable from outside without an appropriate
> > translation entry on the gateway machine.
> >
> > Now, there is also this range:
> > 169.254.0.0/16
> >
> > I'm a little fuzzier on this, but I'll give an explanation a shot.
> >
> > This is the "link-local" address range.  Essentially, if a machine is
> > supposed to get an IP address dynamically (from a DHCP server or
> > something) and can't, it's supposed to assume one of these addresses and
> > continue to function, though not participating on the network
> > (presumably, since there are no other local machines on that network). 
> > Using this address space for a local network is a recipe for disaster.
> >
> > Your JetDirect card was configured with this address as a sort of
> > sample/random address and should be reconfigured with an address that is
> > actually used on your local network.
> >
> > Depending on how your connectivity with the outside world works, you have
> > a few options.
> >
> > Here's my Best Suggestion for a home network with a permanent internet
> > connection of some kind (DSL, Cable, Frame, ISDN, etc.):
> >
> > Build a local network using one of the private address spaces set aside
> > by RFC 1918, renumbering existing systems as necessary.  (In order to
> > renumber my network printer, I had to run a special diagnostic mode on
> > the printer and get a printout of the MAC address for the network card,
> > set an entry in the arp table of one of my computers with the desired
> > address, then simply ping the address.  The printer's network card
> > understood that the address to which the ping packet was destined should
> > be its IP address.  Seems like a very foolish system if anyone on the
> > network can change the printer's IP at will, but I didn't design the
> > thing.)
> >
> > Acquire a gateway/firewall device to bridge the local network and the
> > greater internet.
> >
> > Configure this device with one interface on the internet via your remote
> > network bridge device (DSL bridge, cable modem, etc.) and another
> > interface on your local, private network.
> >
> > Configure Network Address Translation between the two interfaces.
> >
> > Set the internal interface on the firewall as the Default Gateway on each
> > host on the private network that needs to reach the internet.  Set your
> > ISP's default gateway as the default on the firewall machine.
> >
> > If you need further help, ask here or show up at a plug meeting and get
> > ready to talk notes and draw diagrams.
> >
> > J.
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug