New installation won't connect to internet at all

[Kalinda]

Just installed proxmox on a desktop, can't ping 8.8.8.8, any websites or anything at all. Also doing apt-get update returns with 'Failed to fetch' any of the debian packets. It also says ifconfig command not found.

 

[102020]

ifconfig uses net-tools, by default (and more mainstream these days), ethtools is used.
try:
ip address
ip link
ip route
ip up/down

for your commands

 

[Kalinda]

Oh cool, those commands work but even if I change around my IP address from the default 192.168.100.2 it still won't ping even 8.8.8.8. It says that the 8006 port is listening though.

 

[ecce]

I have the same issue. I can connect to the proxmox server as long as I'm in the same subnet, and I can ping anything within the same subnet, but nothing outside the same subnet. DNS lookups works fine (I have a local DNS on the same subnet). apt update for some reason chooses IPv6 although I only have a link-local address.

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp7s0f1 inet manual

iface eno0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.14.112
netmask 255.255.255.0
gateway 192.168.14.1
bridge-ports enp7s0f1
bridge-stp off
bridge-fd 0



Some output:

root@prox1:/etc/network# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> 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: eno0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1e:67:97:98:bd brd ff:ff:ff:ff:ff:ff
3: enp7s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 00:1e:67:97:98:be brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:1e:67:97:98:be brd ff:ff:ff:ff:ff:ff
inet 192.168.14.112/24 brd 192.168.14.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::21e:67ff:fe97:98be/64 scope link
valid_lft forever preferred_lft forever


root@prox1:/etc/network# ping 192.168.14.1
PING 192.168.14.1 (192.168.14.1) 56(84) bytes of data.
64 bytes from 192.168.14.1: icmp_seq=1 ttl=64 time=0.288 ms
64 bytes from 192.168.14.1: icmp_seq=2 ttl=64 time=0.308 ms
^C
--- 192.168.14.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 12ms
rtt min/avg/max/mdev = 0.288/0.298/0.308/0.010 ms


root@prox1:/etc/network# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 107ms


root@prox1:/etc/network# nslookup www.google.com
Server: 192.168.14.61
Address: 192.168.14.61#53

Non-authoritative answer:
Name: www.google.com
Address: 216.58.207.228
Name: www.google.com
Address: 2a00:1450:400f:80c::2004

root@prox1:/etc/network# ip route
default via 192.168.14.1 dev vmbr0 onlink
192.168.14.0/24 dev vmbr0 proto kernel scope link src 192.168.14.112

root@prox1:/etc/network# apt update
0% [Connecting to ftp.se.debian.org (2001:6b0:19::165)] [Connecting to prod.debian.map.fastly.net (2a04:4e42:47::204)] ...

 

[Chris]

Hi,
is the firewall enabled on this host? Does it work when you force apt to use ipv4 via apt -o Acquire::ForceIPv4=true update?

 

[ecce]

Hi,
is the firewall enabled on this host? Does it work when you force apt to use ipv4 via apt -o Acquire::ForceIPv4=true update?

No. Not as far as I can tell, I'm new to proxmox. On the datacenter level it says "Firewall No", I've set it to No also on the node, and iptables shows empty tables with ACCEPT as the default policy. Forcing IPv4 does not work. Nothing beyond the gateway works.

 

[ecce]

Managed to fix my issue but I'm not really sure what I did... I tried setting IP addresses on the NICs, changed stuff around in the /etc/network/interfaces file, rebooting, getting nowhere, and changed it all back again and suddenly it worked. I really cant see anything different in the config now when comparing to the output above. Also apt started working, I guess it switched to IPv6 when IPv4 did not work or something, and that is the output I saw.