Linux Mint 21.1

Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
Model: BEFVP41 ver2

I have the ancient router above. It works.

I haven't logged into it for years.

I went to the manual to read how to log into the web interface. I was told to put 192.168.1.1 into the browser. It just timed out. I tried a different browser and got the same results.

My guess is that browsers changed since the ancient manual for my ancient router was written.

Is there anyway around this?

Thanks for any clues

On 21/01/2023 13:02, Steve Mysterious wrote:
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was told to put 192.168.1.1 into the browser. It just timed out. I tried a different browser and got the same results.
>
> My guess is that browsers changed since the ancient manual for my ancient router was written.
You may well have changed its interface.
This doesn't matter.

If you switch it on and connect the standalone MINT to it , it should
honour a DHCP request. Or if it is all working, proceed to next step

Now you can go into the network interface on the MINT box and see
evidence that it has - usually a sort of networking icon in one of the
panels.
Right click on that, select 'connection information' and see what
'default route' is set to. That will be the current IP address of the router
>
> Is there anyway around this?
>
Use that address to connect to the router. I hope you haven't forgotten
your passwords

> Thanks for any clues

If all else fails switching on while holding some button down or pushing
a pin in a hole usually set everything to 'factory defaults;/ which is a
right pain as you lose all the passwords to connect to the internet

--
"A point of view can be a dangerous luxury when substituted for insight
and understanding".

Marshall McLuhan

On 2023-01-21, Steve Mysterious <tinker123@gmail.com> wrote:
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was
> told to put 192.168.1.1 into the browser. It just timed out. I tried
> a different browser and got the same results.

So it's not listening on 192.168.1.1 on port 80 - it must have a
different IP address or listening on a different port. Did you not keep
notes on how you configured it?

Can you ping that IP address?

There will be a way to factory reset the router - BUT you will loose the
configuration, so make sure you have the relevant data to configure your
connection etc and you know how to use that data.

> My guess is that browsers changed since the ancient manual for my
> ancient router was written.

There is one slight possibility. That the browsers you tried were
configured to only use an HTTPS connection, and the router only supports
unsecured HTTP.

> Is there anyway around this?
>
> Thanks for any clues

On 2023-01-21 14:02, Steve Mysterious wrote:
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was told to put 192.168.1.1 into the browser. It just timed out. I tried a different browser and got the same results.
>
> My guess is that browsers changed since the ancient manual for my ancient router was written.

Warm, but not hot :-)

You need http, not https, most probably. Try:

http://192.168.1.1

your modern browser will not want to do this, so you have to insist.

--
Cheers, Carlos.

At Sat, 21 Jan 2023 05:02:45 -0800 (PST) Steve Mysterious <tinker123@gmail.com> wrote:

>
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was told to put 192.168.1.1 into the browser. It just timed out. I tried a different browser and got the same results.
>
> My guess is that browsers changed since the ancient manual for my ancient router was written.

Not really...

>
> Is there anyway around this?

Check to see what netstat -rn says. The default route IP should be the
router's IP.

One other thing: you might want to change the settings in your browser: Many
"modern" browsers have a "SSL Only" and will force a https: connection, but
most "ancient" routers don't bother with a (self-signed) cert and only connect
"insecurely" with plain http:. You have to disable the "SSL Only" setting in
the browser. And connect with http://192.168.1.1 [include the http://] (or
whatever the IP address shown by netstat -rn).

>
> Thanks for any clues
>
>

--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@deepsoft.com -- Webhosting Services

On Saturday, January 21, 2023 at 8:40:45 AM UTC-5, The Natural Philosopher wrote:
> Now you can go into the network interface on the MINT box and see
> evidence that it has - usually a sort of networking icon in one of the
> panels.
> Right click on that, select 'connection information' and see what
> 'default route' is set to. That will be the current IP address of the router

Yep.

https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png

I tried 216.15.0.1 in my browser. It didn't work either though the browser rejected it very quickly.

On Saturday, January 21, 2023 at 8:56:44 AM UTC-5, Robert Heller wrote:
> Check to see what netstat -rn says. The default route IP should be the
> router's IP.

https://i.paste.pics/9e8bd265ce629f5002d4f4d50f014ee8.png

I tried the various IPs there, none worked.
>
> One other thing: you might want to change the settings in your browser: Many
> "modern" browsers have a "SSL Only" and will force a https: connection,

My browser, Firefox, already had that shut off

https://i.paste.pics/a5d72ee3c732705e9c6efb8ad528a67f.png

