Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu!


computers / comp.misc / Re: Network is unreachable - VM

SubjectAuthor
* Network is unreachable - VMAdrian
`* Re: Network is unreachable - VMMarco Moock
 `* Re: Network is unreachable - VMAdrian
  `* Re: Network is unreachable - VMMarco Moock
   +* Re: Network is unreachable - VMSH
   |+- Re: Network is unreachable - VMMarco Moock
   |`* Re: Network is unreachable - VMAdrian
   | `* Re: Network is unreachable - VMSH
   |  `* Re: Network is unreachable - VMAdrian
   |   `* Re: Network is unreachable - VMDan Purgert
   |    +* Re: Network is unreachable - VMMarco Moock
   |    |`* Re: Network is unreachable - VMDan Purgert
   |    | `- Re: Network is unreachable - VMMarco Moock
   |    `* Re: Network is unreachable - VMAdrian
   |     `* Re: Network is unreachable - VMMarco Moock
   |      `* Re: Network is unreachable - VMAdrian
   |       `* Re: Network is unreachable - VMMarco Moock
   |        `- Re: Network is unreachable - VMAdrian
   `* Re: Network is unreachable - VMAdrian
    `* Re: Network is unreachable - VMMarco Moock
     `* Re: Network is unreachable - VMAdrian
      `* Re: Network is unreachable - VMMarco Moock
       `* Re: Network is unreachable - VMAdrian
        +* Re: Network is unreachable - VMDan Purgert
        |+* Re: Network is unreachable - VMAdrian
        ||`- Re: Network is unreachable - VMMarco Moock
        |`- Re: Network is unreachable - VMMarco Moock
        +* Re: Network is unreachable - VMMarco Moock
        |`* Re: Network is unreachable - VMAdrian
        | `* Re: Network is unreachable - VMMarco Moock
        |  `* Re: Network is unreachable - VMAdrian
        |   `* Re: Network is unreachable - VMMarco Moock
        |    `* Re: Network is unreachable - VMAdrian
        |     `* Re: Network is unreachable - VMMarco Moock
        |      `* Re: Network is unreachable - VMAdrian
        |       `* Re: Network is unreachable - VMMarco Moock
        |        `* Re: Network is unreachable - VMAdrian
        |         +* Re: Network is unreachable - VMAndy Burns
        |         |`- Re: Network is unreachable - VMAdrian
        |         `* Re: Network is unreachable - VMMarco Moock
        |          `* Re: Network is unreachable - VMAdrian
        |           `* Re: Network is unreachable - VMMarco Moock
        |            `* Re: Network is unreachable - VMAdrian
        |             `* Re: Network is unreachable - VMMarco Moock
        |              `- Re: Network is unreachable - VMAdrian
        `* Re: Network is unreachable - VMAndy Burns
         `- Re: Network is unreachable - VMAdrian

Pages:12
Network is unreachable - VM

<nOihx1FQcRzjFw7Y@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2194&group=comp.misc#2194

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Network is unreachable - VM
Date: Sun, 22 Jan 2023 10:59:28 +0000
Organization: Occasionally
Lines: 23
Message-ID: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="293d484ac2e8136732c231df862638d9";
logging-data="3246834"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+5gPhGDQHi4V6DOMJD0OqY0pEPIHnU5lA="
User-Agent: Turnpike/6.07-M (<r6+zPRQn$wjFTEseE90aFWVMqv>)
Cancel-Lock: sha1:BZaGyH9TOufkd7Gs/KNfPfdacBk=
 by: Adrian - Sun, 22 Jan 2023 10:59 UTC

This is not a new installation problem.

I've had a CentOS VM running under Oracle's Virtual Box for the best
part of 4 years, and it has done so without a problem. Until yesterday.

I installed a new router yesterday, and since then the CentOS VM
(currently running 7.9) has been unable to access any part of my
network, and so be extension the Internet. Any attempt to do so comes
up with variations on the "Network is unreachable" message. I though I
had ifconfig installed, but trying to run that gives me "command not
found".

Given that I can't install any extra software, any suggestions on how to
fix this ?

TIA

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqjb3n$33uvr$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2195&group=comp.misc#2195

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 13:44:39 +0100
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <tqjb3n$33uvr$1@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 22 Jan 2023 12:44:39 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="561bae1880c87189bb1c230dc5962912";
logging-data="3275771"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/KG0qiFbX/pIja0jI11KA"
Cancel-Lock: sha1:gAzGWOesHQpUSuGi3Jqi2cFbEaE=
 by: Marco Moock - Sun, 22 Jan 2023 12:44 UTC

Am 22.01.2023 um 10:59:28 Uhr schrieb Adrian:

> Given that I can't install any extra software, any suggestions on how
> to fix this ?

Make sure the NIC of the VM is connected as a network bridge in VBox.

Show the output of

ip a
ip -6 route show
ip -4 route show

Re: Network is unreachable - VM

<9fE3V4LJlTzjFw41@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2196&group=comp.misc#2196

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 13:25:29 +0000
Organization: Occasionally
Lines: 57
Message-ID: <9fE3V4LJlTzjFw41@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="293d484ac2e8136732c231df862638d9";
logging-data="3292486"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18TzwOvck8vaivnSa5EipzHQaZQSYPt0Qs="
User-Agent: Turnpike/6.07-M (<$J1zPd3T$wz3cFserp3aFGYjUK>)
Cancel-Lock: sha1:I4FRijfOsZ6LaJFo4IE1ibjVrug=
 by: Adrian - Sun, 22 Jan 2023 13:25 UTC

In message <tqjb3n$33uvr$1@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 22.01.2023 um 10:59:28 Uhr schrieb Adrian:
>
>> Given that I can't install any extra software, any suggestions on how
>> to fix this ?
>
>Make sure the NIC of the VM is connected as a network bridge in VBox.
>

Thanks

I have two VMs running (one W10/32 one CentOS), both appear to have the
same settings. The W10/32 works fine, I'm posting this from that VM.

>Show the output of
>
>ip a

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether 08:00:27:6f:0b:15 brd ff:ff:ff:ff:ff:ff
$ >ip -6 route show

$ ip -6 route show
unreachable ::/96 dev lo metric 1024 error -113 pref medium
unreachable ::/ffff:0.0.0.0/96 dev lo metric 1024 error -113 pref medium
unreachable 2002:a00::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:7f00::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:a9fe::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:ac10::/28 dev lo metric 1024 error -113 pref medium
unreachable 2002:c0a8::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:e000::/19 dev lo metric 1024 error -113 pref medium
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -113 pref medium
$ >ip -4 route show

$ ip -4 route show
$

Last command returns nothing.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqjtqt$36tmg$3@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2198&group=comp.misc#2198

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 19:04:13 +0100
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <tqjtqt$36tmg$3@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 22 Jan 2023 18:04:13 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="561bae1880c87189bb1c230dc5962912";
logging-data="3372752"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18p2NFTN/D404B+NQeGdryn"
Cancel-Lock: sha1:YXcMQ3da4Ql0LKonp2Oe+H+9skA=
 by: Marco Moock - Sun, 22 Jan 2023 18:04 UTC

Am 22.01.2023 um 13:25:29 Uhr schrieb Adrian:

> I have two VMs running (one W10/32 one CentOS), both appear to have
> the same settings. The W10/32 works fine, I'm posting this from that
> VM.

Please check the settings.

> 2: enp0s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> pfifo_fast state DOWN group default qlen 1000
^^^^

That means the NIC isn't active. Check VBox if it is "connected". VBox
can virtually disconnect a NIC of VM, like pulling the cable on a
physical machine.

Next question is:
How is your network managed in the virtual OS?

Re: Network is unreachable - VM

<tqjv4c$70f$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2199&group=comp.misc#2199

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!aioe.org!ok3HMNHmsIv5MlSBB73KNg.user.46.165.242.75.POSTED!not-for-mail
From: i.love.s...@spam.com (SH)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 18:26:21 +0000
Organization: Aioe.org NNTP Server
Message-ID: <tqjv4c$70f$1@gioia.aioe.org>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="7183"; posting-host="ok3HMNHmsIv5MlSBB73KNg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.6.1
X-Notice: Filtered by postfilter v. 0.9.2
 by: SH - Sun, 22 Jan 2023 18:26 UTC

On 22/01/2023 18:04, Marco Moock wrote:
> Am 22.01.2023 um 13:25:29 Uhr schrieb Adrian:
>
>> I have two VMs running (one W10/32 one CentOS), both appear to have
>> the same settings. The W10/32 works fine, I'm posting this from that
>> VM.
>
> Please check the settings.
>
>> 2: enp0s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>> pfifo_fast state DOWN group default qlen 1000
> ^^^^
>
> That means the NIC isn't active. Check VBox if it is "connected". VBox
> can virtually disconnect a NIC of VM, like pulling the cable on a
> physical machine.
>
> Next question is:
> How is your network managed in the virtual OS?
>

Is the new router IP different to the old router IP?

some routers use 192.168.0.1 and others use 192.168.1.1 and some other
routers use completely different IP addresses

Routers usually offer DHCP as well giving the DNS IPs

Now what I think has happened is that Oracle's VBox simply needs to be
told the new router's IP address?

Alternatively, has the physical IP of the machine hosting the VM's
changed? The VMs may still think the host machine still has the old IP
(that was given out by the old router) and simply need to be told what
the host machine's new IP is that is given out by new router?

Re: Network is unreachable - VM

<tqk052$36tmg$4@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2200&group=comp.misc#2200

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 19:43:46 +0100
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <tqk052$36tmg$4@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 22 Jan 2023 18:43:46 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="561bae1880c87189bb1c230dc5962912";
logging-data="3372752"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/CDbqOTg8FVncG+sPp6Bbx"
Cancel-Lock: sha1:qyF4QMBRNXN8SxFr3E7E8TwiI8k=
 by: Marco Moock - Sun, 22 Jan 2023 18:43 UTC

Am 22.01.2023 um 18:26:21 Uhr schrieb SH:

> Now what I think has happened is that Oracle's VBox simply needs to
> be told the new router's IP address?

No. The virtual NIC need to be bridged with the physical NIC. Then it
haves like a switch and the computer is like a physical computer in the
normal network.

Re: Network is unreachable - VM

<$CunyCTgpYzjFwI4@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2201&group=comp.misc#2201

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 19:11:28 +0000
Organization: Occasionally
Lines: 30
Message-ID: <$CunyCTgpYzjFwI4@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="293d484ac2e8136732c231df862638d9";
logging-data="3398229"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19yCSXyM7tKyqv9Abo9VwLvZecqjstMTCc="
User-Agent: Turnpike/6.07-M (<n76zPVBv$wjEXHseUx1aFmRcor>)
Cancel-Lock: sha1:wAQuofwTbHB8UmkIYgPacvMbEZ8=
 by: Adrian - Sun, 22 Jan 2023 19:11 UTC

In message <tqjtqt$36tmg$3@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 22.01.2023 um 13:25:29 Uhr schrieb Adrian:
>
>> I have two VMs running (one W10/32 one CentOS), both appear to have
>> the same settings. The W10/32 works fine, I'm posting this from that
>> VM.
>
>Please check the settings.
>

Looking under "advanced settings", I find that the is a tick box for
"Cable connected". This was unticked. I've now ticked it, and I'm back
on the network, well sort of.

ip a now shows Up rather than down, and I can ping external sites, but I
can't ping any local (i.e. on my LAN) machines by name, but can by ip
address. So something somewhere means that I've lost the DNS settings.

>Next question is:
>How is your network managed in the virtual OS?

Sorry, I don't know, and I'm not sure how to find out.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<QzV8OIUP0YzjFwvP@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2202&group=comp.misc#2202

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 19:22:55 +0000
Organization: Occasionally
Lines: 38
Message-ID: <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="293d484ac2e8136732c231df862638d9";
logging-data="3404559"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18F3OhNb/fOF1Z7KJkpeJ/H4WWV+xHo28s="
User-Agent: Turnpike/6.07-M (<DY$zPZev$wTlbGsemF0aF2fKoD>)
Cancel-Lock: sha1:tzR9zpBmtROCOER3zqr+kA0xc84=
 by: Adrian - Sun, 22 Jan 2023 19:22 UTC

In message <tqjv4c$70f$1@gioia.aioe.org>, SH <i.love.spam@spam.com>
writes
>Is the new router IP different to the old router IP?
>
No. The new router was set up using the same ip address as the old one.
In part this was to try and avoid problems like this.

>Now what I think has happened is that Oracle's VBox simply needs to be
>told the new router's IP address?
>

I don't argue with that. However what is confusing me is that I've got
two VBox VMs (the CentOS one and a Windows10/32 one). The CentOS one
had completely fallen off the network (now fixed, see another post in
the thread), but the Windows one didn't. Additionally, I can't see
anything in the VM set up (that is from the VM's window menus, rather
than settings under /etc) that allows you to do that.

Basically, now I can reach the Internet, however, I can only access
machines on my LAN by their IP address, the local DNS lookup has stopped
working.

>Alternatively, has the physical IP of the machine hosting the VM's
>changed? The VMs may still think the host machine still has the old IP
>(that was given out by the old router) and simply need to be told what
>the host machine's new IP is that is given out by new router?
>

All machines on my LAN are given fixed leases at the router (and that
information was ported to the new router), so they should retain their
IP addresses.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqk9cp$2h8ao$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2203&group=comp.misc#2203

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: i.l...@spam.com (SH)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 21:21:30 +0000
Organization: A noiseless patient Spider
Lines: 52
Message-ID: <tqk9cp$2h8ao$1@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 22 Jan 2023 21:21:29 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="0032dfcf1dd91188e4f58c4d8fabcaf3";
logging-data="2662744"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX195m/xxYM/fq2Xe+ouxL7B8LLx8GnQRmw4="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.6.1
Cancel-Lock: sha1:V2k+xnT1lwCtUFABuFM9+5W3idE=
In-Reply-To: <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
 by: SH - Sun, 22 Jan 2023 21:21 UTC

On 22/01/2023 19:22, Adrian wrote:
> In message <tqjv4c$70f$1@gioia.aioe.org>, SH <i.love.spam@spam.com> writes
>> Is the new router IP different to the old router IP?
>>
> No.  The new router was set up using the same ip address as the old one.
> In part this was to try and avoid problems like this.
>
>> Now what I think has happened is that Oracle's VBox simply needs to be
>> told the new router's IP address?
>>
>
> I don't argue with that.  However what is confusing me is that I've got
> two VBox VMs (the CentOS one and a Windows10/32 one).  The CentOS one
> had completely fallen off the network (now fixed, see another post in
> the thread), but the Windows one didn't.  Additionally, I can't see
> anything in the VM set up (that is from the VM's window menus, rather
> than settings under /etc) that allows you to do that.
>
> Basically, now I can reach the Internet, however, I can only access
> machines on my LAN by their IP address, the local DNS lookup has stopped
> working.

Ah.... you're missing a hosts file? this has FDQN (fully qualified
domain names) vs IP addresses.

Did you have a list in the old router where you could type in the FQDN
name and the machine would get the IP address from the hosts file.

For externals, this would use DNS, but for internals, that uses a hosts
file. Perhaps the new router needs a bit more info?

I run my own DNS (pi Hole) and I put my local machine names and IP
addresses in there to save me messing about creating a hosts file on
every PC and knowing that external DNS won't know about my internal network.

S.

>> Alternatively, has the physical IP of the machine hosting the VM's
>> changed? The VMs may still think the host machine still has the old IP
>> (that was given out by the old router) and simply need to be told what
>> the host machine's new IP is that is given out by new router?
>>
>
> All machines on my LAN are given fixed leases at the router (and that
> information was ported to the new router), so they should retain their
> IP addresses.
>
> Adrian

Re: Network is unreachable - VM

<6T622Hax9bzjFw5V@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2205&group=comp.misc#2205

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Sun, 22 Jan 2023 22:57:53 +0000
Organization: Occasionally
Lines: 71
Message-ID: <6T622Hax9bzjFw5V@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1;format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: reader01.eternal-september.org; posting-host="c7ef5c439a48d6e59a3c401d9384bf2e";
logging-data="3472744"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ehXt6GIhzhq6xCPLzu4rqSmUz5KaCoS4="
User-Agent: Turnpike/6.07-M (<bv8zPFYT$wDRUEseJdxaFWCFcC>)
Cancel-Lock: sha1:vHFzUpe/qBMaHw1HD6gEkn5q7U0=
 by: Adrian - Sun, 22 Jan 2023 22:57 UTC

In message <tqk9cp$2h8ao$1@dont-email.me>, SH <i.love@spam.com> writes
>On 22/01/2023 19:22, Adrian wrote:
>> In message <tqjv4c$70f$1@gioia.aioe.org>, SH <i.love.spam@spam.com> writes
>>> Is the new router IP different to the old router IP?
>>>
>> No.  The new router was set up using the same ip address as the old
>>one. In part this was to try and avoid problems like this.
>>
>>> Now what I think has happened is that Oracle's VBox simply needs to
>>>be told the new router's IP address?
>>>
>> I don't argue with that.  However what is confusing me is that I've
>>got two VBox VMs (the CentOS one and a Windows10/32 one).  The CentOS
>>one had completely fallen off the network (now fixed, see another
>>post in the thread), but the Windows one didn't.  Additionally, I
>>can't see anything in the VM set up (that is from the VM's window
>>menus, rather than settings under /etc) that allows you to do that.
>> Basically, now I can reach the Internet, however, I can only access
>>machines on my LAN by their IP address, the local DNS lookup has
>>stopped working.
>
>Ah.... you're missing a hosts file? this has FDQN (fully qualified
>domain names) vs IP addresses.
>

Pedantically, I'm not missing one, but whether or not it has the right
info in it is a different matter.

>Did you have a list in the old router where you could type in the FQDN
>name and the machine would get the IP address from the hosts file.
>

The old router (and the new one, which is basically a newer version) has
the ability to put in IP addresses, names and MAC addresses for items on
the LAN, but this is fully populated. In addition to the CentOS VM,
I've got a Ubuntu PC and a stack of RPis, and they all happily work with
out any mods to the hosts file (and they basically hold the default info
for that box , references to 127.0.0.1). What has changed with the new
router is that now the various RPis no longer accept "machine_name", but
now need "machine_name.local" for ping or ssh to find the machine in
question (the Ubuntu box always did). I added another RPi to the LAN
this afternoon, and without editing anything, I was able to access it by
name straight away.
The router appears to pickup the machine name from the machine in
question, and doesn't have the ".local" bit in its version of the hosts
table.

>For externals, this would use DNS, but for internals, that uses a hosts
>file. Perhaps the new router needs a bit more info?

In view of the above para, I'm not convinced that the problem is the
router, I think it is how the VM accesses (or doesn't) the router for
LAN destinations. Changing the router seems to have upset the VM
(witness it "unplugging" itself.

>
>I run my own DNS (pi Hole) and I put my local machine names and IP
>addresses in there to save me messing about creating a hosts file on
>every PC and knowing that external DNS won't know about my internal
>network.

This is something that I've only ever done on the router. I suspect
that strictly speaking I don't need to do it there, but that is to
ensure that each machine keeps the same IP address.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqljq7$3i3r8$6@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2208&group=comp.misc#2208

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Mon, 23 Jan 2023 10:25:27 +0100
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <tqljq7$3i3r8$6@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 23 Jan 2023 09:25:27 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="0f4e6e3e4087703c94f6affa9824d895";
logging-data="3739496"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18jQ/IVVvcQdBjMXhHBuZ17"
Cancel-Lock: sha1:VEvqH0t4DDNrgOcASR5s6yuDUXs=
 by: Marco Moock - Mon, 23 Jan 2023 09:25 UTC

Am 22.01.2023 um 19:11:28 Uhr schrieb Adrian:

> Looking under "advanced settings", I find that the is a tick box for
> "Cable connected". This was unticked. I've now ticked it, and I'm
> back on the network, well sort of.
>
> ip a now shows Up rather than down, and I can ping external sites,
> but I can't ping any local (i.e. on my LAN) machines by name, but can
> by ip address. So something somewhere means that I've lost the DNS
> settings.

Is the NIC in the VBox settings connected via Bridge and NOT NAT?
NAT breaks certain things here, don't use it.

Re: Network is unreachable - VM

<7HI6fCPoeqzjFwJn@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2210&group=comp.misc#2210

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Mon, 23 Jan 2023 15:28:40 +0000
Organization: Occasionally
Lines: 28
Message-ID: <7HI6fCPoeqzjFwJn@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff> <tqljq7$3i3r8$6@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="c7ef5c439a48d6e59a3c401d9384bf2e";
logging-data="3868682"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18dGYOIqrw+yKoWQlOvMaBk1TJpIBPAYB8="
User-Agent: Turnpike/6.07-M (<XPzzPFv7$wTyWHseTBzaFmC7Em>)
Cancel-Lock: sha1:O8L6VuYzBShVj0VeKhP1qRMb1xk=
 by: Adrian - Mon, 23 Jan 2023 15:28 UTC

In message <tqljq7$3i3r8$6@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 22.01.2023 um 19:11:28 Uhr schrieb Adrian:
>
>> Looking under "advanced settings", I find that the is a tick box for
>> "Cable connected". This was unticked. I've now ticked it, and I'm
>> back on the network, well sort of.
>>
>> ip a now shows Up rather than down, and I can ping external sites,
>> but I can't ping any local (i.e. on my LAN) machines by name, but can
>> by ip address. So something somewhere means that I've lost the DNS
>> settings.
>
>Is the NIC in the VBox settings connected via Bridge and NOT NAT?
>NAT breaks certain things here, don't use it.
>

Curious. The only setting that seems to work here is NAT.

If I set it to anything else, I can't ping Internet sites by name. With
NAT set I can ping Internet sites by name, and LAN sites by IP address.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqmqmn$3op39$3@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2211&group=comp.misc#2211

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Mon, 23 Jan 2023 21:29:11 +0100
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <tqmqmn$3op39$3@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff>
<tqljq7$3i3r8$6@dont-email.me>
<7HI6fCPoeqzjFwJn@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 23 Jan 2023 20:29:11 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="0f4e6e3e4087703c94f6affa9824d895";
logging-data="3957865"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/OJz8oXzPPaAOQy708oF47"
Cancel-Lock: sha1:kY2L2q0QPkymvTVvyi4FFzLsOBM=
 by: Marco Moock - Mon, 23 Jan 2023 20:29 UTC

Am 23.01.2023 um 15:28:40 Uhr schrieb Adrian:

> Curious. The only setting that seems to work here is NAT.
>
> If I set it to anything else, I can't ping Internet sites by name.
> With NAT set I can ping Internet sites by name, and LAN sites by IP
> address.

Set it to Bridge, disconnect the virtual NIC, the connect it again.
You also need to select the physical NIC you actually use at the
computer in VBox.

https://picr.eu/images/2023/01/23/Mn7Hh.png

Re: Network is unreachable - VM

<slrntsvcrs.304.dan@djph.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2213&group=comp.misc#2213

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: dan...@djph.net (Dan Purgert)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 10:30:26 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 65
Message-ID: <slrntsvcrs.304.dan@djph.net>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me> <6T622Hax9bzjFw5V@ku.gro.lloiff>
Injection-Date: Tue, 24 Jan 2023 10:30:26 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="569928bd638f52d0b202a772ff7ae1c0";
logging-data="113517"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19BENIJEvdETcgjiQzogqactYpgGC1uJt8="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:I2fWIAqUdSDrM5ZqEu79wdqH4X8=
X-PGP-KeyID: 0x4CE72860
 by: Dan Purgert - Tue, 24 Jan 2023 10:30 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-01-22, Adrian wrote:
> In message <tqk9cp$2h8ao$1@dont-email.me>, SH <i.love@spam.com> writes
>>Did you have a list in the old router where you could type in the FQDN
>>name and the machine would get the IP address from the hosts file.
>>
>
> The old router (and the new one, which is basically a newer version) has
> the ability to put in IP addresses, names and MAC addresses for items on
> the LAN, but this is fully populated. In addition to the CentOS VM,
> I've got a Ubuntu PC and a stack of RPis, and they all happily work with
> out any mods to the hosts file (and they basically hold the default info
> for that box , references to 127.0.0.1). What has changed with the new
> router is that now the various RPis no longer accept "machine_name", but
> now need "machine_name.local" for ping or ssh to find the machine in
> question (the Ubuntu box always did). I added another RPi to the LAN
> this afternoon, and without editing anything, I was able to access it by
> name straight away.
> The router appears to pickup the machine name from the machine in
> question, and doesn't have the ".local" bit in its version of the hosts
> table.

That's mDNS. Sounds like you lost the search-domain for ".local" as
part of the upgrade cycle. That is, the previous router had some
setting that applied the ".local" TLD to non-FQDN hostnames.

>
>>I run my own DNS (pi Hole) and I put my local machine names and IP
>>addresses in there to save me messing about creating a hosts file on
>>every PC and knowing that external DNS won't know about my internal
>>network.
>
> This is something that I've only ever done on the router. I suspect
> that strictly speaking I don't need to do it there, but that is to
> ensure that each machine keeps the same IP address.

DNS has nothing to do with IP address assignments to a host. It is
merely the translator of a given hostname to the machine's assigned IP
address.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPPs3wACgkQbWVw5Uzn
KGDpaw//UJNmBr1/j8mex/egfAbJHNdUTwAFBI0d7GljGj6p13ntyrTlG8Wuvhu/
xi1ZKFcyUOGd2ztu0h/GO/JegThy7CC+RHs5Ol7+8FDjgz/gzW/pxbIk7YH5qQqq
TGp4Mie60AeZFFe9eYhYoZp4d0s/vGg9XUCqda342P1IbCkXhOCLdiV4VmfT2lzB
MBR7RkwK1RqYdtjeqoIeOFQmM+XhFhSVL8aBPJV7eCktqjGB2mhaBxZP3d3uVlEg
naNpipuoggUXddzKbLJQObmQ9XvuaFT/Rf5DOIBryt+baOB/SqUgvgklXTpjdytO
+IiaEAmSqg1YaaRm2GsOOMVYfeXnzxa/VTfra3KIzD/8j6vabHRjb+LOV9Uq0buE
aeFwl8ZVzP+Agd7KCMgVAvsbR7d9gbIgvN4ig8TMK14IJRoM7gcEdRD2wRNW9pwP
SV2NJkSyctBb9zD7K1d/wkSQgw7ay9vhfIC0HORXHKOA/JqKmaRJyBaj5grxBea2
YDLVtnrb8dSNJn697mp7kJJnNJ6BlGMmeQoNAAbPeSTur0KL9EDS4LeQdc+027Zl
KgjDr9ZCRxWreH7ABpOdZ8KS6w+SBmsh3OuGYgNMWJtnp7OGaRkGLhJs5WhDkvF+
bbonDSGfJ6V5cAdA6tWj6eL62rv05Mp4YAP79Incf5lqe2/+U18=
=tD19
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Re: Network is unreachable - VM

<LH2NjEGGS7zjFweR@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2214&group=comp.misc#2214

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 10:35:50 +0000
Organization: Occasionally
Lines: 42
Message-ID: <LH2NjEGGS7zjFweR@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff> <tqljq7$3i3r8$6@dont-email.me>
<7HI6fCPoeqzjFwJn@ku.gro.lloiff> <tqmqmn$3op39$3@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="f5b3f2500b7231f3976f52428233ae94";
logging-data="123974"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18BPGJSI+GBKscK8EX7D6QI4ZvaMPitPF0="
User-Agent: Turnpike/6.07-M (<Pw6zP5Jn$wDE7Fse0Z8aFG$c59>)
Cancel-Lock: sha1:mMnav5ThCXaGtPui3VwWXv+GEWo=
 by: Adrian - Tue, 24 Jan 2023 10:35 UTC

In message <tqmqmn$3op39$3@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 23.01.2023 um 15:28:40 Uhr schrieb Adrian:
>
>> Curious. The only setting that seems to work here is NAT.
>>
>> If I set it to anything else, I can't ping Internet sites by name.
>> With NAT set I can ping Internet sites by name, and LAN sites by IP
>> address.
>
>Set it to Bridge, disconnect the virtual NIC, the connect it again.
>You also need to select the physical NIC you actually use at the
>computer in VBox.
>
>https://picr.eu/images/2023/01/23/Mn7Hh.png
>

Thanks

This is not what I'm seeing. When I open up the settings and select
network, I can see "Bridged Adapter", but the "Enable Network Adapter"
box is greyed out. No option seems to allow me to tick/un tick that
box.

With Bridged Adapter selected, under Name, I have three options :

RealtekPCIe GbE Family Controller (which is the default)
Qualcomm QCA9565 802.11b/g/n Wireless Adapter
VirtualBox Host-Only Ethernet Adapter

There is no option to enter the NIC that I'm using (enp0s3)

As an experiment last night, I swapped back to my old router, and with
that the VM worked as I expected it to, without changing any settings.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqocka$2tlc$9@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2215&group=comp.misc#2215

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 11:41:14 +0100
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <tqocka$2tlc$9@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
<QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me>
<6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 24 Jan 2023 10:41:14 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1dcf83a5c5efb0722b11517ef0c4aff6";
logging-data="95916"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+NtJVPNilLLwQRZOHYs7Ch"
Cancel-Lock: sha1:osW866x70hbUS6odBlheSqada2o=
 by: Marco Moock - Tue, 24 Jan 2023 10:41 UTC

Am 24.01.2023 um 10:30:26 Uhr schrieb Dan Purgert:

> That's mDNS. Sounds like you lost the search-domain for ".local" as
> part of the upgrade cycle. That is, the previous router had some
> setting that applied the ".local" TLD to non-FQDN hostnames.

Wrong.

..local is mDNS and will be used with IPv4/IPv6 multicast link local
addresses, regardless if a router is present or not.

Although mDNS uses link-local multicast, it only works on the same
Ethernet link, NAT breaks that as I already pointed out.

Re: Network is unreachable - VM

<1HYCDnG+k7zjFwYO@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2216&group=comp.misc#2216

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 10:55:58 +0000
Organization: Occasionally
Lines: 57
Message-ID: <1HYCDnG+k7zjFwYO@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me> <6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="f5b3f2500b7231f3976f52428233ae94";
logging-data="130585"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19QwktY5f17JviMI239nhWH0JNOAsp/BLQ="
User-Agent: Turnpike/6.07-M (<rRwzP9iH$wjm9Ese+9$aFW52fw>)
Cancel-Lock: sha1:EyKoO/X0KsT9sfZeDXuwpp4mC3E=
 by: Adrian - Tue, 24 Jan 2023 10:55 UTC

In message <slrntsvcrs.304.dan@djph.net>, Dan Purgert <dan@djph.net>
writes
>On 2023-01-22, Adrian wrote:
>> In message <tqk9cp$2h8ao$1@dont-email.me>, SH <i.love@spam.com> writes
>>>Did you have a list in the old router where you could type in the FQDN
>>>name and the machine would get the IP address from the hosts file.
>>>
>>
>> The old router (and the new one, which is basically a newer version) has
>> the ability to put in IP addresses, names and MAC addresses for items on
>> the LAN, but this is fully populated. In addition to the CentOS VM,
>> I've got a Ubuntu PC and a stack of RPis, and they all happily work with
>> out any mods to the hosts file (and they basically hold the default info
>> for that box , references to 127.0.0.1). What has changed with the new
>> router is that now the various RPis no longer accept "machine_name", but
>> now need "machine_name.local" for ping or ssh to find the machine in
>> question (the Ubuntu box always did). I added another RPi to the LAN
>> this afternoon, and without editing anything, I was able to access it by
>> name straight away.
>> The router appears to pickup the machine name from the machine in
>> question, and doesn't have the ".local" bit in its version of the hosts
>> table.
>
>That's mDNS. Sounds like you lost the search-domain for ".local" as
>part of the upgrade cycle. That is, the previous router had some
>setting that applied the ".local" TLD to non-FQDN hostnames.

In the grand scheme of things, that doesn't matter as much, so long as
it is consistent.

>
>
>>
>>>I run my own DNS (pi Hole) and I put my local machine names and IP
>>>addresses in there to save me messing about creating a hosts file on
>>>every PC and knowing that external DNS won't know about my internal
>>>network.
>>
>> This is something that I've only ever done on the router. I suspect
>> that strictly speaking I don't need to do it there, but that is to
>> ensure that each machine keeps the same IP address.
>
>DNS has nothing to do with IP address assignments to a host. It is
>merely the translator of a given hostname to the machine's assigned IP
>address.

Which isn't working at all from my VM, but does from other (physical)
machines on the LAN. The VM is unable to translate the name of a
machine into an IP address when it is plugged into the new router, but
with the old one, it works fine.

Adrian.
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqoffm$2tlc$10@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2217&group=comp.misc#2217

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 12:29:57 +0100
Organization: A noiseless patient Spider
Lines: 10
Message-ID: <tqoffm$2tlc$10@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
<QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me>
<6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net>
<1HYCDnG+k7zjFwYO@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 24 Jan 2023 11:29:58 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1dcf83a5c5efb0722b11517ef0c4aff6";
logging-data="95916"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18aaYB4cJyezEB8uyVlTiRU"
Cancel-Lock: sha1:xehVZAas1Xz9spbNOJsaFPscqzA=
 by: Marco Moock - Tue, 24 Jan 2023 11:29 UTC

Am 24.01.2023 um 10:55:58 Uhr schrieb Adrian:

> Which isn't working at all from my VM, but does from other (physical)
> machines on the LAN. The VM is unable to translate the name of a
> machine into an IP address when it is plugged into the new router,
> but with the old one, it works fine.

Use Wireshark and capture for dns, LLMNR, mdns and nbns.
Check which protocol will be used.

Re: Network is unreachable - VM

<ciKYqTI0g9zjFw$j@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2218&group=comp.misc#2218

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 13:08:04 +0000
Organization: Occasionally
Lines: 42
Message-ID: <ciKYqTI0g9zjFw$j@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me> <6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net> <1HYCDnG+k7zjFwYO@ku.gro.lloiff>
<tqoffm$2tlc$10@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="f5b3f2500b7231f3976f52428233ae94";
logging-data="173301"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19d4TbCk8l7txk3yuZK2/uJmjqRRavqUF0="
User-Agent: Turnpike/6.07-M (<bx4zP9IX$wDE8Ese4d9aFW6U54>)
Cancel-Lock: sha1:oXA+0PGxD7qPANp65MA/keTBMVY=
 by: Adrian - Tue, 24 Jan 2023 13:08 UTC

In message <tqoffm$2tlc$10@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 24.01.2023 um 10:55:58 Uhr schrieb Adrian:
>
>> Which isn't working at all from my VM, but does from other (physical)
>> machines on the LAN. The VM is unable to translate the name of a
>> machine into an IP address when it is plugged into the new router,
>> but with the old one, it works fine.
>
>Use Wireshark and capture for dns, LLMNR, mdns and nbns.
>Check which protocol will be used.
>
Thanks.

The VM works in console mode only (no window manager installed).

$ tshark &
[1] 1265
$ Capturing on 'enp0s3'
ping -c 1 ffoilpi1.local
ping: ffoilpi1.local: Name or service not know
$ 1 0.000000000 10.0.2.15 -> 217.169.20.20 DNS 74 Standard query
0x97be A ffoilpi1.local
2 0.01177891 217.169.20.20 -> 10.0.2.15 DNS 149 Standard query
response 0x97be No such name
3 0.011954155 10.0.2.15 -> 217.169.20.20 DNS 86 Standard query
0x2c3f A ffoilpi1.local.localdomain
4 0.023462861 217.169.20.20 -> 10.0.2.15 DNS 161 Standard query
response 0x2c3f No such name
$ kill %1
$ 4 packets captured

217.169.20.20 appears in my /etc/resolv.conf as a nameserver.

If more information is needed, please advise on options to use.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqooda$2tlc$16@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2219&group=comp.misc#2219

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 15:02:18 +0100
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <tqooda$2tlc$16@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
<QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me>
<6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net>
<1HYCDnG+k7zjFwYO@ku.gro.lloiff>
<tqoffm$2tlc$10@dont-email.me>
<ciKYqTI0g9zjFw$j@ku.gro.lloiff>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 24 Jan 2023 14:02:18 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1dcf83a5c5efb0722b11517ef0c4aff6";
logging-data="95916"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18KdefkKk3GzePnBlSeHpOO"
Cancel-Lock: sha1:1KM5EUEOryHBSGwOfv+DCSt34O8=
 by: Marco Moock - Tue, 24 Jan 2023 14:02 UTC

Am 24.01.2023 um 13:08:04 Uhr schrieb Adrian:

> 217.169.20.20 appears in my /etc/resolv.conf as a nameserver.
>
> If more information is needed, please advise on options to use.

Again, last time, I don't want to repeat myself:

Is you NIC configured as a bridge in VBox?
Show the output of
ip a

Did you understand that .local is mDNS and not normal Unicast DNS?
What is the content of the /etc/nsswitch.conf?

Is an mDNS client like Avahi or Bonjour running on the target machine?
A service MUST listen on 5353 UDP.

Re: Network is unreachable - VM

<TQ87G2LvW$zjFwch@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2220&group=comp.misc#2220

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 15:13:51 +0000
Organization: Occasionally
Lines: 131
Message-ID: <TQ87G2LvW$zjFwch@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me> <6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net> <1HYCDnG+k7zjFwYO@ku.gro.lloiff>
<tqoffm$2tlc$10@dont-email.me> <ciKYqTI0g9zjFw$j@ku.gro.lloiff>
<tqooda$2tlc$16@dont-email.me>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="f5b3f2500b7231f3976f52428233ae94";
logging-data="215884"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/lwX7aq2GBNTAaSRHcLwvC3mgJZ8j3Q0="
User-Agent: Turnpike/6.07-M (<vh4zP9BD$wjU9Fse959aFG5V9f>)
Cancel-Lock: sha1:AlIykIou58l8muwmK/DF7cqBYM4=
 by: Adrian - Tue, 24 Jan 2023 15:13 UTC

In message <tqooda$2tlc$16@dont-email.me>, Marco Moock <mo01@posteo.de>
writes
>Am 24.01.2023 um 13:08:04 Uhr schrieb Adrian:
>
>> 217.169.20.20 appears in my /etc/resolv.conf as a nameserver.
>>
>> If more information is needed, please advise on options to use.
>
>Again, last time, I don't want to repeat myself:

Sorry if I don't understand all the technical terms.

>
>Is you NIC configured as a bridge in VBox?
Not currently. When I do configure it as a bridge, all ping commands
run very slowly, and they all fail.

>Show the output of
>ip a
>

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 08:00:27:6f:0b:15 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global nopreficroute dynamic
enp0s3
valid_lft 81441sec preferred_lft 81441sec
inet6 fe80::39de:38c5Lc39d:c521/64 scope link noprefixroute
valid_lft forever preferred_lft forever
$

>Did you understand that .local is mDNS and not normal Unicast DNS?
Not entirely. I haven't had time (yet) to look up the definitions in
terms that I understand.

>What is the content of the /etc/nsswitch.conf?
>
# # /etc/nsswitch.conf
# # An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
# # The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
# # Valid entries include:
# # nisplus Use NIS+ (NIS version 3)
# nis Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#

# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
# # Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis

passwd: files sss
shadow: files sss
group: files sss
#initgroups: files sss

#hosts: db files nisplus nis dns
hosts: files dns myhostname

# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files

bootparams: nisplus [NOTFOUND=return] files

ethers: files
netmasks: files
networks: files
protocols: files
rpc: files
services: files sss

netgroup: nisplus sss

publickey: nisplus

automount: files nisplus sss
aliases: files nisplus

>Is an mDNS client like Avahi or Bonjour running on the target machine?

Which is the target machine in this case ? If you mean (for instance)
one of my Raspberry Pis, then no. The router has Bonjour available, but
it has not been enabled.

>A service MUST listen on 5353 UDP.
>
Checking with one of my Pis, netstat -tulp shows

upd6 0 0 :::5353 :::*

The VM does not show 5353

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<slrntsvts9.304.dan@djph.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2221&group=comp.misc#2221

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: dan...@djph.net (Dan Purgert)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 15:20:47 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 52
Message-ID: <slrntsvts9.304.dan@djph.net>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org> <QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me> <6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net> <tqocka$2tlc$9@dont-email.me>
Injection-Date: Tue, 24 Jan 2023 15:20:47 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="569928bd638f52d0b202a772ff7ae1c0";
logging-data="209544"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18QGzYXV7Xr0jGPfnzov+K7j/tVtDYgvcA="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:45W/t2trdlReH2x5Go48cOUW7II=
X-PGP-KeyID: 0x4CE72860
 by: Dan Purgert - Tue, 24 Jan 2023 15:20 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-01-24, Marco Moock wrote:
> Am 24.01.2023 um 10:30:26 Uhr schrieb Dan Purgert:
>
>> That's mDNS. Sounds like you lost the search-domain for ".local" as
>> part of the upgrade cycle. That is, the previous router had some
>> setting that applied the ".local" TLD to non-FQDN hostnames.
>
> Wrong.
>
> .local is mDNS and will be used with IPv4/IPv6 multicast link local
> addresses, regardless if a router is present or not.
>
> Although mDNS uses link-local multicast, it only works on the same
> Ethernet link, NAT breaks that as I already pointed out.

You seem to have misread the interaction.

Old router -> unqualified hostnames (i.e. "rpi3") resolved properly to
hosts on the LAN.
New router -> unqualified hostnames (i.e "rpi3") do not resolve; BUT
their mDNS hostnames (i.e. "rpi3.local") do.

Therefore -> "old router" had been providing the appropriate mDNS
search-domain (".local"). I'd imagine this to be most likely provided
as part of the DHCP options; although it could potentially have been
part of the router's own internal DNS server configuration.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPP94kACgkQbWVw5Uzn
KGDN0hAAjEFdWNnGjUkZdw/t8c7HlCUlqP2ibtGm8/XYbVqAjMPJ+ehzWBV1RSVm
rLgPf/dsGnELAPxagUvES8HKx654gzrUWG7Dkjs3+2NjMNgQXBhrR8zThRx2tkYD
s/YCUOImQEwd9CeB7dj4eAEQUb2CxoVQqSPTwTIf50pvT6qaQp/uu53MIg8q5sWo
cbqzIcgJr1AabOUNjLAqYMSaj242ONWmdqa5mmd5dLoRF4B2ajBfXbBn6BUYkXUk
NW7wzoAZK/T+rqDsQijHIh61Cw6FDBbPo/OoPs54wnSwPdaz/eQJKVRBNrH3+/go
dQRYk0otg88li/hoN6M2WMYBteK3VvDdGDjpx7IOhKFOLfUq79jIvM0nNRZ5GcGK
Q4xk/o4VauNru3LssKU2Ga1qVObI1spu/JFDuNEUJIguDLXU7Ql+c7S/WQNHYIyY
w0agulZRWwqUPgl3sW7+eh1AJbkUhZ9iDM0f1Ulvnw1Bx/UGqKwI7pgiEXpv+A0c
Lhokak7yW1ev/7CgSQo6Wo2OXGUzRhRm6Mj1kAYEfvJSVeXKcZJ1nWBuumA2CW/7
WzqtKGnz+mvm8YvAZe1YoAhriJ2cTowNE3ollvGe6IFYUyPbX+snVLZqDIjDRYoA
+pqkH8cUXCZ71VlU+VDG+mzF7Z9MoN3pKRbQ4b4ppxrO4PFwuKQ=
=C4Q5
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Re: Network is unreachable - VM

<slrntsvuhq.304.dan@djph.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2222&group=comp.misc#2222

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: dan...@djph.net (Dan Purgert)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 15:32:16 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 77
Message-ID: <slrntsvuhq.304.dan@djph.net>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff> <tqljq7$3i3r8$6@dont-email.me>
<7HI6fCPoeqzjFwJn@ku.gro.lloiff> <tqmqmn$3op39$3@dont-email.me>
<LH2NjEGGS7zjFweR@ku.gro.lloiff>
Injection-Date: Tue, 24 Jan 2023 15:32:16 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="569928bd638f52d0b202a772ff7ae1c0";
logging-data="209544"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+SzOAhe4HiDfmalFvF5ICpDhjqQyi5qEk="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:BCMWYxkIRGKCguJr/riHsDsmQ9c=
X-PGP-KeyID: 0x4CE72860
 by: Dan Purgert - Tue, 24 Jan 2023 15:32 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-01-24, Adrian wrote:
> In message <tqmqmn$3op39$3@dont-email.me>, Marco Moock <mo01@posteo.de>
> writes
>>Am 23.01.2023 um 15:28:40 Uhr schrieb Adrian:
>>
>>> Curious. The only setting that seems to work here is NAT.
>>>
>>> If I set it to anything else, I can't ping Internet sites by name.
>>> With NAT set I can ping Internet sites by name, and LAN sites by IP
>>> address.
>>
>>Set it to Bridge, disconnect the virtual NIC, the connect it again.
>>You also need to select the physical NIC you actually use at the
>>computer in VBox.
>>
>>https://picr.eu/images/2023/01/23/Mn7Hh.png
>>
>
> Thanks
>
> This is not what I'm seeing. When I open up the settings and select
> network, I can see "Bridged Adapter", but the "Enable Network Adapter"
> box is greyed out. No option seems to allow me to tick/un tick that
> box.

It's been a long time since I've used vbox; but as I (probably
incorrectly) recall; some of the "greyed out" things were only
accessible if you were running the vbox UI as root (or in a more
permissive vbox-something group).

>
>
> With Bridged Adapter selected, under Name, I have three options :
>
> RealtekPCIe GbE Family Controller (which is the default)
> Qualcomm QCA9565 802.11b/g/n Wireless Adapter
> VirtualBox Host-Only Ethernet Adapter
>
> There is no option to enter the NIC that I'm using (enp0s3)

enp0s3 is just the "name" used by the kernel because that's where it was
enumerated (EtherNet; on PCI Port0, Slot 3). However, that's not the
"device name" as burned into the chip's firmware -- given the options,
it's most likely the Realtek controller there (I'd imagine the atheros
chip will be something like "wlp0s#", where the "#" is some other number)

> As an experiment last night, I swapped back to my old router, and with
> that the VM worked as I expected it to, without changing any settings.

In either case; the VM in question is getting its DNS server information
via DHCP, right? In both cases, is it the IP address of the router?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPP+jkACgkQbWVw5Uzn
KGCNvQ//bct98umzMRT5NaAVelCDhh8UPp22TYZLnFkBuBd5gKJaGjd3W1LzTFq7
rCQRu1X/M5KhnaCYNyufOTSeDrd+5Oa4fNP1WDro42ZEvgeDT8SvJxoIo+uPeczd
dtQjKPUO7Q3GG44ZK8O08ewm5aPlTy1nMKpJfmjpdMbQOuiKl6np6TTvus2H1x5d
MxWyPrwiHmTtsAl0lzgMtOrkQbUBqImL30gufb2afNwSQ6hmQQti+N3pJeUWKMpW
NYewjiWDLv7w393WSX+1h7nnPtgWRl45Q7VFe/mc2VLuJMLdcL+ZqbjWmv7S6ZpB
/IQ1mw025n6o36FvKWx4msPkh5OlRGweAo90haPXyqV8LNlD+6ovVHN8W1hoNdeb
7sMKCpbfkiGwpM3Z53C/5z7i94z5+FSzJqezuLdONUp22e418NS93TgZnhRVGWyt
IFfwYGJtzVFvs/FaLqK5ayYsLQ9hCjBMg4ITQ3i8mAInYvmKfIG3Z8hPofslgkp8
Jd5LEP84CwXyoj5wiLhvL5oCu7QZ2aRht2mVg8P8EoUGzMEvd95AxfaTsx04iNMu
reHHsmtGwBXiLlYccbhVPIciRtHyPif0mYrIMdmrSguWttsRqpEmoDZoI0FYG/Wl
GtsVVbikJ9uU2tDEIbg1xcN0fqVaaGBpHRVD4ACs0bd4jhT/V2o=
=/3FI
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Re: Network is unreachable - VM

<EuPe5eP$LA0jFw0Q@ku.gro.lloiff>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2223&group=comp.misc#2223

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: bull...@ku.gro.lioff (Adrian)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 16:10:39 +0000
Organization: Occasionally
Lines: 37
Message-ID: <EuPe5eP$LA0jFw0Q@ku.gro.lloiff>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff> <tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff> <tqjtqt$36tmg$3@dont-email.me>
<$CunyCTgpYzjFwI4@ku.gro.lloiff> <tqljq7$3i3r8$6@dont-email.me>
<7HI6fCPoeqzjFwJn@ku.gro.lloiff> <tqmqmn$3op39$3@dont-email.me>
<LH2NjEGGS7zjFweR@ku.gro.lloiff> <slrntsvuhq.304.dan@djph.net>
Reply-To: Adrian <bulleid@ffoil.org.uk>
MIME-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader01.eternal-september.org; posting-host="f5b3f2500b7231f3976f52428233ae94";
logging-data="235755"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/qAsfGkiejT/rRYL0HpJd00YbrdghAWO4="
User-Agent: Turnpike/6.07-M (<T3+zPlY$$wDB2GseAV5aF2iM50>)
Cancel-Lock: sha1:AlxWpHjCknpJyBMN5aATZDya8zI=
 by: Adrian - Tue, 24 Jan 2023 16:10 UTC

In message <slrntsvuhq.304.dan@djph.net>, Dan Purgert <dan@djph.net>
writes
>> As an experiment last night, I swapped back to my old router, and with
>> that the VM worked as I expected it to, without changing any settings.
>
>In either case; the VM in question is getting its DNS server information
>via DHCP, right? In both cases, is it the IP address of the router?
>

I can't see that it has any other source. I've only set up that
information on the router.

Another quirk, which may or may not be relevant. As an experiment, I've
created another CentOS VM on Virtual Box, and that also has the same
issue (it can ping external servers, but not local ones unless I use
their IP address). I also created a new CentOS VM (both using the same
ISO) on VMWare, again, a vanilla install, and that one works in the same
way that the original VM worked prior to the router change. The config
options for the VM wrapper (for want of a better name) don't seem to be
as extensive with VMWare, but the networking shows up as NAT. Network
connection options are :
Bridged
Nat (selected)
Host-only
Custom
Lan segment

Am I right in drawing the conclusion that the problem isn't with the VM
itself, but with the VM hosting software and the way it talks to the new
router ?

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

Re: Network is unreachable - VM

<tqp100$2tlc$17@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=2224&group=comp.misc#2224

 copy link   Newsgroups: comp.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: mo0...@posteo.de (Marco Moock)
Newsgroups: comp.misc
Subject: Re: Network is unreachable - VM
Date: Tue, 24 Jan 2023 17:28:48 +0100
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <tqp100$2tlc$17@dont-email.me>
References: <nOihx1FQcRzjFw7Y@ku.gro.lloiff>
<tqjb3n$33uvr$1@dont-email.me>
<9fE3V4LJlTzjFw41@ku.gro.lloiff>
<tqjtqt$36tmg$3@dont-email.me>
<tqjv4c$70f$1@gioia.aioe.org>
<QzV8OIUP0YzjFwvP@ku.gro.lloiff>
<tqk9cp$2h8ao$1@dont-email.me>
<6T622Hax9bzjFw5V@ku.gro.lloiff>
<slrntsvcrs.304.dan@djph.net>
<tqocka$2tlc$9@dont-email.me>
<slrntsvts9.304.dan@djph.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 24 Jan 2023 16:28:49 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1dcf83a5c5efb0722b11517ef0c4aff6";
logging-data="95916"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18aZIaLVFI2fGv/1tw9TYKQ"
Cancel-Lock: sha1:Z7G0qc3wUiyZHUQ6gxnxG912CAI=
 by: Marco Moock - Tue, 24 Jan 2023 16:28 UTC

Am 24.01.2023 um 15:20:47 Uhr schrieb Dan Purgert:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2023-01-24, Marco Moock wrote:
> > Am 24.01.2023 um 10:30:26 Uhr schrieb Dan Purgert:
> >
> >> That's mDNS. Sounds like you lost the search-domain for ".local"
> >> as part of the upgrade cycle. That is, the previous router had
> >> some setting that applied the ".local" TLD to non-FQDN hostnames.
> >
> > Wrong.
> >
> > .local is mDNS and will be used with IPv4/IPv6 multicast link local
> > addresses, regardless if a router is present or not.
> >
> > Although mDNS uses link-local multicast, it only works on the same
> > Ethernet link, NAT breaks that as I already pointed out.
>
> You seem to have misread the interaction.
>
> Old router -> unqualified hostnames (i.e. "rpi3") resolved properly to
> hosts on the LAN.
> New router -> unqualified hostnames (i.e "rpi3") do not resolve; BUT
> their mDNS hostnames (i.e. "rpi3.local") do.
>
> Therefore -> "old router" had been providing the appropriate mDNS
> search-domain (".local").

A search domain can be obtained via DHCP, but using .local for that is
not common.

> I'd imagine this to be most likely provided
> as part of the DHCP options; although it could potentially have been
> part of the router's own internal DNS server configuration.

Normally not because .local is intended for multicast DNS - not unicast
DNS, that works a bit different.

Pages:12
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor