Главная » Интернет

Нет интернета в proxmox

На чтение 11 мин Просмотров 2 Опубликовано
Содержание
  1. VM no Internet
  2. eiger3970
  3. dcsapak
  4. eiger3970
  5. wosp
  6. eiger3970
  7. wosp
  8. eiger3970
  9. wosp
  10. eiger3970
  11. [SOLVED] No internet on network
  12. gernazdasch
  13. Proxmox потерял сеть
  14. Проблема решена
  15. Похожие темы
  16. [SOLVED] Proxmox container no internet
  17. popallo

VM no Internet

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

eiger3970

Active Member

Hello, I upgraded to Proxmox Virtual Environment 4.2-2/725d76f0 and restored the VMs, but 1 VM (Ubuntu) will not access Internet? I set /etc/network/interfaces with the same config as the other VMs, but no Internet for some reason?
Setting is: 

source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.143 netmask 255.255.255.0 network 192.168.1.0 gateway 192.168.1.1 dns-nameservers 8.8.8.8 dns-nameservers 8.8.4.4

Any suggestions on the Proxmox config at all?
I might remove and create a new VM and restore the VM to fix it, but I would like to know what configuration is awry.

dcsapak

Proxmox Staff Member

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

eiger3970

Active Member

VM 141’s network shows: (141 DHCP and static IP has Internet) 

net0: e1000=02:4A:8D:18:39:63,bridge=vmbr0

VM 143’s network shows: (DHCP has Internet, but static IP (preferred) has no Internet) 

net0: bridge=vmbr0,e1000=36:64:33:61:65:63

I’m not sure why the order of the network bridge and e1000 (not sure what e1000 is) is different, so I’ll research.
Any help on this would be great and maybe quicker than my research.

root@proxmox:~# qm config 141 bootdisk: virtio0 cores: 1 ide2: local:iso/ubuntu-16.04-server-amd64.iso,media=cdrom memory: 2048 name: vm141 net0: e1000=02:4A:8D:18:39:63,bridge=vmbr0 onboot: 1 ostype: other smbios1: uuid=bcd7c21c-69ce-4ae0-a7c2-95eed0ab2d2c sockets: 1 virtio0: local:141/vm-141-disk-1.raw,size=100G
root@proxmox:~# qm config 143 bootdisk: virtio0 cores: 1 ide2: local:iso/ubuntu-16.04-server-amd64.iso,media=cdrom memory: 2048 name: vm143 net0: bridge=vmbr0,e1000=36:64:33:61:65:63 numa: 0 onboot: 1 ostype: l26 smbios1: uuid=9f0e0b40-b537-49a1-9611-f25f1f20f253 sockets: 1 virtio0: local-lvm:vm-143-disk-1,size=30G

wosp

Member

e1000 is your network driver. Try to change it to virtio (also gives better performence in most setups). The order is just a syntax issue and both are valid, if you want you can change it in /etc/pve/qemu-server/VMID.conf.

On the VM without internet connection, can you ping the gateway IP?

eiger3970

Active Member

From VM 143, pinging the gateway shows error:
connect: Network is unreachable.

However, the network seems messed up:

This is the current config for /etc/network/interfaces: 

source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.143 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 8.8.8.8 dns-nameservers 8.8.4.4
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:160 errors:0 dropped:0 overruns:0 frame:0 TX packets:160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:11840 (11.8 KB) TX bytes:11840 (11.8 KB)

I changed /etc/pve/qemu-server/143.conf, line 4, from 

ide2: local:iso/ubuntu-16.04-server-amd64.iso,media=cdrom memory: 2048 name: 143 net0: bridge=vmbr0,e1000=36:64:33:61:65:63 numa: 0 onboot: 1 ostype: l26 smbios1: uuid=9f0e0b40-b537-49a1-9611-f25f1f20f253 sockets: 1 virtio0: local-lvm:vm-143-disk-1,size=30G
ide2: local:iso/ubuntu-16.04-server-amd64.iso,media=cdrom memory: 2048 name: 143 net0: bridge=vmbr0,virtio=36:64:33:61:65:63 numa: 0 onboot: 1 ostype: l26 smbios1: uuid=9f0e0b40-b537-49a1-9611-f25f1f20f253 sockets: 1 virtio0: local-lvm:vm-143-disk-1,size=30G