Interestingly, when the IP times out in the browser it has an https:// in front of it, even though I am prepending http://

On 21/01/2023 15:47, Steve Mysterious wrote:
> On Saturday, January 21, 2023 at 8:40:45 AM UTC-5, The Natural Philosopher wrote:
>> Now you can go into the network interface on the MINT box and see
>> evidence that it has - usually a sort of networking icon in one of the
>> panels.
>> Right click on that, select 'connection information' and see what
>> 'default route' is set to. That will be the current IP address of the router
>
> Yep.
>
> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png
>
> I tried 216.15.0.1 in my browser. It didn't work either though the browser rejected it very quickly.
Hmm. try telnetting to that.

Or using https.

The rapid refusal means it responded but refused access to the port you
are trying to access.

--
“It is not the truth of Marxism that explains the willingness of
intellectuals to believe it, but the power that it confers on
intellectuals, in their attempts to control the world. And since...it is
futile to reason someone out of a thing that he was not reasoned into,
we can conclude that Marxism owes its remarkable power to survive every
criticism to the fact that it is not a truth-directed but a
power-directed system of thought.”
Sir Roger Scruton

On 21/01/2023 16:01, Steve Mysterious wrote:
> On Saturday, January 21, 2023 at 8:56:44 AM UTC-5, Robert Heller wrote:
>> Check to see what netstat -rn says. The default route IP should be the
>> router's IP.
>
> https://i.paste.pics/9e8bd265ce629f5002d4f4d50f014ee8.png
>
> I tried the various IPs there, none worked.
>>
>> One other thing: you might want to change the settings in your browser: Many
>> "modern" browsers have a "SSL Only" and will force a https: connection,
>
> My browser, Firefox, already had that shut off
>
> https://i.paste.pics/a5d72ee3c732705e9c6efb8ad528a67f.png
>
> Interestingly, when the IP times out in the browser it has an https:// in front of it, even though I am prepending http://

Mmm. it may be that the router needs rebooting. It may be sorta wedged.
It looks like it is redirecting you to the https port but that isn't
responding. web daemon crashed?

try telnet. Many routers will respond to that on a LAN connection. Same
name/password/.

--
In todays liberal progressive conflict-free education system, everyone
gets full Marx.

On Sat, 21 Jan 2023 05:02:45 -0800, Steve Mysterious wrote:

> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface.
> I was told to put 192.168.1.1 into the browser. It just timed
> out. I tried a different browser and got the same results.

It sounds like you may not have a route to your router.

Take a look at the results from
/sbin/route -n
to see if you have a route to 192.168.1.1 . Remember,
192.168 numbers are not internet-routable, so the default
route will not count.

/If/ you are lacking a route to the 192.168.1 network, or
to the 192.168.1.1 host, then assign one. The specifics
of this assignment will depend on /how/ you communicate
to your cable router: if you use a dedicated ethernet
interface, you ensure that the route is assigned to that
interface. If you've attached the router to an interface
that already lives in a different network, you will
need to create an "alias" interface of your live interface,
and assign the 192.168.1 network to /that/ interface.

> My guess is that browsers changed since the ancient manual for
> my ancient router was written.

More likely that your system lives on a different network, and
can't find a route to your 192.168.1.1 router.

> Is there anyway around this?
>
> Thanks for any clues

One other possibility: is there /another/ device already
assigned the 192.168.1.1 IP address? Could be an address
conflict causing the problem.

HTH
--
Lew Pitcher
"In Skills We Trust"

At Sat, 21 Jan 2023 08:01:43 -0800 (PST) Steve Mysterious <tinker123@gmail.com> wrote:

>
> On Saturday, January 21, 2023 at 8:56:44 AM UTC-5, Robert Heller wrote:
> > Check to see what netstat -rn says. The default route IP should be the
> > router's IP.
>
> https://i.paste.pics/9e8bd265ce629f5002d4f4d50f014ee8.png
>
> I tried the various IPs there, none worked.
> >
> > One other thing: you might want to change the settings in your browser: Many
> > "modern" browsers have a "SSL Only" and will force a https: connection,
>
> My browser, Firefox, already had that shut off
>
> https://i.paste.pics/a5d72ee3c732705e9c6efb8ad528a67f.png
>
> Interestingly, when the IP times out in the browser it has an https:// in front of it, even though I am prepending http://

You need to clear the cache and/or restart firefox. FF is *remembering* the
https and is ?helpfully? sticking it in and trying to connect to port 443
which is timing out.

