No internet connection on PROXMOX

Mark979

New Member
Jan 4, 2024
10
0
1
Hi to everyone,
I'm new on PROXMOX, i have installed it and i have assigned ip 192.168.200.99. My router connection have a static ip with 192.168.200.1. When i connect a new lan cable with ip 192.168.200.98 i haven't internet connection....If i type "/etc/network/interfaces" system say "permission denied". I'm confused about what to do...can you help me please? Thank you in advance to everyone and sorry for my bad english.
Mark.
 

Attachments

  • img2.jpg
    img2.jpg
    62.1 KB · Views: 67
  • win.jpg
    win.jpg
    70.6 KB · Views: 66
  • img1.jpg
    img1.jpg
    22.3 KB · Views: 62
If i type "/etc/network/interfaces" system say "permission denied".
"interfaces" is a text file. What you did in shell - is you tried to execute it, that would not work. If you want to view its context you can use "more" or "cat", ie
more /etc/network/interfaces

It also seems like you are trying to have your server multihomed whereby you have two network connections on the same subnet. Thats an exercise for above average system administrator and I would recommend you dont start there. Ie dont connect second cable.

To view your network status, in addition to context of "interfaces":
ip a
ip route
ping 192.168.200.1
ping 192.168.200.98



Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
"interfaces" is a text file. What you did in shell - is you tried to execute it, that would not work. If you want to view its context you can use "more" or "cat", ie
more /etc/network/interfaces

It also seems like you are trying to have your server multihomed whereby you have two network connections on the same subnet. Thats an exercise for above average system administrator and I would recommend you dont start there. Ie dont connect second cable.

To view your network status, in addition to context of "interfaces":
ip a
ip route
ping 192.168.200.1
ping 192.168.200.98



Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thank you so much for your answer...i have typed that command and i have attach file for results...Ping on 192.168.200.98 it's ok but on 192.168.200.1 is "destination Host Unreachable" I need to have internet connection because i will install "Openmptcrouter" and for download image inside PROXMOX need internet connection...How should I set everything up? Thank you...
 

Attachments

  • Nuova immagine bitmap (2).jpg
    Nuova immagine bitmap (2).jpg
    279.9 KB · Views: 40
  • Nuova immagine bitmap (3).jpg
    Nuova immagine bitmap (3).jpg
    27.1 KB · Views: 40
Last edited:
Have you already looked at this guide?
https://pve.proxmox.com/wiki/Network_Configuration#_default_configuration_using_a_bridge

When i connect a new lan cable with ip 192.168.200.98 i haven't internet connection
How did you try and determine this? Often it is simply the DNS servers that are missing or unreachable or you have specified a search domain.

Sorry, but I have to correct that immediately so that it doesn't get misremembered :)

Code:
The name Proxmox

When referring to the Proxmox name, the first letter must be capitalized followed by lowercase letters like
for example: Proxmox
When referring to one of the Proxmox products use Proxmox together with the product name like for
example ‘Proxmox Virtual Environment’ (in short: Proxmox VE) or ‘Proxmox Mail Gateway’.
When referring to the company you can either use the name ‘Proxmox’ or the full company name ‘Proxmox
Server Solutions GmbH’.

DO:
• Proxmox
• Proxmox Virtual Environment (or Proxmox VE)
• Proxmox Mail Gateway
• Proxmox Server Solutions GmbH

DON'T:
• don’t use all lower case (no: proxmox)
• don’t use all uppercase (no: PROXMOX)
• don’t mix upper- and lowercase in the middle of the name (never: ProxMox)
• don’t simply use our website URL in a sentence instead of the name Proxmox (no: “The company
proxmox.com is...’ if you want to say: ‘The company Proxmox is...’)

See: https://www.proxmox.com/en/about/media-kit
 
How did you try and determine this? Often it is simply the DNS servers that are missing or unreachable or you have specified a search domain.
Because for example if i try "ping www.google.com" i get "temporary failure in name resolution" or something like that...
Sorry, but I have to correct that immediately so that it doesn't get misremembered :)
Ohhh Excuse me for that!!!
Have you already looked at this guide?
Yes but I didn't understand how to set up to have an internet connection... perhaps it should be set as a bridge i.e. for example the Proxmox server on 192.168.150.1 and the LAN connection on 192.168.155.1? Can you direct me on how best to set up the network?
 
Because for example if i try "ping www.google.com" i get "temporary failure in name resolution" or something like that...
But that doesn't mean that you don't have an internet connection. Your ping also requires a DNS server that can resolve the name into an IP. Try pinging the Google DNS servers 8.8.8.8 instead of google.com.

Can you direct me on how best to set up the network?
I already have that, the Wiki article contains all possible types. The linked bridge setup is probably the most common one.

Show us the contents of your network configuration (cat /etc/network/interfaces) and DNS servers (cat /etc/resolv.conf).

And please avoid screenshots and use the code tag [CODE][/CODE] (NOT inline code tag!).
 
But that doesn't mean that you don't have an internet connection. Your ping also requires a DNS server that can resolve the name into an IP. Try pinging the Google DNS servers 8.8.8.8 instead of google.com.


