Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E. R." Newsgroups: comp.os.linux.misc Subject: Re: Slightly Off Topic: Router Issues Date: Mon, 23 Jan 2023 16:39:05 +0100 Lines: 31 Message-ID: References: <0699e1fc-40b7-4c79-bac9-160397852d2fn@googlegroups.com> <5450be04-83e9-4f3e-a9aa-6198fe173227n@googlegroups.com> <87cz75zztu.fsf@usenet.ankman.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Ms/KcErLBGGMtMSeH9ZVxgUfkmjfl5KxatPEt2Jqiu2esgK0XS Cancel-Lock: sha1:KB0ymFZmZdQ97k5FEATjWLhsKVA= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Content-Language: en-US In-Reply-To: <87cz75zztu.fsf@usenet.ankman.de> Xref: csiph.com comp.os.linux.misc:36810 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: >>> >> >> 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.