Prox still uses old gateway ip

aurel81

New Member
Oct 12, 2024
4
0
1
Hey I was wondering why one prox ve cant access the wan in my setup ( 1 of 3).
Some digging showed me, that it tries to connect to 192.169.0.1... the gateway/subnet it was connected to during installation and although it gets ip from the current vlan... the other 2, connected to the same vlan try to reach for the corresponding gateway...und it works

Any idea how to fix it?
 
Change the network config to use the correct GW?

Otherwise, please provide more infos! What is the current network config of the host? (cat /etc/network/interfaces) and what is actually applied? (ip a, ip r)
 
alright sure :)

here are the requested information

NOT working PVE

IP a
Code:
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:d0:b4:01:95:c3 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.3/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::2d0:b4ff:fe01:95c3/64 scope link
       valid_lft forever preferred_lft forever
IP r
Code:
via 10.10.10.1 dev vmbr0 proto kernel onlink
10.10.10.0/24 dev vmbr0 proto kernel scope link src 10.10.10.3
interfaces:
Code:
/etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 10.10.10.3/24
        gateway 10.10.10.1
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

source /etc/network/interfaces.d/*

Code:
root@prox:~# dig web.de
;; communications error to 192.168.0.1#53: timed out
;; communications error to 192.168.0.1#53: timed out
---------------------------------------------------------------------------------
and from the WORKING PVE, same VLAN

ip a
Code:
vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e0:4c:3c:a8:20 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.5/24 brd 10.10.10.255 scope global dynamic vmbr0
       valid_lft 6558sec preferred_lft 6558sec
    inet6 fe80::2e0:4cff:fe3c:a820/64 scope link
       valid_lft forever preferred_lft forever

ip r
Code:
default via 10.10.10.1 dev vmbr0
10.10.10.0/24 dev vmbr0 proto kernel scope link src 10.10.10.5

interfaces
Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet dhcp
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

source /etc/network/interfaces.d/*

Code:
root@truebackup:~# dig web.de

; <<>> DiG 9.18.24-1-Debian <<>> web.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41536
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;web.de.                                IN      A

;; ANSWER SECTION:
web.de.                 60      IN      A       82.165.229.83
web.de.                 60      IN      A       82.165.229.138

;; Query time: 57 msec
;; SERVER: 10.10.10.1#53(10.10.10.1) (UDP)
;; WHEN: Thu Oct 24 21:14:49 CEST 2024
;; MSG SIZE  rcvd: 67
 
Looks to me, that your DNS server is incorrect; not your gateway.
You can adapt it in: /etc/resolv.conf
 

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!

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!