Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #36755 > unrolled thread
| Started by | Steve Mysterious <tinker123@gmail.com> |
|---|---|
| First post | 2023-01-21 05:02 -0800 |
| Last post | 2023-01-23 05:46 +0000 |
| Articles | 20 on this page of 51 — 13 participants |
Back to article view | Back to comp.os.linux.misc
Slightly Off Topic: Router Issues Steve Mysterious <tinker123@gmail.com> - 2023-01-21 05:02 -0800
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-21 13:40 +0000
Re: Slightly Off Topic: Router Issues Steve Mysterious <tinker123@gmail.com> - 2023-01-21 07:47 -0800
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-21 16:27 +0000
Re: Slightly Off Topic: Router Issues Pancho <Pancho.Jones@proton.me> - 2023-01-21 18:13 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-21 20:25 +0100
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-21 17:01 -0500
Re: Slightly Off Topic: Router Issues Robert Heller <heller@deepsoft.com> - 2023-01-21 22:45 +0000
Re: Slightly Off Topic: Router Issues Jim Jackson <jj@franjam.org.uk> - 2023-01-21 13:49 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-21 14:49 +0100
Re: Slightly Off Topic: Router Issues Robert Heller <heller@deepsoft.com> - 2023-01-21 13:56 +0000
Re: Slightly Off Topic: Router Issues Steve Mysterious <tinker123@gmail.com> - 2023-01-21 08:01 -0800
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-21 16:30 +0000
Re: Slightly Off Topic: Router Issues Robert Heller <heller@deepsoft.com> - 2023-01-21 16:53 +0000
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-22 09:31 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-21 18:54 +0100
Re: Slightly Off Topic: Router Issues Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-21 16:51 +0000
Re: Slightly Off Topic: Router Issues Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-21 17:05 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-21 17:07 -0500
Re: Slightly Off Topic: Router Issues Bit Twister <BitTwister@mouse-potato.com> - 2023-01-21 20:59 -0600
Re: Slightly Off Topic: Router Issues Allodoxaphobia <trepidation@example.net> - 2023-01-22 03:23 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-22 00:29 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-22 09:29 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-22 12:57 +0100
Re: Slightly Off Topic: Router Issues Bobbie Sellers <bliss@mouse-potato.com> - 2023-01-21 21:51 -0800
Re: Slightly Off Topic: Router Issues Steve Mysterious <tinker123@gmail.com> - 2023-01-22 09:12 -0800
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-22 20:09 +0100
Re: Slightly Off Topic: Router Issues Steve Mysterious <tinker123@gmail.com> - 2023-01-22 17:18 -0800
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-23 02:47 +0100
Re: Slightly Off Topic: Router Issues Robert Heller <heller@deepsoft.com> - 2023-01-23 02:57 +0000
Re: Slightly Off Topic: Router Issues Pancho <Pancho.Jones@proton.me> - 2023-01-23 13:20 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-24 02:33 +0100
Re: Slightly Off Topic: Router Issues "Carlos E. R." <robin_listas@es.invalid> - 2023-01-23 16:37 +0100
Re: Slightly Off Topic: Router Issues Bit Twister <BitTwister@mouse-potato.com> - 2023-01-22 20:57 -0600
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-22 22:37 -0500
Re: Slightly Off Topic: Router Issues "Carlos E. R." <robin_listas@es.invalid> - 2023-01-23 16:39 +0100
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-23 19:13 -0500
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-24 02:29 +0100
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-23 05:43 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-22 22:31 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-23 05:54 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-23 19:12 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-24 03:58 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-24 02:55 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-24 10:24 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-24 18:02 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-24 23:57 +0000
Re: Slightly Off Topic: Router Issues "Carlos E.R." <robin_listas@es.invalid> - 2023-01-25 12:19 +0100
Re: Slightly Off Topic: Router Issues gazelle@shell.xmission.com (Kenny McCormack) - 2023-01-25 12:26 +0000
Re: Slightly Off Topic: Router Issues Andreas Kohlbach <ank@spamfence.net> - 2023-01-22 22:26 -0500
Re: Slightly Off Topic: Router Issues The Natural Philosopher <tnp@invalid.invalid> - 2023-01-23 05:46 +0000
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
| From | Allodoxaphobia <trepidation@example.net> |
|---|---|
| Date | 2023-01-22 03:23 +0000 |
| Message-ID | <slrntspb0s.geo.trepidation@vps.jonz.net> |
| In reply to | #36781 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2023-01-22 00:29 -0500 |
| Message-ID | <871qnn16ie.fsf@usenet.ankman.de> |
| In reply to | #36782 |
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
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2023-01-22 09:29 +0000 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <tqivlc$3201v$2@dont-email.me> |
| In reply to | #36781 |
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
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-22 12:57 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <pukv9jxs4m.ln2@Telcontar.valinor> |
| In reply to | #36778 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Bobbie Sellers <bliss@mouse-potato.com> |
|---|---|
| Date | 2023-01-21 21:51 -0800 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <tqiisv$3025t$2@dont-email.me> |
| In reply to | #36755 |
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
[toc] | [prev] | [next] | [standalone]
| From | Steve Mysterious <tinker123@gmail.com> |
|---|---|
| Date | 2023-01-22 09:12 -0800 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <b6bfa4e9-892a-4323-a7e0-ed02cb2af811n@googlegroups.com> |
| In reply to | #36755 |
Update. I contacted the company that made my router. The support person led me through all of the things you guys suggested. No luck. The support person concluded by process of elimination that there must be something off with my computer settings. I was grateful when she didn't dump me the moment I told her I was running Linux. :-) I do appreciate all of the effort you guys gave me in trying to figure this out, so I decided to post to let you know how things ended. Steve On Saturday, January 21, 2023 at 8:02:49 AM UTC-5, 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
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-22 20:09 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <b8e0ajxk3a.ln2@Telcontar.valinor> |
| In reply to | #36794 |
On 2023-01-22 18:12, Steve Mysterious wrote: > Update. > > I contacted the company that made my router. > > The support person led me through all of the things you guys suggested. No luck. > > The support person concluded by process of elimination that there must be something off with my computer settings. > > I was grateful when she didn't dump me the moment I told her I was running Linux. :-) > > I do appreciate all of the effort you guys gave me in trying to figure this out, so I decided to post to let you > know how things ended. Assuming this is still correct: <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> Basically you need to issue the command "ip addr" and "route". You will probably not have an IP in the range 192.168.1.* nor a route to that range. In order to connect to your router at 192.168.1.1 you first need a route to it. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Steve Mysterious <tinker123@gmail.com> |
|---|---|
| Date | 2023-01-22 17:18 -0800 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <5450be04-83e9-4f3e-a9aa-6198fe173227n@googlegroups.com> |
| In reply to | #36795 |
On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote: > Assuming this is still correct: > <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> It is. > Basically you need to issue the command "ip addr" and "route". You will > probably not have an IP in the range 192.168.1.* nor a route to that > range. In order to connect to your router at 192.168.1.1 you first need > a route to it. I took a look at the manual page for those commands to see what they do. Are you saying I can make a route to 192.168.1.1 and my router? If so, can you point me to a link that will teach me how to do that? Happy Monday
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-23 02:47 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <th51ajxko1.ln2@Telcontar.valinor> |
| In reply to | #36797 |
On 2023-01-23 02:18, Steve Mysterious wrote: > On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote: >> Assuming this is still correct: >> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> > > It is. > > >> Basically you need to issue the command "ip addr" and "route". You will >> probably not have an IP in the range 192.168.1.* nor a route to that >> range. In order to connect to your router at 192.168.1.1 you first need >> a route to it. > > I took a look at the manual page for those commands to see what they do. > > Are you saying I can make a route to 192.168.1.1 and my router? You must do it, yes. Just try to ping 192.168.1.1, it should give you "no route to host" or some error. Not a time out. > If so, can you point me to a link that will teach me how to do that? Not at this moment... I know, more or less, how to do it, following my nose, but I don't have a text for it. Basically, assign a second address to the same ethernet hardware. Or, create, temporarily, another "network manager" connection, manually, that is on 192.168.1.10. When you activate it, you will loose internet connection, but should gain access to the router, hopefully. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Robert Heller <heller@deepsoft.com> |
|---|---|
| Date | 2023-01-23 02:57 +0000 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <lcScnXgKMewxalD-nZ2dnZfqn_GdnZ2d@giganews.com> |
| In reply to | #36798 |
At Mon, 23 Jan 2023 02:47:09 +0100 "Carlos E.R." <robin_listas@es.invalid> wrote:
>
> On 2023-01-23 02:18, Steve Mysterious wrote:
> > On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote:
> >> Assuming this is still correct:
> >> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png>
> >
> > It is.
> >
> >
> >> Basically you need to issue the command "ip addr" and "route". You will
> >> probably not have an IP in the range 192.168.1.* nor a route to that
> >> range. In order to connect to your router at 192.168.1.1 you first need
> >> a route to it.
> >
> > I took a look at the manual page for those commands to see what they do.
> >
> > Are you saying I can make a route to 192.168.1.1 and my router?
>
> You must do it, yes.
>
> Just try to ping 192.168.1.1, it should give you "no route to host" or
> some error. Not a time out.
>
>
> > If so, can you point me to a link that will teach me how to do that?
>
> Not at this moment... I know, more or less, how to do it, following my
> nose, but I don't have a text for it.
>
> Basically, assign a second address to the same ethernet hardware.
>
> Or, create, temporarily, another "network manager" connection, manually,
> that is on 192.168.1.10. When you activate it, you will loose internet
> connection, but should gain access to the router, hopefully.
All of this assumes that OP is jacked into the LAN port(s) of the router (or
connecting via WiFi to the router's Access Point (assuming that this is a WiFi
router -- the above screen shot talks only about a *wired* connection).
The IP address in the screen shot is not a "private" (LAN) IP address [eg
192.168.x.y], it is a public IP address. This suggests that the OP is jacked
in the WAN directly and not into a router providing a private LAN behind a
NAT/firewall. Either the OP's computer is jacked directly into the WAN point
on the cable modem (you really don't want to do that) or the cable modem's WAN
port is jacked in his home switch (not router) [YOU REALLY DON'T WANT TO DO
THAT]. Either way, you are not going to be able to log into the *router*.
>
--
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
[toc] | [prev] | [next] | [standalone]
| From | Pancho <Pancho.Jones@proton.me> |
|---|---|
| Date | 2023-01-23 13:20 +0000 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <tqm1ig$3k1pr$1@dont-email.me> |
| In reply to | #36800 |
On 23/01/2023 02:57, Robert Heller wrote: > > The IP address in the screen shot is not a "private" (LAN) IP address [eg > 192.168.x.y], it is a public IP address. This suggests that the OP is jacked > in the WAN directly and not into a router providing a private LAN behind a > NAT/firewall. Either the OP's computer is jacked directly into the WAN point > on the cable modem (you really don't want to do that) or the cable modem's WAN > port is jacked in his home switch (not router) [YOU REALLY DON'T WANT TO DO > THAT]. Either way, you are not going to be able to log into the *router*. > I think Steve really needs to describe what his cable layout is. Perform a few tests. No need for anything clever until we check basics. Test 1) Switch the router off, see if his PC still has a connection to the internet. Reboot PC. Check "ip route" in a terminal/shell. Check if internet works. Test 2) If Test 1) cuts the internet. Switch the router on again. Disconnect the modem Ethernet cable from the router WAN port, leave the PC Ethernet cable connected to a router LAN port. Reboot PC. Check "ip route" in a PC terminal/shell. Report the results to us. We know the router ain't routing, but we don't know why. Pushing the wrong cable in the wrong port is my standard type of error. :-) But I can imagine other failure modes, that might cause the router to act purely as a switch or bridge.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-24 02:33 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <d4p3ajxkcp.ln2@Telcontar.valinor> |
| In reply to | #36808 |
On 2023-01-23 14:20, Pancho wrote: > On 23/01/2023 02:57, Robert Heller wrote: > >> >> The IP address in the screen shot is not a "private" (LAN) IP >> address [eg 192.168.x.y], it is a public IP address. This suggests >> that the OP is jacked in the WAN directly and not into a router >> providing a private LAN behind a NAT/firewall. Either the OP's >> computer is jacked directly into the WAN point on the cable modem >> (you really don't want to do that) or the cable modem's WAN port is >> jacked in his home switch (not router) [YOU REALLY DON'T WANT TO >> DO THAT]. Either way, you are not going to be able to log into the >> *router*. >> > > I think Steve really needs to describe what his cable layout is. > Perform a few tests. No need for anything clever until we check > basics. > > Test 1) Switch the router off, see if his PC still has a > connection to the internet. Reboot PC. Check "ip route" in a > terminal/shell. Check if internet works. > > Test 2) If Test 1) cuts the internet. Switch the router on again. > Disconnect the modem Ethernet cable from the router WAN port, leave > the PC Ethernet cable connected to a router LAN port. Reboot PC. > Check "ip route" in a PC terminal/shell. > > Report the results to us. > > We know the router ain't routing, but we don't know why. Yes, we do. Or we have an educated guess. The router is in single user mode. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-23 16:37 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <k37ntcFnkh4U1@mid.individual.net> |
| In reply to | #36800 |
On 2023-01-23 03:57, Robert Heller wrote:
> At Mon, 23 Jan 2023 02:47:09 +0100 "Carlos E.R." <robin_listas@es.invalid> wrote:
>
>>
>> On 2023-01-23 02:18, Steve Mysterious wrote:
>>> On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote:
>>>> Assuming this is still correct:
>>>> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png>
>>>
>>> It is.
>>>
>>>
>>>> Basically you need to issue the command "ip addr" and "route". You will
>>>> probably not have an IP in the range 192.168.1.* nor a route to that
>>>> range. In order to connect to your router at 192.168.1.1 you first need
>>>> a route to it.
>>>
>>> I took a look at the manual page for those commands to see what they do.
>>>
>>> Are you saying I can make a route to 192.168.1.1 and my router?
>>
>> You must do it, yes.
>>
>> Just try to ping 192.168.1.1, it should give you "no route to host" or
>> some error. Not a time out.
>>
>>
>>> If so, can you point me to a link that will teach me how to do that?
>>
>> Not at this moment... I know, more or less, how to do it, following my
>> nose, but I don't have a text for it.
>>
>> Basically, assign a second address to the same ethernet hardware.
>>
>> Or, create, temporarily, another "network manager" connection, manually,
>> that is on 192.168.1.10. When you activate it, you will loose internet
>> connection, but should gain access to the router, hopefully.
>
> All of this assumes that OP is jacked into the LAN port(s) of the router (or
> connecting via WiFi to the router's Access Point (assuming that this is a WiFi
> router -- the above screen shot talks only about a *wired* connection).
More likely, the router is configured in modem mode or single user mode.
And he has a router, he said so.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2023-01-22 20:57 -0600 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <slrntsrtst.a5h.BitTwister@wb.home.arpa> |
| In reply to | #36797 |
On Sun, 22 Jan 2023 17:18:19 -0800 (PST), Steve Mysterious wrote:
> On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote:
>> Assuming this is still correct:
>> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png>
>
> It is.
>
>
>> Basically you need to issue the command "ip addr" and "route". You will
>> probably not have an IP in the range 192.168.1.* nor a route to that
>> range. In order to connect to your router at 192.168.1.1 you first need
>> a route to it.
>
> I took a look at the manual page for those commands to see what they do.
>
> Are you saying I can make a route to 192.168.1.1 and my router?
what is the result/output from running
ip route
in a root terminal.
FYI: I can suggest that you could create a ~/.signature file
with information about your setup. The information can help subject matter
exports with supplying actual commands or commands requesting information.
~/.signature file starts with dash dash space Return
Note: I have removed the space from end of dash dash line.
For example:
--
Running Mageia release 7 (Official) for x86_64 using
Kernel 5.5.15-desktop-3.mga7 on x86_64 DM=lightdm DE=xfce
grub Legacy OS boot
For testing your sig file use any group ending in .test.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2023-01-22 22:37 -0500 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <87cz75zztu.fsf@usenet.ankman.de> |
| In reply to | #36797 |
On Sun, 22 Jan 2023 17:18:19 -0800 (PST), Steve Mysterious wrote: > > On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote: >> Assuming this is still correct: >> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> > > It is. > > >> Basically you need to issue the command "ip addr" and "route". You will >> probably not have an IP in the range 192.168.1.* nor a route to that >> range. In order to connect to your router at 192.168.1.1 you first need >> a route to it. > > I took a look at the manual page for those commands to see what they do. > > Are you saying I can make a route to 192.168.1.1 and my router? That's all odd. Shouldn't DNS not take care of everything? Or is that box so old it doesn't know what DNS is? > If so, can you point me to a link that will teach me how to do that? Something like /sbin/route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0 You need to replace eth0 with whatever the name of your device is. Yes I know, "ip route" is better than "route", but still did not got used to use it. -- Andreas https://news-commentaries.blogspot.com/
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-23 16:39 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <k37o0pFnkh4U2@mid.individual.net> |
| In reply to | #36803 |
On 2023-01-23 04:37, Andreas Kohlbach wrote:
> On Sun, 22 Jan 2023 17:18:19 -0800 (PST), Steve Mysterious wrote:
>>
>> On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote:
>>> Assuming this is still correct:
>>> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png>
>>
>> It is.
>>
>>
>>> Basically you need to issue the command "ip addr" and "route". You will
>>> probably not have an IP in the range 192.168.1.* nor a route to that
>>> range. In order to connect to your router at 192.168.1.1 you first need
>>> a route to it.
>>
>> I took a look at the manual page for those commands to see what they do.
>>
>> Are you saying I can make a route to 192.168.1.1 and my router?
>
> That's all odd. Shouldn't DNS not take care of everything? Or is that
> box so old it doesn't know what DNS is?
I guess you mean DHCP.
No, most probably the router intentionally will not publish the lan
interface.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2023-01-23 19:13 -0500 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <875ycwyekn.fsf@usenet.ankman.de> |
| In reply to | #36810 |
On Mon, 23 Jan 2023 16:39:05 +0100, Carlos E. R. wrote: > > On 2023-01-23 04:37, Andreas Kohlbach wrote: >> On Sun, 22 Jan 2023 17:18:19 -0800 (PST), Steve Mysterious wrote: >>> >>> Are you saying I can make a route to 192.168.1.1 and my router? >> That's all odd. Shouldn't DNS not take care of everything? Or is >> that >> box so old it doesn't know what DNS is? > > I guess you mean DHCP. Yes, sorry. > No, most probably the router intentionally will not publish the lan > interface. Publish where? -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-01-24 02:29 +0100 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <0to3ajxkcp.ln2@Telcontar.valinor> |
| In reply to | #36812 |
On 2023-01-24 01:13, Andreas Kohlbach wrote: > On Mon, 23 Jan 2023 16:39:05 +0100, Carlos E. R. wrote: >> >> On 2023-01-23 04:37, Andreas Kohlbach wrote: >>> On Sun, 22 Jan 2023 17:18:19 -0800 (PST), Steve Mysterious wrote: >>>> >>>> Are you saying I can make a route to 192.168.1.1 and my router? >>> That's all odd. Shouldn't DNS not take care of everything? Or is >>> that >>> box so old it doesn't know what DNS is? >> >> I guess you mean DHCP. > > Yes, sorry. > >> No, most probably the router intentionally will not publish the lan >> interface. > > Publish where? Over DHCP. The router, which is giving a public IP (216.15.0.143), will not also give a private (LAN) IP (on 192.168.1.*) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2023-01-23 05:43 +0000 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <tql6qo$3gf1q$1@dont-email.me> |
| In reply to | #36797 |
On 23/01/2023 01:18, Steve Mysterious wrote: > On Sunday, January 22, 2023 at 2:14:38 PM UTC-5, Carlos E.R. wrote: >> Assuming this is still correct: >> <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> > > It is. > > >> Basically you need to issue the command "ip addr" and "route". You will >> probably not have an IP in the range 192.168.1.* nor a route to that >> range. In order to connect to your router at 192.168.1.1 you first need >> a route to it. > > I took a look at the manual page for those commands to see what they do. > > Are you saying I can make a route to 192.168.1.1 and my router? > > If so, can you point me to a link that will teach me how to do that? > > Happy Monday A good start is to make sure the PC is plugged into a LAN port first Then DHCP will do the rest -- I would rather have questions that cannot be answered... ...than to have answers that cannot be questioned Richard Feynman
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2023-01-22 22:31 -0500 |
| Subject | Re: Slightly Off Topic: Router Issues |
| Message-ID | <87fsc2yljb.fsf@usenet.ankman.de> |
| In reply to | #36795 |
On Sun, 22 Jan 2023 20:09:31 +0100, Carlos E.R. wrote: > > On 2023-01-22 18:12, Steve Mysterious wrote: >> Update. >> I contacted the company that made my router. >> The support person led me through all of the things you guys >> suggested. No luck. >> The support person concluded by process of elimination that there >> must be something off with my computer settings. >> I was grateful when she didn't dump me the moment I told her I was >> running Linux. :-) >> I do appreciate all of the effort you guys gave me in trying to >> figure this out, so I decided to post to let you >> know how things ended. > > Assuming this is still correct: > <https://i.paste.pics/5e2cb347c08743e31475fe8e3155eb58.png> Just checked mine (MATE desktop) after I see yours now. Here (Ethernet connection) I find an option "Link Negotiation" which is set to "ignore". What does this do? Somewhat improves things (not that I can complain) to change the setting? -- Andreas
[toc] | [prev] | [next] | [standalone]
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web