wosp

Member

To change from e1000 to virtio you need to stop-start the VM, a reboot is not enough.

Читайте также:  Проверка скорости интернета сети интернет

Do you get any error when you run «service networking restart» and/or «ifconfig eth0 up» in the VM?

eiger3970

Active Member
Service networking restart Job for networking.service failed because the control process exited with error code. See “systemctl status networking.service” and “journalctl -xe” for details.
Ifconfig eth0 up Eth0: ERROR while getting interface flags: No such device

wosp

Member

Okay so there’s no eth0 device. I guess your system has another/new interface name (possibly eth1?) for your networkcard. Run:

Then you should see something like:

Change in /etc/network/interfaces to right interface name and reboot VM. If you only see ‘lo’ this isn’t the case and there’s another problem.

eiger3970

Active Member

Thank you for the reply.
The Console shows the 2nd option, outputting lo.

Here’s the output for the error prompts:
systemctl status networking.service 

networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/networking.service.d |_50-insserv.conf-$network.conf Active: failed (Result: exit-code) since Sat 2016-05-28 17:50:44 AEST; 3h 24min ago Docs: man:interfaces(5) Process: 706 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 698 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exlude Main PID: 706 (code=exited, status=1/FAILURE) May 28 17:50:44 ubuntu systemd[1]: Starting Raise network interfaces. May 28 17:50:44 ubuntu ifup[706]: Cannot find device "eth0" May 28 17:50:44 ubuntu ifup[706]: Failed to bring up eth0. May 28 17:50:44 ubuntu systemd[1] networking.service: Main process exited, code=exited, status=1/FAILURE May 28 17:50:44 ubuntu systemd[1]: Failed to start Raise network interfaces. May 28 17:50:44 ubuntu systemd[1]: networking.service: Unit entered failed state. May 28 17:50:44 ubuntu systemd[1]: networking.service: Failed with result 'exit-code'. lines 1-17/17 (END)

Источник

[SOLVED] No internet on network

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

gernazdasch

New Member

I want to give internet access to a VM. I used this technique a lot of times, why is now not working?

# network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read 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 iface lo inet6 loopback auto enp8s0 iface enp8s0 inet static address xxx.xxx.xxx.xxx/26 gateway xxx.xxx.xxx.xxx up route add -net xxx.xxx.xxx.xxx netmask 255.255.255.192 gw xxx.xxx.xxx.xxx dev enp8s0 # route xxx.xxx.xxx.xxx/26 via xxx.xxx.xxx.xxx post-up echo 1 > /proc/sys/net/ipv4/ip_forward iface enp8s0 inet6 static address xxxx:xxx:xxx:xxxx::x/64 gateway fe80::1 iface eth0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.10.1/24 bridge-ports none bridge-stp off bridge-fd 0 post-up iptables -t nat -A POSTROUTING -s 192.168.10.1/24 -o vmbr0 -j MASQUERADE post-down iptables -t nat -A POSTROUTING -s 192.168.10.1/24 -o vmbr0 -j MASQUERADE auto vmbr1 iface vmbr1 inet static address 192.168.20.1/24 bridge-ports none bridge-stp off bridge-fd 0 # no internet network auto vmbr2 iface vmbr2 inet static address 10.10.10.100/24 bridge-ports none bridge-stp off bridge-fd 0 post-up iptables -t nat -A POSTROUTING -s 10.10.10.100/24 -o vmbr2 -j MASQUERADE post-down iptables -t nat -A POSTROUTING -s 10.10.10.100/24 -o vmbr2 -j MASQUERADE
test1@test1:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens18: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 6a:95:75:02:14:92 brd ff:ff:ff:ff:ff:ff altname enp0s18 inet 192.168.10.101/24 brd 192.168.10.255 scope global noprefixroute ens18 valid_lft forever preferred_lft forever inet6 fe80::6895:75ff:fe02:1492/64 scope link noprefixroute valid_lft forever preferred_lft forever

I am wondering what i am doing wrong, i did this to other proxmox servers and working. I might miss something maybe.

Читайте также:  Где лучше измерять скорость интернета

Источник

Proxmox потерял сеть

Debian, а конкретно сборка Proxmox. Сервер завис, после перезагрузки перестал видеть сеть. Куда копать?

Проблема программная. аппаратным путём не решается.

