Connection issue after adding a new static IP

O

OD3UNICRON

New Member
Oct 23, 2022
20
4
3
I'm not very good in networking, perhaps someone can guide me thru. So this how I started.

Code: 
root@UniMatrix001:~# ip -br -c a
lo               UNKNOWN        127.0.0.1/8 ::1/128
eno1np0          UP             
eno2np1          UP             
enp129s0f0       DOWN           
enp129s0f1       DOWN           
enx42d0f00f737b  DOWN           
vmbr0            UP             38.189.78.27/24 fe80::aaa1:59ff:fec2:7858/64
vmbr1            UP             38.189.78.26/24 fe80::aaa1:59ff:fec2:7859/64
tap100i0         UNKNOWN

I can SSH and login to Proxmox, but I can't update, I open shell and typed ping google.com and its unreachable.
Next step.

Code: 
root@UniMatrix001:~# ip -c link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:58 brd ff:ff:ff:ff:ff:ff
    altname enp66s0f0np0
3: eno2np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:59 brd ff:ff:ff:ff:ff:ff
    altname enp66s0f1np1
4: enp129s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:25:90:3a:99:3e brd ff:ff:ff:ff:ff:ff
5: enp129s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:25:90:3a:99:3f brd ff:ff:ff:ff:ff:ff
6: enx42d0f00f737b: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 42:d0:f0:0f:73:7b brd ff:ff:ff:ff:ff:ff
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:58 brd ff:ff:ff:ff:ff:ff
8: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:59 brd ff:ff:ff:ff:ff:ff
11: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 02:2e:4f:24:44:0d brd ff:ff:ff:ff:ff:ff

As you see, I don't see any IP on any device, so my next step to type in Option A: ```ip addr add 38.189.78.27/24 dev eno1np0``` or Option:B ```ip addr add 38.189.78.27/24 dev vmbr0```

So option A or B? or I'm wrong?
 
Mr.Doubt said:
Could you post the Output of
ip r
Click to expand...
Code: 
root@UniMatrix001:~# ip r
default via 38.189.78.1 dev vmbr0 proto kernel onlink
38.189.78.0/24 dev vmbr0 proto kernel scope link src 38.189.78.27
38.189.78.0/24 dev vmbr1 proto kernel scope link src 38.189.78.26
 
Can you ping an IP-address (for example 8.8.8.8)?
Which nameserver you have configured?
cat /etc/resolv.conf

Edit: Why you use two adresse from the same Netzwork for both bridges?
 
Last edited:
Mr.Doubt said:
Can you ping an IP-address (for example 8.8.8.8)?
Which nameserver you have configured?
cat /etc/resolv.conf

Edit: Why you use two adresse from the same Netzwork for both bridges?
Click to expand...
Code: 
root@UniMatrix001:~# cat /etc/resolv.conf
search unimatrix001.net
nameserver 192.168.1.1
This wrong, it should be 38.189.78.1
I need two public IP because I'm using and app that needs it.
 
Last edited:
should I nano this? nano ```/etc/resolv.conf``` and change 192.168.1.1 to 38.189.78.1 then run systemctl restart networking? because I'm not using a router.
 
Last edited:
OD3UNICRON said:
should I nano this? nano ```/etc/resolv.conf``` and change 192.168.1.1 to 38.189.78.1 then run systemctl restart networking? because I'm not using a router.
Click to expand...

Yes, edit the /etc/resolv.conf. You don't need to restart anything.

The address you asigned to the bridge ist the Management adress of the PVE. VMs/CTs have their own configuration.

You could assign the 38.189.78.26 to the vmbr0. The 38.189.78.27 to VM/CT

If you don't need the PVE reachable from public, you can assign 0.0.0.0 to the vmbr1 an connect this bridge to the VMs/CTs. In the VM/CT configure the public IP and Gateway.
The vmbr0 can be used only in the private network formanagement (192.168.1.123).
 
Mr.Doubt said:
Yes, edit the /etc/resolv.conf. You don't need to restart anything.

The address you asigned to the bridge ist the Management adress of the PVE. VMs/CTs have their own configuration.

You could assign the 38.189.78.26 to the vmbr0. The 38.189.78.27 to VM/CT

If you don't need the PVE reachable from public, you can assign 0.0.0.0 to the vmbr1 an connect this bridge to the VMs/CTs. In the VM/CT configure the public IP and Gateway.
The vmbr0 can be used only in the private network formanagement (192.168.1.123).
Click to expand...
Code: 
oot@UniMatrix001:~# ip r
default via 38.189.78.1 dev vmbr0 proto kernel onlink
38.189.78.0/24 dev vmbr0 proto kernel scope link src 38.189.78.27
38.189.78.0/24 dev vmbr1 proto kernel scope link src 38.189.78.26
 
Mr.Doubt said:
Are you now able to resolv names an ping to eg. 8.8.8.8
Click to expand...
root@UniMatrix001:~# ping google.com
ping: google.com: Temporary failure in name resolution
root@UniMatrix001:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=23.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=23.4 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=114 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=114 time=23.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=114 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=114 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=114 time=23.5 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=114 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=114 time=23.4 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=114 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=114 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=114 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=114 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=114 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=114 time=23.3 ms
^C
--- 8.8.8.8 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15021ms
rtt min/avg/max/mdev = 23.147/23.334/23.610/0.129 ms
 
OD3UNICRON said:
I'm not very good in networking, perhaps someone can guide me thru. So this how I started.

Code: 
root@UniMatrix001:~# ip -br -c a
lo               UNKNOWN        127.0.0.1/8 ::1/128
eno1np0          UP            
eno2np1          UP            
enp129s0f0       DOWN          
enp129s0f1       DOWN          
enx42d0f00f737b  DOWN          
vmbr0            UP             38.189.78.27/24 fe80::aaa1:59ff:fec2:7858/64
vmbr1            UP             38.189.78.26/24 fe80::aaa1:59ff:fec2:7859/64
tap100i0         UNKNOWN

I can SSH and login to Proxmox, but I can't update, I open shell and typed ping google.com and its unreachable.
Next step.

Code: 
root@UniMatrix001:~# ip -c link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:58 brd ff:ff:ff:ff:ff:ff
    altname enp66s0f0np0
3: eno2np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:59 brd ff:ff:ff:ff:ff:ff
    altname enp66s0f1np1
4: enp129s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:25:90:3a:99:3e brd ff:ff:ff:ff:ff:ff
5: enp129s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:25:90:3a:99:3f brd ff:ff:ff:ff:ff:ff
6: enx42d0f00f737b: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 42:d0:f0:0f:73:7b brd ff:ff:ff:ff:ff:ff
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:58 brd ff:ff:ff:ff:ff:ff
8: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:c2:78:59 brd ff:ff:ff:ff:ff:ff
11: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 02:2e:4f:24:44:0d brd ff:ff:ff:ff:ff:ff

As you see, I don't see any IP on any device, so my next step to type in Option A: ```ip addr add 38.189.78.27/24 dev eno1np0``` or Option:B ```ip addr add 38.189.78.27/24 dev vmbr0```

So option A or B? or I'm wrong?
Click to expand...
My concern that none of these devices are not showing any IP.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back