[SOLVED] interface didn't started after gateway changed

mldstdk

New Member
Feb 10, 2021
2
0
1
Hello everyone.
I have to change proxmox gateway and move from one router to another. [gw 192.168.1.1 -> 192.168.0.1]
After changed IP and gateway settings new connection was lost. Leds didn't light too.
Didn't change IP to old one but connected to old router. Leds lights on on the ethernet port.
Connected to the new router, the ethernet port LED will turn off. Funny.
Change static ip to dhcp /etc/network/interfaces
auto lo
iface lo inet loopback

#iface eno1 inet manual

auto eno2
iface eno2 inet dhcp

#iface eno3 inet manual

#iface eno4 inet manual

#auto vmbr0
#iface vmbr0 inet static
# address 192.168.0.45
# netmask 255.255.255.0
# gateway 192.168.0.1
# bridge-ports eno2
# bridge-stp off
# bridge-fd 0
and trying find out whats going on.
The connection on the old router (192.168.1.1) went well. Link is Up.
Feb 17 13:18:01 dyk systemd[1]: pvesr.service: Succeeded.
Feb 17 13:18:01 dyk systemd[1]: Started Proxmox VE replication runner.
Feb 17 13:18:57 dyk kernel: i40e 0000:64:00.1 eno2: NIC Link is Up, 1000 Mbps Full Duplex, Flow Control: None
Feb 17 13:18:57 dyk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready
Feb 17 13:19:00 dyk systemd[1]: Starting Proxmox VE replication runner...
Feb 17 13:19:01 dyk systemd[1]: pvesr.service: Succeeded.
Feb 17 13:19:01 dyk systemd[1]: Started Proxmox VE replication runner.
Feb 17 13:19:52 dyk systemd[1]: Stopping Network initialization...
Feb 17 13:19:52 dyk networking[5315]: networking: Deconfiguring network interfaces
Dhcp client get new[old] ip address
Feb 17 13:19:52 dyk systemd[1]: Stopped Network initialization.
Feb 17 13:19:52 dyk systemd[1]: Starting Network initialization...
Feb 17 13:19:52 dyk networking[5390]: networking: Configuring network interfaces
Feb 17 13:19:53 dyk info[5405]: eno2: enabling syslog for dhcp configuration
Feb 17 13:19:53 dyk info[5405]: executing /sbin/dhclient -x -pf /run/dhclient.eno2.pid -lf /var/lib/dhcp/dhclient.eno2.leases eno2
Feb 17 13:19:53 dyk dhclient[5418]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 4
Feb 17 13:19:53 dyk info[5405]: executing ip -o addr show eno2
Feb 17 13:19:53 dyk info[5405]: executing /sbin/dhclient -pf /run/dhclient.eno2.pid -lf /var/lib/dhcp/dhclient.eno2.leases eno2
Feb 17 13:19:53 dyk dhclient[5421]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 4
Feb 17 13:19:53 dyk dhclient[5421]: DHCPOFFER of 192.168.1.56 from 192.168.1.1
Feb 17 13:19:53 dyk dhclient[5421]: DHCPREQUEST for 192.168.1.56 on eno2 to 255.255.255.255 port 67
Feb 17 13:19:53 dyk dhclient[5421]: DHCPACK of 192.168.1.56 from 192.168.1.1
Feb 17 13:19:53 dyk dhclient[5421]: bound to 192.168.1.56 -- renewal in 284913 seconds.
Feb 17 13:19:53 dyk info[5405]: executing ip -o addr show eno2
Feb 17 13:19:53 dyk info[5405]: eno2: dhclient: new address detected: 192.168.1.56/24
Feb 17 13:19:53 dyk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready
Then I connect to a new router (192.168.0.1) :
Feb 17 14:26:32 dyk kernel: i40e 0000:64:00.1 eno2: NIC Link is Down
Dhcp client can't get an ip. and how
1613561395208.png

I checked all interfaces eno1-4.
The old router gets connection, but the new one is not.

I will be very appreciated on any information what to do.
 

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!