Browser can't connect on 1st PVE install on home network

[freedoN]

Thank you for any assistance!!! (I don't know much about my home networking but very interested in learning)

• Nube first time PVE install on a 2010 Mac Pro Xeon 12-core
• Cabled ethernet
• Tried 3 different browsers
• Restarted physical machine
• Restarted services: systemctl restart pveproxy pvedaemon

Checked if I'm using correct address and if it's configured on the host with: ip -br -c a --- It returned


Checked posting status with: systemctl status pveproxy pvedaemon --- It returned

 

[freedoN]

I'm not sure why I'm not getting a response. Any suggestions on how I can get pointed in the right direction? Is there a better forum for a first time user?

 

[UdoB]

1st screenshot: both NICs and the bridge vmbr0 are down. Please check cabling and/or the switch port.

You might add some more information regarding network topology and the content of /etc/network/interfaces.

Also 170.11.x.x/16 belongs to a "real" network:

NetRange:       170.11.0.0 - 170.11.255.255
CIDR:           170.11.0.0/16      
NetName:        MML-B                                                      
NetHandle:      NET-170-11-0-0-1
Parent:         NET170 (NET-170-0-0-0-0)
NetType:        Direct Allocation
OriginAS:                      
Organization:   Securian Financial Group, Inc. (SECUR-71-Z)

You are using this intentionally? What is your router? Does the configuration fit to each other?

Anyway: as long a the NIC is physically down --> nothing can work... What gives ifup vmbr0?


Best regards

 

[freedoN]

Thanks UdoB!
Your questions are informative. I will reinstall PVE a 2nd time, photo what I input and be more certain of initial settings and come back to this thread in a couple of hours.

 

[freedoN]

> check cabling and/or the switch port.

This 2010 Mac Pro has 2 built-in ethernet ports. I switched the ethernet cable to the other port, rebooted the Mac Pro, restarted PVE, entered:
ip -br -c a
It returned green:
enp9s0: up
vmbr0: up

But different browsers still do not connect to my
https://170.11.11.4:8006/

> regarding network topology

My Mac Pro is connected with ethernet to a basic home ATT internet router and plan with wifi and 4 ethernet ports.
Is it insecure in this forum? to post my results for
$ cat /proc/net/dev
and
$ ip link show

or is there another command which would provide more better:
> more information regarding network topology and the content of /etc/network/interfaces

Is it secure to post my router model here?

> Also 170.11.x.x/16 belongs to a "real" network... You are using this intentionally? Does the configuration fit to each other?

No configuration plan. I picked the numbers 170.11.11.x randomly and because it was outside of my routers DHCP Network Range. If I need a different number, I do not know how to select it. My PVE will "not" be opened to the internet.

Now when I enter
ifup vmbr0
I get nothing just the command prompt

 

[UdoB]

It returned green:
enp9s0: up
vmbr0: up

Fine! That's an important step forward

My Mac Pro is connected with ethernet to a basic home ATT internet router and plan with wifi and 4 ethernet ports.
Is it insecure in this forum? to post my results for
$ cat /proc/net/dev
and
$ ip link show

Should be okay, in my opinion. You may anonymize the last octet like 123.456.789.xxx of IP addresses.

Is it secure to post my router model here?

Well, it should not be necessery to keep this secret. But it doesn't help (me) as I probably don't know that type anyway. (I am in central Europe.)

> Also 170.11.x.x/16 belongs to a "real" network... You are using this intentionally? Does the configuration fit to each other?

No configuration plan. I picked the numbers 170.11.11.x randomly and because it was outside of my routers DHCP Network Range.

Okay, seem logical but is (partially) wrong ;-)
What is your actual router dhcp range? For simplicity you need to use an address in the same network, but an unused one of course.

Now when I enter
ifup vmbr0
I get nothing just the command prompt

That's basically fine. No (text-) output means no error message

You can not contact your Proxmox because your default route points to "the internet". All packages directed to 170.11.11.3 will be delivered to the legit user / destination - and that is NOT your proxmox installation.

Please read https://en.wikipedia.org/wiki/Private_network for a description which networks are "free" to use.


Best regards

 

[freedoN]

UdoB said:
> ...You are using this intentionally? Does the configuration fit to each other?
freedoN said:
> ...I picked the numbers 170.11.11.x randomly and because it was outside of my routers DHCP Network Range.
UdoB said:
> Okay, seem logical but is (partially) wrong ;-)
...you need to use an address in the same network, but an unused one of course.

Yes! Thank you UdoB that worked. Logged in with a browser to my first PVE!

 

[freedoN]

UdoB said:
> ...You are using this intentionally? Does the configuration fit to each other?
freedoN said:
> ...I picked the numbers 170.11.11.x randomly and because it was outside of my routers DHCP Network Range.
UdoB said:
> Okay, seem logical but is (partially) wrong ;-)
...you need to use an address in the same network, but an unused one of course.

Yes! Thank you UdoB that worked. Logged in with a browser to my first PVE!
(got some incorrect instructions from a tutorial I was using)

 

[UdoB]

Great!

Have fun