I already have that, the Wiki article contains all possible types. The linked bridge setup is probably the most common one.

Show us the contents of your network configuration (cat /etc/network/interfaces) and DNS servers (cat /etc/resolv.conf).

And please avoid screenshots and use the code tag
Code:
(NOT inline code tag!).
This is my situation...

Code:
# 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!

auto lo
iface lo inet loopback

iface enp1s0 inet manual

iface enp2s0 inet manual

iface enp3s0 inet manual

iface enp4s0 inet manual

auto enxf0a7312a3272
iface enxf0a7312a3272 inet static
        address 192.168.200.2/24
        gateway 192.168.200.1

iface enxf0a7312a37d4 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.200.99/24
        bridge-ports enxf0a7312a37d4
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*
root@Openptcp:~# cat /etc/resolv.conf
search local
nameserver 8.8.8.8
nameserver 8.8.4.4
 
Last edited:
I have no idea what you did, but translating a config file or output is the worst thing you can do. The code tag ([CODE][/CODE]) does not need to be translated either. Please repost it properly without any translation.
 
I have no idea what you did, but translating a config file or output is the worst thing you can do. The code tag ([CODE][/CODE]) does not need to be translated either. Please repost it properly without any translation.
Sorry....you're right, now is ok
 
root@Openptcp:~# cat /etc/resolv.conf
search local
Remove the "search local" from this file.

Please also the output of ip a and ip r.

Your network config looks okay at first. As noted above, “search” may have been your “internet problem”. Because obviously you can access the server via SSH.

Your "internet problem" is ultimately not a problem but just a DNS problem and you could probably have pinged IPs directly without any problems.
 
Remove the "search local" from this file.

Please also the output of ip a and ip r.

Your network config looks okay at first. As noted above, “search” may have been your “internet problem”. Because obviously you can access the server via SSH.

Your "internet problem" is ultimately not a problem but just a DNS problem and you could probably have pinged IPs directly without any problems.
My
Code:
ip a

Code:
root@Openptcp:~# 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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e2:59:00:b0:49 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e2:59:00:b0:4a brd ff:ff:ff:ff:ff:ff
4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e2:59:00:b0:4b brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e2:59:00:b0:4c brd ff:ff:ff:ff:ff:ff
6: enxf0a7312a3272: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f0:a7:31:2a:32:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.2/24 scope global enxf0a7312a3272
       valid_lft forever preferred_lft forever
    inet6 fe80::f2a7:31ff:fe2a:3272/64 scope link
       valid_lft forever preferred_lft forever
7: enxf0a7312a37d4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether f0:a7:31:2a:37:d4 brd ff:ff:ff:ff:ff:ff
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f0:a7:31:2a:37:d4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.99/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::f2a7:31ff:fe2a:37d4/64 scope link
       valid_lft forever preferred_lft forever
9: tap200i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr200i0 state UNKNOWN group default qlen 1000
    link/ether fa:94:17:34:fd:1e brd ff:ff:ff:ff:ff:ff
10: fwbr200i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 62:f0:8f:f0:fb:51 brd ff:ff:ff:ff:ff:ff
11: fwpr200p0@fwln200i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether b6:3c:93:0a:21:90 brd ff:ff:ff:ff:ff:ff
12: fwln200i0@fwpr200p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr200i0 state UP group default qlen 1000
    link/ether 62:f0:8f:f0:fb:51 brd ff:ff:ff:ff:ff:ff

My
Code:
ip r

Code:
root@Openptcp:~# ip r
default via 192.168.200.1 dev enxf0a7312a3272 proto kernel onlink
192.168.200.0/24 dev enxf0a7312a3272 proto kernel scope link src 192.168.200.2
192.168.200.0/24 dev vmbr0 proto kernel scope link src 192.168.200.99

Try to ping
Code:
dev vmbr0 proto kernel scope link src 192.168.200.99
root@Openptcp:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.200.2 icmp_seq=1 Destination Host Unreachable
From 192.168.200.2 icmp_seq=2 Destination Host Unreachable
From 192.168.200.2 icmp_seq=3 Destination Host Unreachable
From 192.168.200.2 icmp_seq=4 Destination Host Unreachable
From 192.168.200.2 icmp_seq=5 Destination Host Unreachable
From 192.168.200.2 icmp_seq=6 Destination Host Unreachable

Thanks for your help...
 
Remove the "search local" from this file.

Please also the output of ip a and ip r.

Your network config looks okay at first. As noted above, “search” may have been your “internet problem”. Because obviously you can access the server via SSH.

Your "internet problem" is ultimately not a problem but just a DNS problem and you could probably have pinged IPs directly without any problems.
So will I have to set up the network according to a bridge scheme? But apparently that wouldn't work for me...
 
I think I've solved it...I set the Proxmox IP to 10.0.0.1/24, the DNS to 1.1.1.1 and 1.0.0.1
You were right, the problem was the DNS because by changing them I can now ping everything... thanks again! A greeting.
 

Attachments

  • 1.jpg
    1.jpg
    25.2 KB · Views: 54
  • 2.jpg
    2.jpg
    70.9 KB · Views: 51

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!