On Tuesday, 14 September 2021 9:18:36 AM ACST Douglas McGarrett wrote:
On 9/13/21 7:32 PM, Douglas McGarrett wrote:
/snip/
ip addr add 192.168.1.199/24 dev eth0
Then point your firefox to the address of the printer that was printed in the status page:
You should reach a setup web page of the printer itself (I'm guessing it has one) and in there you can probably change the printer address to be 192.161.0.10, for instance, in a manner easier than the printer panel.
The setup page you printed should say if this local web page exists. It would be on port 80. If it exists but is disabled, you should be able to enable it in the panel.
OK! I did what you suggested, and moved the "1" in the ip to "0" and reset it in YAST and by golly it prints! I'm having a little trouble with the HP-- I set it up in YAST and it printed a test page OK, but then I tried to print from an app and it didn't, and it is "paused"--for whatever reason I don't know. Maybe I'm getting there. . . . --doug
Just added the HP to the static ip configuration, rediddled YAST and it seems to be working the way it should now. I HOPE I have put the printer problem to bed at long last, and this should close the thread. Thanx again to all who participated in this long-running tale of woe! --doug Doug, here's a tip to file away: In the IP address configuration of any network-connected device, there are 3 key parameters:
IP Address Netmask Default Gateway. The IP address is what you've been looking at with your printer -for IP version 4 it is expressed as a "dotted quad" of 4x 8bit decimal numbers for a total of 32 bits, each octet ranging from 0 to 255 e.g. 192.168.0.100 as you've seen on your LAN. The Netmask tells each network device 2 key pieces of information: what portion of that IP address represents the NETWORK, and what portion represents the HOST (a "network-connected device"). The netmask looks like "255.255.255.0", or "255.255.0.0", or other combinations (I won't get into more complex netmasks here"). In the case of 255.255.255.0 (in binary notation that would be 11111111.11111111.11111111.00000000), the first 3 octets (everywhere that the bits are all 1's) represent the NETWORK portion of the address, and the last octet (or everywhere there are zeros) represents the HOST portion of the network address. Computers on a LAN can talk directly to other computers where the NETWORK portion of the address matches - if the netmask is 255.255.255.0, that means the first 3 octets of the address must match; if it is 255.255.0.0, only the first 2 need to match. In case 1, there are a maximum of 254 host addresses possible (.1 to .254, .0 is the "network address" and .255 is the broadcast address i.e. ALL HOSTS get packets addressed to .255), and in case 2 there are 255*254 hosts available (host addresses are x.x.0.1 to x.x.255.254). The default gateway address is the router address - if the devices are trying to talk to an IP address that does NOT have matching octets in the positions specified by the netmask, they will forward that traffic to the default gateway address, in the hope that the router will know how to deliver it (if not directly, it will forward it to the next upstream router that it knows about, as long as it has a default-gateway configured for itself - that will be an address on your ISP's router. IP addressing is analogous to sending a letter through the mail - as long as the letter is correctly addressed, you only have to get it to your local mailbox (the "ethernet port", which gets it to the local post-office (the "router"), which sends it onto the mail processing facility (the upstream router in "the cloud"...penultimately it gets delivered to a local post office at the far end, and then to the final destination. That's basically how networking functions, only with bits and bytes on "the wire". It gets a whole lot more complicated than that, but if you can follow that for now you'll be a lot further ahead than you were when this saga started. Regards, -- ================================================================================================================== Rodney Baker rodney.baker@iinet.net.au ==================================================================================================================