Столкнулся с аналогичной проблемой.

Покажите ip link show dev vmbr0

Покажите brctl show vmbr0

Какая версия Proxmox ( pveversion -v )?

Harliff ★★★★★ ( 29.11.21 15:00:38 MSK )
Последнее исправление: Harliff 29.11.21 15:01:31 MSK (всего исправлений: 2)

ifup что то сделает, если интерфейса нет в системе?

ifup что то сделает, если интерфейса нет в системе?

Выполнит скрипт /etc/network/if-pre-up.d/bridge, который запустит brctl addbr и ip link с нужными параметрами.

Проблема решена

Проблема решена. Оказался выгоревший порт на коммутаторе.

У меня выгоревший порт на коммутаторе оказался.

У меня выгоревший порт на коммутаторе оказался. Видимо статика повесила ядро и выжгла порт (

так я и подумал, что дело не в проксмосе, судя по скриншотам.

В моём случае, кажется всё было интересней…

При установке, установщик спросил на какой интерфейс (из двух) назначить мост, и после установки перепутал интерфейсы. Условно говоря, я говорю, привяжи мост к интерфейсу eno0, он привязал, а после перезагрузки, всё спуталось eno0 — стал интерфейс который не должен принимать участие в мосту. Поправил /etc/network/interfaces — и всё заработало. Вроде…

Похожие темы

  • Форум Gentoo, скоро хендбук отроскомнадзорят (2021)
  • Галерея Запустил в qemu на Arm64 винду ХР и семёрку (2021)
  • Форум Как на уровне ядра «сдвинуть» видео по HDMI? (2021)
  • Форум Паяльно-справочное. ШИМ SSD. Кащ. (2021)
  • Форум Контроль частоты процессора (2022)
  • Форум Как понять асинхонщину в Rust? (2021)
  • Форум Получение разрешения на изменение раздела (2022)
  • Форум [eeepc900]suspend2ram (2011)
  • Форум NAS не видит у себя раздел с файлами (2011)
  • Форум Настройка LVM-Thin на Proxmox (2018)
Читайте также:  Снижается скорость интернета через вай фай

Источник

[SOLVED] Proxmox container no internet

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

popallo

Member

Hello everyone, I have a problem that I can not solve on a SCALEWAY GP1-XS instance.

I installed debian 9 on it then proxmox 5.4. Good for this part, I can connect to the proxmox web interface without any problems.

I would like to give the opportunity to my LXC containers to access the internet without ip failover but i’m lost when i need to configure the network interfaces.

Currently i have an interface named «ens2» and I do not know what else to do.

I followed various tutorial indicating to create an interface vmbr0 then vmbr1. So I manage to make my containers ping the host via an ip type 192.168.1.x but they can not reach any website.

Here is the configuration I did (which does not work) and any help would be appreciated

auto lo iface lo inet loopback source /etc/network/interfaces.d/*.cfg iface eth0 inet manual iface eth1 inet manual auto vmbr0 iface vmbr0 inet static address 10.x.x.x #Scaleway private ip netmask 255.255.255.254 gateway 10.x.x.y bridge-ports eth0 bridge-stp off bridge-fd 0 auto vmbr1 iface vmbr1 inet static address 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255 bridge_ports none bridge_stp off bridge_fd 0 post-up echo 1 > /proc/sys/net/ipv4/ip_forward post-up iptables -t nat -A POSTROUTING -s '192.168.1.0/24' -o vmbr0 -j MASQUERADE post-down iptables -t nat -D POSTROUTING -s '192.168.1.0/24' -o vmbr0 -j MASQUERADE

The content of interfaces.d/

auto lo iface lo inet loopback auto ens2 iface ens2 inet dhcp

Same file for my first container

auto lo
iface lo inet loopback

auto eth0 iface eth0 inet static address 192.168.1.100 netmask 255.255.255.0 gateway 192.168.1.254

traceroute 1.1.1.1 give me this

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default gateway 0.0.0.0 UG 0 0 0 ens2 10.x.x.198 0.0.0.0 255.255.255.254 U 0 0 0 ens2

I think that I made several errors, in particular I see under the interface of proxmox that the interface eth0 is not active and I have a doubt on the use of the private ip on vmbr0.

Источник

Оцените статью
© 2023 Posetke
Adblock
detector