On 12/09/2021 00.40, Douglas McGarrett wrote:
On 9/12/2021 12:08 AM, Carlos E. R. wrote:
On 11/09/2021 22.14, Douglas McGarrett wrote:
To find a networked hp printer, you probably want to do:
nmap -p 9100 -n 192.168.1.*
ran that in Windows, but got no answers:
C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.1.* Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 20:57 GMT Summer Time Nmap done: 256 IP addresses (0 hosts up) scanned in 208.53 seconds
Then tried with the third entry set to 0 and got this:
C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.0.* Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 23:34 GMT Summer Time Nmap scan report for 192.168.0.1 Host is up (0.0029s latency).
PORT STATE SERVICE 9100/tcp closed jetdirect MAC Address: 1C:AF:F7:DD:AE:FF (D-Link International)
That's the router.
Nmap scan report for 192.168.0.102 Host is up (0.0020s latency).
PORT STATE SERVICE 9100/tcp filtered jetdirect MAC Address: F0:4D:A2:0F:81:CF (Dell)
Nmap scan report for 192.168.0.103 Host is up (0.0029s latency).
PORT STATE SERVICE 9100/tcp open jetdirect MAC Address: 48:0F:CF:C3:33:B7 (Hewlett Packard)
The HP printer, probably.
Nmap scan report for 192.168.0.104 Host is up (0.0023s latency).
PORT STATE SERVICE 9100/tcp closed jetdirect MAC Address: 00:26:B9:D4:42:2D (Dell)
Nmap scan report for 192.168.0.100 Host is up (0.00s latency).
I am not familiar with the value of the third number in the ips. I seem to remember that 5 or 6 years ago, all my ips had a 1 in the third position; now they all seem to want a 0.
Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance.
Anyway, not discovering the Epson printer ip, if any.
Well, I told you the trick for HPs, not Epson. I don't know what port the Epson uses. Google "what port uses an epson printer" <https://epson.com/faq/SPT_C11CD16201~faq-0000525-shared?faq_cat=faq-8796127635532> ok, try: nmap -p 3289,515,9100,631 -n 192.168.0.* -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/12/21 6:24 AM, Carlos E. R. wrote:
On 12/09/2021 00.40, Douglas McGarrett wrote:
On 9/12/2021 12:08 AM, Carlos E. R. wrote:
On 11/09/2021 22.14, Douglas McGarrett wrote:
To find a networked hp printer, you probably want to do:
nmap -p 9100 -n 192.168.1.* ran that in Windows, but got no answers:
C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.1.* Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 20:57 GMT Summer Time Nmap done: 256 IP addresses (0 hosts up) scanned in 208.53 seconds
Then tried with the third entry set to 0 and got this:
C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.0.* Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 23:34 GMT Summer Time Nmap scan report for 192.168.0.1 Host is up (0.0029s latency).
PORT STATE SERVICE 9100/tcp closed jetdirect MAC Address: 1C:AF:F7:DD:AE:FF (D-Link International) That's the router.
Nmap scan report for 192.168.0.102 Host is up (0.0020s latency).
PORT STATE SERVICE 9100/tcp filtered jetdirect MAC Address: F0:4D:A2:0F:81:CF (Dell)
Nmap scan report for 192.168.0.103 Host is up (0.0029s latency).
PORT STATE SERVICE 9100/tcp open jetdirect MAC Address: 48:0F:CF:C3:33:B7 (Hewlett Packard) The HP printer, probably.
Nmap scan report for 192.168.0.104 Host is up (0.0023s latency).
PORT STATE SERVICE 9100/tcp closed jetdirect MAC Address: 00:26:B9:D4:42:2D (Dell)
Nmap scan report for 192.168.0.100 Host is up (0.00s latency).
I am not familiar with the value of the third number in the ips. I seem to remember that 5 or 6 years ago, all my ips had a 1 in the third position; now they all seem to want a 0.
Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance.
Anyway, not discovering the Epson printer ip, if any. Well, I told you the trick for HPs, not Epson. I don't know what port the Epson uses.
Google "what port uses an epson printer"
<https://epson.com/faq/SPT_C11CD16201~faq-0000525-shared?faq_cat=faq-8796127635532>
ok, try:
nmap -p 3289,515,9100,631 -n 192.168.0.*
I found in the printer manual, a way to get a status sheet from the printer's control panel. It shows that the original static ip address that was set back around 2016 is still in effect. I suspect that whatever is supposed to decode that from a ping has been blown out, since it does not respond to a ping at that ip. Now I mentioned earlier that the third number in the ip addresses on my network now is 0, where it used to be 1, and one of the correspondents here suggested that this is router dependent. Will the router not interrogate an address with a 1 in the third position? (The old router was destroyed in the lightning strike--I can't put it back and try it!) It seems that there are unknown failures in the printer, in addition to the one already found--the FAX line is zapped. comments? --doug
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2021-09-12 a las 15:19 -0400, Douglas McGarrett escribió:
On 9/12/21 6:24 AM, Carlos E. R. wrote:
On 12/09/2021 00.40, Douglas McGarrett wrote:
I am not familiar with the value of the third number in the ips. I seem to remember that 5 or 6 years ago, all my ips had a 1 in the third position; now they all seem to want a 0.
Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance.
...
I found in the printer manual, a way to get a status sheet from the printer's control panel. It shows that the original static ip address that was set back around 2016 is still in effect. I suspect that whatever is supposed to decode that from a ping has been blown out, since it does not respond to a ping at that ip. Now I mentioned earlier that the third number in the ip addresses on my network now is 0, where it used to be 1, and one of the correspondents here suggested that this is router dependent. Will the router not interrogate an address with a 1 in the third position? (The old router was destroyed in the lightning strike--I can't put it back and try it!) It seems that there are unknown failures in the printer, in addition to the one already found--the FAX line is zapped. comments?
Tell what that IP in the printed paper is. That information is important and you hide it from us. If it is not 192.168.0.something, the printer will not respond to pings and you have to reconfigure it using its panel. - -- Cheers Carlos E. R. (from openSUSE 15.2 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYT5p7Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVSO0An1H2JRgvj4A9zU40Jjs7 jmvvHRmpAJ9XnEsV/C+LAb/AZufBeQ5MJ7gUqA== =FR7j -----END PGP SIGNATURE-----
On 9/12/21 4:58 PM, Carlos E. R. wrote:
El 2021-09-12 a las 15:19 -0400, Douglas McGarrett escribió:
On 9/12/21 6:24 AM, Carlos E. R. wrote:
On 12/09/2021 00.40, Douglas McGarrett wrote:
I am not familiar with the value of the third number in the ips. I seem to remember that 5 or 6 years ago, all my ips had a 1 in the third position; now they all seem to want a 0.
Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance.
...
I found in the printer manual, a way to get a status sheet from the printer's control panel. It shows that the original static ip address that was set back around 2016 is still in effect. I suspect that whatever is supposed to decode that from a ping has been blown out, since it does not respond to a ping at that ip. Now I mentioned earlier that the third number in the ip addresses on my network now is 0, where it used to be 1, and one of the correspondents here suggested that this is router dependent. Will the router not interrogate an address with a 1 in the third position? (The old router was destroyed in the lightning strike--I can't put it back and try it!) It seems that there are unknown failures in the printer, in addition to the one already found--the FAX line is zapped. comments?
Tell what that IP in the printed paper is. That information is important and you hide it from us.
If it is not 192.168.0.something, the printer will not respond to pings and you have to reconfigure it using its panel.
We're going round in circles. The printer was set up to be 192.168.1.26 back around 2016 or so, and it worked that way--even in OpenSUSE Tumbleweed-- but I could never get it (or the HP, either) to work in Leap, either before or after the lightning strike. As I mentioned previously in this track, all of the items on the lan were originally set up with 1 in the third position, and now it seems that everything (except, of course, this printer) wants to have a 0 in that position. I discovered the hard way that it is EXTREMELY difficult to enter anything into the printer via its control panel. Is there any reason you know of that I should not be able to ping 192.158.1.26 on the lan? Such a ping does not respond: linux1:~ # ping 192.168.1.26 PING 192.168.1.26 (192.168.1.26) 56(84) bytes of data. ^C --- 192.168.1.26 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13295ms --doug
-- Cheers Carlos E. R.
(from openSUSE 15.2 (Legolas))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <69514c5b-685a-45ee-dc64-87f2ff79eae@Legolas.valinor> El 2021-09-12 a las 17:32 -0400, Douglas McGarrett escribió:
On 9/12/21 4:58 PM, Carlos E. R. wrote:
El 2021-09-12 a las 15:19 -0400, Douglas McGarrett escribió:
On 9/12/21 6:24 AM, Carlos E. R. wrote:
On 12/09/2021 00.40, Douglas McGarrett wrote:
...
Tell what that IP in the printed paper is. That information is important and you hide it from us.
If it is not 192.168.0.something, the printer will not respond to pings and you have to reconfigure it using its panel.
We're going round in circles. The printer was set up to be 192.168.1.26 back around 2016 or so, and it worked that way--even in OpenSUSE Tumbleweed-- but I could never get it (or the HP, either) to work in Leap, either before or after the lightning strike. As I mentioned previously in this track, all of the items on the lan were originally set up with 1 in the third position, and now it seems that everything (except, of course, this printer) wants to have a 0 in that position. I discovered the hard way that it is EXTREMELY difficult to enter anything into the printer via its control panel. Is there any reason you know of that I should not be able to ping 192.158.1.26 on the lan? Such a ping does not respond: linux1:~ # ping 192.168.1.26 PING 192.168.1.26 (192.168.1.26) 56(84) bytes of data. ^C --- 192.168.1.26 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13295ms
It is IMPOSSIBLE to access a printer on 192.168.1.26 when the network is 192.168.0.* No matter how difficult it is, you have to tell that printer, using its panel, to use a different address in the 192.168.0.* range. The alternative is to configure the new router to change to 192.168.1.1, and then configure anything else on that network to change back to 192.168.1.* Your choice of difficulty. I would change the printer. You can give the printer a fixed IP on the printer panel, or also in the panel set it up to use an automatic address. Once done this, you have to enter the router configuration to ASSIGN a fixated address to the printer. And please forget the wireshark path, that's very difficult for you and not needed. - -- Cheers Carlos E. R. (from openSUSE 15.2 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYT51Pxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV8DEAnRx5bPb0nybHbwZO11ja BLDJ1I+lAJ9V4mVR7kz++7IHZ3LwOXkOEj4vTA== =5IIX -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2021-09-12 a las 23:46 +0200, Carlos E. R. escribió:
El 2021-09-12 a las 17:32 -0400, Douglas McGarrett escribió:
On 9/12/21 4:58 PM, Carlos E. R. wrote:
...
It is IMPOSSIBLE to access a printer on 192.168.1.26 when the network is 192.168.0.*
No matter how difficult it is, you have to tell that printer, using its panel, to use a different address in the 192.168.0.* range.
The alternative is to configure the new router to change to 192.168.1.1, and then configure anything else on that network to change back to 192.168.1.*
Your choice of difficulty.
I would change the printer.
You can give the printer a fixed IP on the printer panel, or also in the panel set it up to use an automatic address. Once done this, you have to enter the router configuration to ASSIGN a fixated address to the printer.
And please forget the wireshark path, that's very difficult for you and not needed.
Another possibility is to reconfigure every computer in your network to use a /16 mask instead of a /24 mask. I can not assure you that your printer will work with this without changing it, and anyway, it will also be difficult for you. - -- Cheers Carlos E. R. (from openSUSE 15.2 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYT5+vxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVauYAn1d03uTw3wzacD/Q+svt wOXuZ9ybAJ9nzAdDyGi9KJINcuPJyVVu1ekSCA== =X48v -----END PGP SIGNATURE-----
On 9/12/21 6:27 PM, Carlos E. R. wrote:
El 2021-09-12 a las 23:46 +0200, Carlos E. R. escribió:
El 2021-09-12 a las 17:32 -0400, Douglas McGarrett escribió:
On 9/12/21 4:58 PM, Carlos E. R. wrote:
...
It is IMPOSSIBLE to access a printer on 192.168.1.26 when the network is 192.168.0.*
No matter how difficult it is, you have to tell that printer, using its panel, to use a different address in the 192.168.0.* range.
The alternative is to configure the new router to change to 192.168.1.1, and then configure anything else on that network to change back to 192.168.1.*
Your choice of difficulty.
I would change the printer.
You can give the printer a fixed IP on the printer panel, or also in the panel set it up to use an automatic address. Once done this, you have to enter the router configuration to ASSIGN a fixated address to the printer.
And please forget the wireshark path, that's very difficult for you and not needed.
Another possibility is to reconfigure every computer in your network to use a /16 mask instead of a /24 mask. I can not assure you that your printer will work with this without changing it, and anyway, it will also be difficult for you.
-- Cheers Carlos E. R.
(from openSUSE 15.2 (Legolas))
OK! I will change the IP of the printer with its own VERY HAIRY system. Maybe tomorrow. It may take me all afternoon. --doug
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <7b3bb120-411f-d1ac-2aa-c5da7ce84bd8@Legolas.valinor> El 2021-09-12 a las 19:46 -0400, Douglas McGarrett escribió:
On 9/12/21 6:27 PM, Carlos E. R. wrote:
El 2021-09-12 a las 23:46 +0200, Carlos E. R. escribió:
El 2021-09-12 a las 17:32 -0400, Douglas McGarrett escribió:
On 9/12/21 4:58 PM, Carlos E. R. wrote:
...
It is IMPOSSIBLE to access a printer on 192.168.1.26 when the network is 192.168.0.*
No matter how difficult it is, you have to tell that printer, using its panel, to use a different address in the 192.168.0.* range.
The alternative is to configure the new router to change to 192.168.1.1, and then configure anything else on that network to change back to 192.168.1.*
Your choice of difficulty.
I would change the printer.
You can give the printer a fixed IP on the printer panel, or also in the panel set it up to use an automatic address. Once done this, you have to enter the router configuration to ASSIGN a fixated address to the printer.
And please forget the wireshark path, that's very difficult for you and not needed.
Another possibility is to reconfigure every computer in your network to use a /16 mask instead of a /24 mask. I can not assure you that your printer will work with this without changing it, and anyway, it will also be difficult for you.
OK! I will change the IP of the printer with its own VERY HAIRY system. Maybe tomorrow. It may take me all afternoon.
Perfect! Just make sure to select an address that is free and not in the router pool for automatic addresses. Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different). It can be done if you connect printer to computer directly, single cable, and change the network configuration of the computer temporarily. I don't know how complicated that would be for you. - -- Cheers Carlos E. R. (from openSUSE 15.2 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYT6Vaxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV1PcAn0A4P1SXpxxrNqrZI4Xh BKB2ZEFwAJ485z7uTTpqw9eWB0zK+S4u9mh/1Q== =yJfZ -----END PGP SIGNATURE-----
On 9/12/21 8:03 PM, Carlos E. R. wrote: > Content-ID: <7b3bb120-411f-d1ac-2aa-c5da7ce84bd8@Legolas.valinor> > > > El 2021-09-12 a las 19:46 -0400, Douglas McGarrett escribió: > > On 9/12/21 6:27 PM, Carlos E. R. wrote: > >> El 2021-09-12 a las 23:46 +0200, Carlos E. R. escribió: > >>> El 2021-09-12 a las 17:32 -0400, Douglas McGarrett escribió: > >> >> On 9/12/21 4:58 PM, Carlos E. R. wrote: > >> > >> ... > >> > >>> It is IMPOSSIBLE to access a printer on 192.168.1.26 when the > network is > >>> 192.168.0.* > >> > >>> No matter how difficult it is, you have to tell that printer, > using its > >>> panel, to use a different address in the 192.168.0.* range. > >> > >>> The alternative is to configure the new router to change to > 192.168.1.1, > >>> and then configure anything else on that network to change back to > >>> 192.168.1.* > >> > >>> Your choice of difficulty. > >> > >>> I would change the printer. > >> > >>> You can give the printer a fixed IP on the printer panel, or also in > >>> the panel set it up to use an automatic address. Once done this, you > >>> have to enter the router configuration to ASSIGN a fixated address > >>> to the printer. > >> > >> > >>> And please forget the wireshark path, that's very difficult for > you and > >>> not needed. > >> > >> > >> Another possibility is to reconfigure every computer in your > network to > >> use a /16 mask instead of a /24 mask. I can not assure you that your > >> printer will work with this without changing it, and anyway, it > will also > >> be difficult for you. > >> > > > OK! I will change the IP of the printer with its own VERY HAIRY > system. Maybe tomorrow. It may take me all afternoon. > > Perfect! > > Just make sure to select an address that is free and not in the router > pool for automatic addresses. > > > Notice that the printer may have a web page of its own to change its > own configuration, but reaching it is not easy as you are in different > lan sections (the third number is different). > > It can be done if you connect printer to computer directly, single > cable, and change the network configuration of the computer > temporarily. I don't know how complicated that would be for you. > > > -- Cheers > Carlos E. R. > > (from openSUSE 15.2 (Legolas)) Two questions: 1. How do I find out what's in the router pool? 2. The way everything was set up 5 years ago, all the ip addresses were between 192.168.1.10 and 192.168.1.29. Everything on the net had a static ip. [I had a maven telling me how to do that.] It seems that the automatic assignments now are 192.168.0.100 .101 .102, etc. I would like to set all the items (2 desktops, 2 laptops, 2 printers) to static ips once again--only one of the laptops and the Epson are original components. Can the lower numbers between .10 and .29 be used now, or must they all be greater than .100? --doug
On 13/09/2021 04.03, Douglas McGarrett wrote:
On 9/12/21 8:03 PM, Carlos E. R. wrote:
Two questions: 1. How do I find out what's in the router pool?
That's not easy to tell, because each router does it a bit different. I would have to read that router manual. If the router is provided by your ISP, then it would depend on how your ISP sets up your router. Ideally, there would be a manual from your ISP, so have a look at your ISP web help pages.
2. The way everything was set up 5 years ago, all the ip addresses were between 192.168.1.10 and 192.168.1.29.
Everything on the net had a static ip. [I had a maven telling me how to do that.] It seems that the automatic assignments now are 192.168.0.100 .101 .102, etc. I would like to set all the items (2 desktops, 2 laptops, 2 printers) to static ips once again--only one of the laptops and the Epson are original components. Can the lower numbers between .10 and .29 be used now, or must they all be greater than .100?
Ok, if you notice that your automatic IPs are getting numbers like 100, 101, 102... chances are that you can manually assign numbers starting from 2 up to 99 - but this is a guess. So, yes, you could use number between .10 and .29. That is, SMALLER than .100. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Douglas McGarrett composed on 2021-09-12 22:03 (UTC-0400):
1. How do I find out what's in the router pool?
Open 192.168.0.1 in web browser, login, find LAN DHCP section.
2. The way everything was set up 5 years ago, all the ip addresses were between 192.168.1.10 and 192.168.1.29. Everything on the net had a static ip. [I had a maven telling me how to do that.] It seems that the automatic assignments now are 192.168.0.100 .101 .102, etc. I would like to set all the items (2 desktops, 2 laptops, 2 printers) to static ips once again--only one of the laptops and the Epson are original components. Can the lower numbers between .10 and .29 be used now, or must they all be greater than .100?
You're free to designate the beginning and ending addresses of the pool if your router is like most cheap routers. My own pool has a size of only 21 addresses, as all my machines except for one laptop are on static IP assignments. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 13/09/2021 04.28, Felix Miata wrote:
Douglas McGarrett composed on 2021-09-12 22:03 (UTC-0400):
1. How do I find out what's in the router pool?
Open 192.168.0.1 in web browser, login, find LAN DHCP section.
2. The way everything was set up 5 years ago, all the ip addresses were between 192.168.1.10 and 192.168.1.29. Everything on the net had a static ip. [I had a maven telling me how to do that.] It seems that the automatic assignments now are 192.168.0.100 .101 .102, etc. I would like to set all the items (2 desktops, 2 laptops, 2 printers) to static ips once again--only one of the laptops and the Epson are original components. Can the lower numbers between .10 and .29 be used now, or must they all be greater than .100?
You're free to designate the beginning and ending addresses of the pool if your router is like most cheap routers. My own pool has a size of only 21 addresses, as all my machines except for one laptop are on static IP assignments.
On a router provided by the ISP and with a configuration provided by them, I prefer minimal changes (minimal interference). In the case of my ISP, the routers are configured (and maintained) remotely by the ISP, not the clients, who do not have the password (but the client can request the password and take over). In the normal case, the client logs into a remote web page at the ISP, where he can do just a few changes, and then the ISP applies them to the client router, independently of brand. It is not that simple to make generalizations. So unless you know why they do what and how they do it, the generic rule is "minimal change". In this case, look, and don't change, adapt. That way, if you have to phone the ISP for help, they can help. If you change things, it is up to you, no help. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. composed on 2021-09-13 04:39 (UTC+0200):
On a router provided by the ISP
Given Doug's in my time zone, it's safe to assume that he, like most north Americans, is far less likely on DSL than cable, where routers IME historically have been owned mostly by users. It's only relatively recently that cable providers have bundled their own routers with/in their modems to further gouge subscribers. I've never used a router supplied by a provider, and only briefly used a provider modem. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2021-09-12 11:12 p.m., Felix Miata wrote:
Carlos E. R. composed on 2021-09-13 04:39 (UTC+0200):
On a router provided by the ISP
Given Doug's in my time zone, it's safe to assume that he, like most north Americans, is far less likely on DSL than cable, where routers IME historically have been owned mostly by users. It's only relatively recently that cable providers have bundled their own routers with/in their modems to further gouge subscribers. I've never used a router supplied by a provider, and only briefly used a provider modem.
My ISP, Rogers in Canada, has always provided the modem, going back to the late '90s. However, some resellers allow customers to buy their own. Also, the main phone company also provides modems for their ADSL customers.
* James Knott <james.knott@jknott.net> [09-12-21 23:33]:
On 2021-09-12 11:12 p.m., Felix Miata wrote:
Carlos E. R. composed on 2021-09-13 04:39 (UTC+0200):
On a router provided by the ISP
Given Doug's in my time zone, it's safe to assume that he, like most north Americans, is far less likely on DSL than cable, where routers IME historically have been owned mostly by users. It's only relatively recently that cable providers have bundled their own routers with/in their modems to further gouge subscribers. I've never used a router supplied by a provider, and only briefly used a provider modem.
My ISP, Rogers in Canada, has always provided the modem, going back to the late '90s. However, some resellers allow customers to buy their own. Also, the main phone company also provides modems for their ADSL customers.
same in Indiana when I was on cable. when I switched to dsl, the provider installed a combination modem/router. currently 1g fiber at&t. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 2021-09-13 9:23 a.m., Patrick Shanahan wrote:
My ISP, Rogers in Canada, has always provided the modem, going back to the late '90s. However, some resellers allow customers to buy their own. Also, the main phone company also provides modems for their ADSL customers. same in Indiana when I was on cable. when I switched to dsl, the provider installed a combination modem/router. currently 1g fiber at&t.
Originally, Rogers provided only a plain modem. Then "gateways" which included a router. Now the box I have does Internet, home phone and IPTV. However, since I have put it in bridge mode, the router & WiFi are not used.
On 9/12/21 11:12 PM, Felix Miata wrote:
Carlos E. R. composed on 2021-09-13 04:39 (UTC+0200):
On a router provided by the ISP
Given Doug's in my time zone, it's safe to assume that he, like most north Americans, is far less likely on DSL than cable, where routers IME historically have been owned mostly by users. It's only relatively recently that cable providers have bundled their own routers with/in their modems to further gouge subscribers. I've never used a router supplied by a provider, and only briefly used a provider modem. You're correct. The router is mine. By some quirk of fate, it does not have a password, so I can log into it. It turns out that the last time I did was in 2012! I don't know why I replaced it somewhere along the way. Almost all the hardware it connects is newer, so I'll have to adjust it one of these days. Just one more thing to do.
Carlos suggests that I use ip addresses similar to the automatic ones it assigns, and that makes sense, even tho it's one more character to type anytime I need to access something by its address. I am grateful for all the assistance that I've found on this path here! --doug
On 13/09/2021 21.21, Douglas McGarrett wrote: On 9/12/21 11:12 PM, Felix Miata wrote:
Carlos E. R. composed on 2021-09-13 04:39 (UTC+0200):
On a router provided by the ISP
Given Doug's in my time zone, it's safe to assume that he, like most north Americans, is far less likely on DSL than cable, where routers IME historically have been owned mostly by users. It's only relatively recently that cable providers have bundled their own routers with/in their modems to further gouge subscribers. I've never used a router supplied by a provider, and only briefly used a provider modem.
You're correct. The router is mine. By some quirk of fate, it does not have a password, so I can log into it. It turns out that the last time I did was in 2012! I don't know why I replaced it somewhere along the way. Almost all the hardware it connects is newer, so I'll have to adjust it one of these days. Just one more thing to do.
If the router is yours, you could change the IP range to be 192.168.1.* and problem solved.
Carlos suggests that I use ip addresses similar to the automatic ones it assigns, and that makes sense, even tho it's one more character to type anytime I need to access something by its address.
Er... no, different addresses. The router is, apparently, assigning addresses starting with .100 onwards, so you can assign (probably) address lower than 100.
I am grateful for all the assistance that I've found on this path here!
-- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different).
Same LAN, just different IP range. Doug, you could just add that network - ip addr add 192.168.1.199/24 dev eth0 That will make the printer (and any web-config) accessible. Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range. -- Per Jessen, Zürich (18.0°C)
On 13/09/2021 08.24, Per Jessen wrote:
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different).
Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
Huh, I forgot that method. But better using network manager or yast, which I guess are in automatic mode.
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range.
Yes, because every machine in the network using that printer is affected. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Le 13/09/2021 à 11:33, Carlos E. R. a écrit :
On 13/09/2021 08.24, Per Jessen wrote:
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different).
Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
Huh, I forgot that method. But better using network manager or yast, which I guess are in automatic mode.
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range.
Yes, because every machine in the network using that printer is affected.
the better solution could be simply to *reset* to default the printer setup, most probably aimed to dhcp IP jdd -- http://dodin.org
On 13/09/2021 11.37, jdd@dodin.org wrote:
Le 13/09/2021 à 11:33, Carlos E. R. a écrit :
On 13/09/2021 08.24, Per Jessen wrote:
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different).
Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
Huh, I forgot that method. But better using network manager or yast, which I guess are in automatic mode.
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range.
Yes, because every machine in the network using that printer is affected.
the better solution could be simply to *reset* to default the printer setup, most probably aimed to dhcp IP
This is another can of worms. AFAIK, Linux needs the printer to be always in the same IP address, so then you must reconfigure the router to assign always the same IP to the printer. Doug doesn't know how to do this and would need handholding, and we don't even know the router model and current configuration. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Le 13/09/2021 à 11:48, Carlos E. R. a écrit :
On 13/09/2021 11.37, jdd@dodin.org wrote:
the better solution could be simply to *reset* to default the printer setup, most probably aimed to dhcp IP
This is another can of worms.
AFAIK, Linux needs the printer to be always in the same IP address, so then you must reconfigure the router to assign always the same IP to the printer.
this is mostly done automatically by most dhcp router (the lease is long) Doug doesn't know how to do this and would need handholding,
and we don't even know the router model and current configuration.
but this will make the printer use the right sub network and be found jdd -- http://dodin.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2021-09-13 a las 11:55 +0200, jdd@dodin.org escribió:
Le 13/09/2021 à 11:48, Carlos E. R. a écrit :
On 13/09/2021 11.37, jdd@dodin.org wrote:
the better solution could be simply to *reset* to default the printer setup, most probably aimed to dhcp IP
This is another can of worms.
AFAIK, Linux needs the printer to be always in the same IP address, so then you must reconfigure the router to assign always the same IP to the printer.
this is mostly done automatically by most dhcp router (the lease is long)
We don't know for sure. Does it survive a router power cycle?
Doug doesn't know how to do this and would need handholding, and we don't even know the router model and current configuration.
but this will make the printer use the right sub network and be found
Yes, but if the printer is disconnected for a week, it will stop working and he will ask us again for help finding the printer. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYT8hghwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcRo0A/iKpkbWtEbveNvRFPKj1 AO5w/N1ZuLFqWL3UpuMcouYDAP9FmUxguUrt06VQbabf4K/Nr6TF0QlJWrlEGIut X7uroA== =2oTJ -----END PGP SIGNATURE-----
Le 13/09/2021 à 12:01, Carlos E. R. a écrit :
Yes, but if the printer is disconnected for a week, it will stop working and he will ask us again for help finding the printer.
not sure and the ip will be given by printer printed setup I happen to have IP change every few *years* jdd -- http://dodin.org
On 13/09/2021 12.10, jdd@dodin.org wrote:
Le 13/09/2021 à 12:01, Carlos E. R. a écrit :
Yes, but if the printer is disconnected for a week, it will stop working and he will ask us again for help finding the printer.
not sure and the ip will be given by printer printed setup
I happen to have IP change every few *years*
That's nice :-) I wonder how to find out the time lease easily :-? -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Le 13/09/2021 à 13:22, Carlos E. R. a écrit :
On 13/09/2021 12.10, jdd@dodin.org wrote:
Le 13/09/2021 à 12:01, Carlos E. R. a écrit :
Yes, but if the printer is disconnected for a week, it will stop working and he will ask us again for help finding the printer.
not sure and the ip will be given by printer printed setup
I happen to have IP change every few *years*
That's nice :-)
I wonder how to find out the time lease easily :-?
on the modem. But even with smaller lease, the IP happen to be the same because it's the first available :-) jdd -- http://dodin.org
On 13/09/2021 13.57, jdd@dodin.org wrote:
Le 13/09/2021 à 13:22, Carlos E. R. a écrit :
On 13/09/2021 12.10, jdd@dodin.org wrote:
Le 13/09/2021 à 12:01, Carlos E. R. a écrit :
Yes, but if the printer is disconnected for a week, it will stop working and he will ask us again for help finding the printer.
not sure and the ip will be given by printer printed setup
I happen to have IP change every few *years*
That's nice :-)
I wonder how to find out the time lease easily :-?
on the modem.
That's not "easily".
But even with smaller lease, the IP happen to be the same because it's the first available :-)
In my network manager log, I have this entry which I do not know how to interpret: <3.6> 2021-09-13 11:24:44 minas-tirith NetworkManager 2000 - - <info> [1631525084.6446] dhcp4 (wlan0): option expiry => '1631528683' Maybe that is seconds? It is a lot, if it survives power cycles. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. wrote:
Maybe that is seconds? It is a lot, if it survives power cycles.
It is probably a timestamp based on seconds since 1 January 1970 - which makes it about 7200seconds. -- Per Jessen, Zürich (24.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
On 13/09/2021 14.27, Per Jessen wrote:
Carlos E. R. wrote:
Maybe that is seconds? It is a lot, if it survives power cycles.
It is probably a timestamp based on seconds since 1 January 1970 - which makes it about 7200seconds.
Ah. minas-tirith:~ # grep expiry /var/log/NetworkManager <3.6> 2021-09-13 11:24:44 => '1631528683' <3.6> 2021-09-13 11:54:45 => '1631530484' <3.6> 2021-09-13 12:24:45 => '1631532284' <3.6> 2021-09-13 12:54:45 => '1631534084' <3.6> 2021-09-13 13:24:45 => '1631535884' <3.6> 2021-09-13 13:54:45 => '1631537684' <3.6> 2021-09-13 14:24:45 => '1631539484' <3.6> 2021-09-13 14:54:45 => '1631541284' Difference is 1800. cer@minas-tirith:~> date -d @1631541284 Mon Sep 13 15:54:44 CEST 2021 cer@minas-tirith:~> You are absolutely right. So then this router has a lease time of one hour less one second. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different). Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range. Per, you rock! That sure beats trying to reset the address at the
On 9/13/21 2:24 AM, Per Jessen wrote: printer itself. It is a very clumsy setup to do that. Danke sehr! --doug
On 13/09/2021 21.35, Douglas McGarrett wrote:
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different). Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range. Per, you rock! That sure beats trying to reset the address at the
On 9/13/21 2:24 AM, Per Jessen wrote: printer itself. It is a very clumsy setup to do that. Danke sehr!
Ok. Be aware that the command above is not permanent, has to be done on every boot, and on every system or machine that accesses that printer. You could do: 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: http://192.168.1.whatever 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. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/13/21 4:36 PM, Carlos E. R. wrote:
On 13/09/2021 21.35, Douglas McGarrett wrote:
Carlos E. R. wrote:
Notice that the printer may have a web page of its own to change its own configuration, but reaching it is not easy as you are in different lan sections (the third number is different). Same LAN, just different IP range.
Doug, you could just add that network -
ip addr add 192.168.1.199/24 dev eth0
That will make the printer (and any web-config) accessible.
Otherwise I agree with Carlos, the easiest thing is to reconfigure your printer and give it a static IP-address in the new 192.168.0.x range. Per, you rock! That sure beats trying to reset the address at the
On 9/13/21 2:24 AM, Per Jessen wrote: printer itself. It is a very clumsy setup to do that. Danke sehr! Ok.
Be aware that the command above is not permanent, has to be done on every boot, and on every system or machine that accesses that printer.
You could do:
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
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
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 ==================================================================================================================
participants (8)
-
Carlos E. R. -
Douglas McGarrett -
Felix Miata -
James Knott -
jdd＠dodin.org -
Patrick Shanahan -
Per Jessen -
Rodney Baker