[SOLVED] network interfaces doesn’t start correctly

O

optimistic

New Member
Jun 11, 2018
11
1
3
35
I want to have static IP for my Proxmox and Network Bridge for my VM.

When I reboot my Proxmox I can't access it via web.
This is ping of gateway 192.168.0.1 just after reboot:
Code: 
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.150 icmp_seq=1 Destination Host Unreachable
From 192.168.0.150 icmp_seq=2 Destination Host Unreachable
From 192.168.0.150 icmp_seq=3 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2025ms
pipe 3

After I run:
Code: 
ifdown enp0s25 && ifup enp0s25
I can ping 192.168.0.1 correctly and can connect my Proxmox via web.
How to make network interfaces start correctly?

Code: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp0s25

iface enp0s25 inet static
        address  192.168.0.150
        netmask  255.255.255.0

auto vmbr0
iface vmbr0 inet static
        address  192.168.0.150
        netmask  255.255.255.0
        gateway  192.168.0.1
        bridge_ports enp0s25
        bridge_stp off
        bridge_fd 0

Code: 
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.150  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 00:19:99:bb:b4:ec  txqueuelen 1000  (Ethernet)
        RX packets 2215  bytes 878346 (857.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1474  bytes 722508 (705.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xfe400000-fe420000 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 276  bytes 99213 (96.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 276  bytes 99213 (96.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap100i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether a6:1c:65:34:ba:4f  txqueuelen 1000  (Ethernet)
        RX packets 137  bytes 11841 (11.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 388  bytes 348114 (339.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.150  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::219:99ff:febb:b4ec  prefixlen 64  scopeid 0x20<link>
        ether 00:19:99:bb:b4:ec  txqueuelen 1000  (Ethernet)
        RX packets 1996  bytes 534128 (521.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1188  bytes 694095 (677.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
CX3r1sZ.png
 
dietmar said:
No, you should configure the IP on the bridge device ...
Click to expand...
Thanks, this works for me.
Now connection starts both on PVE and VM :)

Code: 
auto lo
iface lo inet loopback

allow-hotplug enp0s25

iface enp0s25 inet manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.0.150
        netmask  255.255.255.0
        gateway  192.168.0.1
        bridge_ports enp0s25
        bridge_stp off
        bridge_fd 0
 
You must log in or register to reply here.
Top Bottom