You *cannot* just type the IP address -- FF (and I'm guessing Chrome* also)
with *always* stick https:// in front, if you don't *explicitly* type the
http://. Web browsers want to protect you and *won't* default to http:// --
they will default to https:// And when you do enter http:// the browser will
likely complain with a warning message, even if the "SSL Only" feature is
turned off.

And the 216.15.0.1 is NOT *your* router's *LAN* IP address. 216.15.0.0/17 is a
public IP range owned by RCN Corporation (you cable provider?).

>
>

--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@deepsoft.com -- Webhosting Services

On Sat, 21 Jan 2023 16:51:54 +0000, Lew Pitcher wrote:

> On Sat, 21 Jan 2023 05:02:45 -0800, Steve Mysterious wrote:
>
>> Linux Mint 21.1
>>
>> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
>> Model: BEFVP41 ver2
>>
>> I have the ancient router above. It works.
>>
>> I haven't logged into it for years.
>>
>> I went to the manual to read how to log into the web interface.
>> I was told to put 192.168.1.1 into the browser. It just timed
>> out. I tried a different browser and got the same results.
>
> It sounds like you may not have a route to your router.
>
> Take a look at the results from
> /sbin/route -n
> to see if you have a route to 192.168.1.1 . Remember,
> 192.168 numbers are not internet-routable, so the default
> route will not count.
>
> /If/ you are lacking a route to the 192.168.1 network, or
> to the 192.168.1.1 host, then assign one. The specifics
> of this assignment will depend on /how/ you communicate
> to your cable router: if you use a dedicated ethernet
> interface, you ensure that the route is assigned to that
> interface. If you've attached the router to an interface
> that already lives in a different network, you will
> need to create an "alias" interface of your live interface,
> and assign the 192.168.1 network to /that/ interface.

I took a quick peek at an old script I wrote to bring my DSL
modem's management link online, and came up with two examples
for you to consider:
# Example 1: Use (otherwise unused) eth1 device
## give eth1 an address on the 192.168.1/24 network
/sbin/ifconfig eth1 192.168.1.9 \
broadcast 192.168.1.255 \
netmask 255.255.255.0
## establish a route to the 192.168.1/24 network
/sbin/route -A inet add -net 192.168.1.0 \
netmask 255.255.255.0 \
dev eth1
## establish a route to ourselves as the 192.168.1.9 host
/sbin/route -A inet add -host 192.168.1.9 \
dev eth1

or

# Example 2: Use (already in use) eth0 device
# but with alias eth0:1 so as not to disturb existing routes
## give eth0:1 an address on the 192.168.1/24 network
/sbin/ifconfig eth0:1 192.168.1.9 \
broadcast 192.168.1.255 \
netmask 255.255.255.0
## establish a route to the 192.168.1/24 network
/sbin/route -A inet add -net 192.168.1.0 \
netmask 255.255.255.0 \
dev eth0:1
## establish a route to ourselves as the 192.168.1.9 host
/sbin/route -A inet add -host 192.168.1.9 \
dev eth0:1

>> My guess is that browsers changed since the ancient manual for
>> my ancient router was written.
>
> More likely that your system lives on a different network, and
> can't find a route to your 192.168.1.1 router.
>
>> Is there anyway around this?
>>
>> Thanks for any clues
>
> One other possibility: is there /another/ device already
> assigned the 192.168.1.1 IP address? Could be an address
> conflict causing the problem.
>
> HTH

--
Lew Pitcher
"In Skills We Trust"

On 2023-01-21 17:01, Steve Mysterious wrote:
> On Saturday, January 21, 2023 at 8:56:44 AM UTC-5, Robert Heller wrote:
>> Check to see what netstat -rn says. The default route IP should be the
>> router's IP.
>
> https://i.paste.pics/9e8bd265ce629f5002d4f4d50f014ee8.png
>
> I tried the various IPs there, none worked.
>>
>> One other thing: you might want to change the settings in your browser: Many
>> "modern" browsers have a "SSL Only" and will force a https: connection,
>
> My browser, Firefox, already had that shut off
>
> https://i.paste.pics/a5d72ee3c732705e9c6efb8ad528a67f.png
>
> Interestingly, when the IP times out in the browser it has an https:// in front of it, even though I am prepending http://

What IP does your computer have? 192.168.1.X? Or something else? Like
192.168.0.X or 192.168.2.X

Do:

nmap 192.168.1.*

and the router should respond.

Example:

Telcontar:~ # nmap 192.168.1.*
Starting Nmap 7.92 ( https://nmap.org ) at 2023-01-21 18:49 CET
Nmap scan report for router.valinor (192.168.1.1)
Host is up (0.00036s latency).
Not shown: 980 closed tcp ports (reset)
PORT STATE SERVICE
21/tcp filtered ftp
22/tcp open ssh
23/tcp filtered telnet
80/tcp open http <====
99/tcp filtered metagram
146/tcp filtered iso-tp0
301/tcp filtered unknown
443/tcp open https <===
563/tcp filtered snews
1122/tcp filtered availant-mgr
1301/tcp filtered ci3-software-1
2604/tcp filtered ospfd
5030/tcp filtered surfpass
5431/tcp open park-agent
5666/tcp filtered nrpe
6106/tcp filtered isdninfo
8090/tcp filtered opsmessaging
49154/tcp filtered unknown
49167/tcp filtered unknown
55055/tcp filtered unknown
MAC Address: CC:ED:DC:05:80:D4 (MitraStar Technology)

....

--
Cheers, Carlos.

On 21/01/2023 15:47, Steve Mysterious wrote:
> On Saturday, January 21, 2023 at 8:40:45 AM UTC-5, The Natural Philosopher wrote:
>> Now you can go into the network interface on the MINT box and see
>> evidence that it has - usually a sort of networking icon in one of the
>> panels.
>> Right click on that, select 'connection information' and see what
>> 'default route' is set to. That will be the current IP address of the router
>
> Yep.
>
> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png
>
> I tried 216.15.0.1 in my browser. It didn't work either though the browser rejected it very quickly.

That is a funny IP address for a router. Are you sure it is a router IP
as opposed to an ISP in Maryland. Maybe your router is in modem mode?

On 2023-01-21 19:13, Pancho wrote:
> On 21/01/2023 15:47, Steve Mysterious wrote:
>> On Saturday, January 21, 2023 at 8:40:45 AM UTC-5, The Natural
>> Philosopher wrote:
>>> Now you can go into the network interface on the MINT box and see
>>> evidence that it has - usually a sort of networking icon in one of the
>>> panels.
>>> Right click on that, select 'connection information' and see what
>>> 'default route' is set to. That will be the current IP address of the
>>> router
>>
>> Yep.
>>
>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png
>>
>> I tried 216.15.0.1 in my browser.  It didn't work either though the
>> browser rejected it very quickly.
>
> That is a funny IP address for a router. Are you sure it is a router IP
> as opposed to an ISP in Maryland. Maybe your router is in modem mode?

You are right, this is a very strange IP.

--
Cheers, Carlos.

On Sat, 21 Jan 2023 20:25:26 +0100, Carlos E.R. wrote:
>
> On 2023-01-21 19:13, Pancho wrote:
>> On 21/01/2023 15:47, Steve Mysterious wrote:
>>>
>>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png
>>>
>>> I tried 216.15.0.1 in my browser.  It didn't work either though the
>>> browser rejected it very quickly.
>> That is a funny IP address for a router. Are you sure it is a router
>> IP as opposed to an ISP in Maryland. Maybe your router is in modem
>> mode?
>
> You are right, this is a very strange IP.

Wonders where it came from.
--
Andreas

On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:
>
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was
> told to put 192.168.1.1 into the browser. It just timed out. I tried
> a different browser and got the same results.

Also try 192.168.0.1 and 192.168.2.1 .

> My guess is that browsers changed since the ancient manual for my ancient router was written.
>
> Is there anyway around this?

Usually the default route is also the address with the web interface. But
as you already mentioned in
https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
there isn't.

I believe the address is still 192.168.1.1 , but something blocking
access from your computer to it. Did you ping it?

Does it has WIFI? Try that IP with a different device connected via WIFI.

> Thanks for any clues

Try a factory reset if else fails.
--
Andreas

At Sat, 21 Jan 2023 17:01:47 -0500 Andreas Kohlbach <ank@spamfence.net> wrote:

>
> On Sat, 21 Jan 2023 20:25:26 +0100, Carlos E.R. wrote:
> >
> > On 2023-01-21 19:13, Pancho wrote:
> >> On 21/01/2023 15:47, Steve Mysterious wrote:
> >>>
> >>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png
> >>>
> >>> I tried 216.15.0.1 in my browser.  It didn't work either though the
> >>> browser rejected it very quickly.
> >> That is a funny IP address for a router. Are you sure it is a router
> >> IP as opposed to an ISP in Maryland. Maybe your router is in modem
> >> mode?
> >
> > You are right, this is a very strange IP.
>
> Wonders where it came from.

Wondering if maybe the OP has things plugged in wrong and somehow has is Mint
PC plugged directly in the WAN and is in fact not using the router at all.
That address is likely his ISP's (cable company?), not a LAN behind a NAT.

--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@deepsoft.com -- Webhosting Services

On Sat, 21 Jan 2023 17:07:12 -0500, Andreas Kohlbach wrote:
> On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:
>>
>> Linux Mint 21.1
>>
>> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
>> Model: BEFVP41 ver2
>>
>> I have the ancient router above. It works.
>>
>> I haven't logged into it for years.
>>
>> I went to the manual to read how to log into the web interface. I was
>> told to put 192.168.1.1 into the browser. It just timed out. I tried
>> a different browser and got the same results.
>
> Also try 192.168.0.1 and 192.168.2.1 .
>
>> My guess is that browsers changed since the ancient manual for my ancient router was written.
>>
>> Is there anyway around this?
>
> Usually the default route is also the address with the web interface. But
> as you already mentioned in
> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
> there isn't.
>
> I believe the address is still 192.168.1.1 , but something blocking
> access from your computer to it. Did you ping it?
>
> Does it has WIFI? Try that IP with a different device connected via WIFI.
>
>> Thanks for any clues
>
> Try a factory reset if else fails.

and read the router manual. I had a router which used .254 instead of .1

On Sat, 21 Jan 2023 20:59:58 -0600, Bit Twister wrote:
> On Sat, 21 Jan 2023 17:07:12 -0500, Andreas Kohlbach wrote:
>> On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:
>>>
>>> Linux Mint 21.1
>>>
>>> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
>>> Model: BEFVP41 ver2
>>>
>>> I have the ancient router above. It works.
>>>
>>> I haven't logged into it for years.
>>>
>>> I went to the manual to read how to log into the web interface. I was
>>> told to put 192.168.1.1 into the browser. It just timed out. I tried
>>> a different browser and got the same results.
>>
>> Also try 192.168.0.1 and 192.168.2.1 .
>>
>>> My guess is that browsers changed since the ancient manual for my ancient router was written.
>>>
>>> Is there anyway around this?
>>
>> Usually the default route is also the address with the web interface. But
>> as you already mentioned in
>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
>> there isn't.
>>
>> I believe the address is still 192.168.1.1 , but something blocking
>> access from your computer to it. Did you ping it?
>>
>> Does it has WIFI? Try that IP with a different device connected via WIFI.
>>
>>> Thanks for any clues
>>
>> Try a factory reset if else fails.
>
> and read the router manual. I had a router which used .254 instead of .1

And do some research to see if this "old" router had known
vulnerabilities. Quite a few old ones did. It could be that
a cracker now "owns" your router.

On 22 Jan 2023 03:23:08 GMT, Allodoxaphobia wrote:
>
> On Sat, 21 Jan 2023 20:59:58 -0600, Bit Twister wrote:
>> On Sat, 21 Jan 2023 17:07:12 -0500, Andreas Kohlbach wrote:
>>> On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:
>>>>
>>>> Linux Mint 21.1
>>>>
>>>> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
>>>> Model: BEFVP41 ver2
>>>>
>>>> I have the ancient router above. It works.
>>>>
>>>> I haven't logged into it for years.
>>>>
>>>> I went to the manual to read how to log into the web interface. I was
>>>> told to put 192.168.1.1 into the browser. It just timed out. I tried
>>>> a different browser and got the same results.
>>>
>>> Also try 192.168.0.1 and 192.168.2.1 .
>>>
>>>> My guess is that browsers changed since the ancient manual for my ancient router was written.
>>>>
>>>> Is there anyway around this?
>>>
>>> Usually the default route is also the address with the web interface. But
>>> as you already mentioned in
>>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
>>> there isn't.
>>>
>>> I believe the address is still 192.168.1.1 , but something blocking
>>> access from your computer to it. Did you ping it?
>>>
>>> Does it has WIFI? Try that IP with a different device connected via WIFI.
>>>
>>>> Thanks for any clues
>>>
>>> Try a factory reset if else fails.
>>
>> and read the router manual. I had a router which used .254 instead of .1

I checked "BEFVP41" and "web interface" against Google, and all pages said
its IP is 192.168.1.1 . Thus I assume that is correct, but something
blocks access to it. Also, because there is a timeout and not an
immediate "Connection refused" or similar indicating the IP is correct.

If the OP has knowledge of Wireshark or TCPDUMP he could try those too.

> And do some research to see if this "old" router had known
> vulnerabilities. Quite a few old ones did. It could be that
> a cracker now "owns" your router.

No idea if his router is property of his ISP (mine is for example). If
so, they do remote firmware updates ever so often. Also, if some bug
cannot be fixed they might just replace it.
--
Andreas

On 1/21/23 05:02, Steve Mysterious wrote:
> Linux Mint 21.1
>
> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
> Model: BEFVP41 ver2
>
> I have the ancient router above. It works.
>
> I haven't logged into it for years.
>
> I went to the manual to read how to log into the web interface. I was told to put 192.168.1.1 into the browser. It just timed out. I tried a different browser and got the same results.
>
> My guess is that browsers changed since the ancient manual for my ancient router was written.
>
> Is there anyway around this?
>
> Thanks for any clues

Try another computer.
Try another browser.
Did you set a password for it in the past?
You may need to wipe the present setting
my holding down the reset button or whatever your
manual specifies.
Finally it may simply be too old.
Some components degrade with time.

Good luck
bliss - up too late.

--
bliss dash SF 4 ever at dslextreme dot com

On 22/01/2023 02:59, Bit Twister wrote:
> On Sat, 21 Jan 2023 17:07:12 -0500, Andreas Kohlbach wrote:
>> On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:
>>>
>>> Linux Mint 21.1
>>>
>>> Linksys Etherfast Cable/DSL VPN Router with 4 Port Switch
>>> Model: BEFVP41 ver2
>>>
>>> I have the ancient router above. It works.
>>>
>>> I haven't logged into it for years.
>>>
>>> I went to the manual to read how to log into the web interface. I was
>>> told to put 192.168.1.1 into the browser. It just timed out. I tried
>>> a different browser and got the same results.
>>
>> Also try 192.168.0.1 and 192.168.2.1 .
>>
>>> My guess is that browsers changed since the ancient manual for my ancient router was written.
>>>
>>> Is there anyway around this?
>>
>> Usually the default route is also the address with the web interface. But
>> as you already mentioned in
>> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
>> there isn't.
>>
>> I believe the address is still 192.168.1.1 , but something blocking
>> access from your computer to it. Did you ping it?
>>
>> Does it has WIFI? Try that IP with a different device connected via WIFI.
>>
>>> Thanks for any clues
>>
>> Try a factory reset if else fails.
>
>
> and read the router manual. I had a router which used .254 instead of .1

I set all my routers to that. Over the years. Hangover from when we
started with isolated LANS and all the machines started at 1...
Servers and other statically adressed stuff all up in the 200+ range

--
How fortunate for governments that the people they administer don't think.

Adolf Hitler

On 21/01/2023 16:53, Robert Heller wrote:
> You need to clear the cache and/or restart firefox. FF is*remembering* the
> https and is ?helpfully? sticking it in and trying to connect to port 443
> which is timing out.
>
> You*cannot* just type the IP address -- FF (and I'm guessing Chrome* also)
> with*always* stick https:// in front, if you don't*explicitly* type the
> http://. Web browsers want to protect you and*won't* default to http:// --
> they will default to https:// And when you do enter http:// the browser will
> likely complain with a warning message, even if the "SSL Only" feature is
> turned off.
>
> And the 216.15.0.1 is NOT*your* router's*LAN* IP address. 216.15.0.0/17 is a
> public IP range owned by RCN Corporation (you cable provider?).

Which is something I missed.

Chances are that he has plugged his Mint into the WAN port.

Or something.

--
How fortunate for governments that the people they administer don't think.

Adolf Hitler

On 2023-01-21 23:07, Andreas Kohlbach wrote:
> On Sat, 21 Jan 2023 05:02:45 -0800 (PST), Steve Mysterious wrote:

....

> Also try 192.168.0.1 and 192.168.2.1 .
>
>> My guess is that browsers changed since the ancient manual for my ancient router was written.
>>
>> Is there anyway around this?
>
> Usually the default route is also the address with the web interface. But
> as you already mentioned in
> https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png the odd IP
> there isn't.
>
> I believe the address is still 192.168.1.1 , but something blocking
> access from your computer to it. Did you ping it?

In that case, he needs an IP in that range in the computer, and an
appropriate route, in order to be able to reach it.

>
> Does it has WIFI? Try that IP with a different device connected via WIFI.
>
>> Thanks for any clues
>
> Try a factory reset if else fails.

Dangerous, as he doesn't remember how it was configured, and how to redo
the configuration.

--
Cheers, Carlos.