--- Begin Message ---
Sorry for rambling.
Allow me to run a single ethernet cable from my Proxmox (not sure which NIC) to
a Netgear
You gave me what I need, I am pretty sure.
I have (3) three NICs that I am using:
1. Internet2. 192.168.20.0/233. 192.168.30.0/24
In the configuration below, I believe this will do what I want which is: GS348T
capable of doing VLANs.
I need 8 of the ports to go to VOIP phones (192.168.30.0) VLAN 30 , I want the
be able to also use VLAN30 from the phone (which is capable of doing VLANS) and
allow VLAN 20 to feed a workstation from the phone.
My question is which NIC do I run the single cable from the PROXMOX to a
trunked port say port 48 of the GS348T Vlan Switch?
and to verify the configuration below is what I need to do this that you
provided before.
Thanks very much!
STeve
On Monday, March 1, 2021, 09:44:17 AM EST, Stefan M. Radman <[email protected]>
wrote:
Hi Steve
What exactly is the question you want to ask?
Stefan
On Feb 28, 2021, at 20:36, Steve Frazier <[email protected]> wrote:
I just purchased a Netgear 48 Port GS348T that will do VLANS.
Let's say I want to "trunk" VLAN 20/30 over to port 48 of the Netgear 48 Port
switch, I would run a patch cord from what interface (NIC) below to port 48.
Then the (8) VOIP phones I need to do would need to trunk VLAN30 (VOIP) and
VLAN20 (Computer) on say ports 1-8 and then I would just set the other ports
for VLAN20 only just for VLAN20?
I am sorry to get so complicated but this is what I want to do and of course
try and understand what I am doing as I do it. I really appreciate all of your
help.
I apologize for taking so long to get back to you, I am going to try and
understand what you have shown me.
This is pretty much way over my head but I am trying to understand.
I have (6) Nic ports that I am using presently. I have lost track of which
NICs that I am using for what. I come from the simple world of ETH0, ETH1,
ETH3 and so on.
(1) Internet(2) 192.168.20.0/23(3) 192.168.30.0/24
Since you have shown me how to have an Internet NIC and then the two local
Nets, my install is geting much more complicated.
I have added pfsense and wireguard into the mix throwing addition interfaces
into the mix I assume, I will lay them out here:
enp11s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
00:15:17:23:f8:2f txqueuelen 1000 (Ethernet) RX packets 183025 bytes
45589221 (43.4 MiB) RX errors 0 dropped 8672 overruns 0 frame 0
TX packets 30779 bytes 10977282 (10.4 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0 device interrupt 36 memory
0xfbee0000-fbf00000
enp9s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
00:15:17:d5:fb:8c txqueuelen 1000 (Ethernet) RX packets 10240813
bytes 12167243782 (11.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4609529 bytes 739192943 (704.9 MiB) TX errors 0
dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 38
memory 0xfbda0000-fbdc0000
enp9s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
00:15:17:d5:fb:8d txqueuelen 1000 (Ethernet) RX packets 313683820
bytes 439237907288 (409.0 GiB) RX errors 0 dropped 36951 overruns 0
frame 0 TX packets 149752924 bytes 21229027987 (19.7 GiB) TX
errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt
40 memory 0xfbde0000-fbe00000
fwbr102i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
9e:b1:69:b1:fe:e5 txqueuelen 1000 (Ethernet) RX packets 902886 bytes
135941047 (129.6 MiB) RX errors 0 dropped 113 overruns 0 frame 0
TX packets 2 bytes 108 (108.0 B) TX errors 0 dropped 0 overruns 0
carrier 0 collisions 0
fwbr105i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
12:66:90:e0:af:bb txqueuelen 1000 (Ethernet) RX packets 166586 bytes
11268544 (10.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 108 (108.0 B) TX errors 0 dropped 0 overruns 0
carrier 0 collisions 0
fwbr105i1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
aa:f9:63:e1:e7:43 txqueuelen 1000 (Ethernet) RX packets 902768 bytes
135930064 (129.6 MiB) RX errors 0 dropped 111 overruns 0 frame 0
TX packets 2 bytes 108 (108.0 B) TX errors 0 dropped 0 overruns 0
carrier 0 collisions 0
fwbr113i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
ca:d5:29:71:50:67 txqueuelen 1000 (Ethernet) RX packets 902578 bytes
135910861 (129.6 MiB) RX errors 0 dropped 109 overruns 0 frame 0
TX packets 2 bytes 108 (108.0 B) TX errors 0 dropped 0 overruns 0
carrier 0 collisions 0
fwln102i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
9e:b1:69:b1:fe:e5 txqueuelen 1000 (Ethernet) RX packets 1228076 bytes
210823169 (201.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 334382 bytes 47442555 (45.2 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwln105i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
12:66:90:e0:af:bb txqueuelen 1000 (Ethernet) RX packets 7060111 bytes
11832514460 (11.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4354033 bytes 678995200 (647.5 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwln105i1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
aa:f9:63:e1:e7:43 txqueuelen 1000 (Ethernet) RX packets 5494888 bytes
873377923 (832.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9998182 bytes 11985630904 (11.1 GiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwln113i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
ca:d5:29:71:50:67 txqueuelen 1000 (Ethernet) RX packets 156305554
bytes 428142574732 (398.7 GiB) RX errors 0 dropped 0 overruns 0 frame
0 TX packets 137592593 bytes 9494602142 (8.8 GiB) TX errors 0
dropped 0 overruns 0 carrier 0 collisions 0
fwpr102p0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
9e:d6:11:e5:e9:0e txqueuelen 1000 (Ethernet) RX packets 334382 bytes
47442555 (45.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1228076 bytes 210823169 (201.0 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwpr105p0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
e2:eb:af:2e:36:3b txqueuelen 1000 (Ethernet) RX packets 4354033 bytes
678995200 (647.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7060111 bytes 11832514460 (11.0 GiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwpr105p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
32:f1:86:8e:a4:5f txqueuelen 1000 (Ethernet) RX packets 9998182 bytes
11985630904 (11.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5494888 bytes 873377923 (832.9 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
fwpr113p0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether
8a:b0:44:57:0c:98 txqueuelen 1000 (Ethernet) RX packets 137592593
bytes 9494602142 (8.8 GiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 156305554 bytes 428142574732 (398.7 GiB) TX errors 0
dropped 0 overruns 0 carrier 0 collisions 0
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 1146862 bytes 145067314
(138.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX
packets 1146862 bytes 145067314 (138.3 MiB) TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
tap102i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
ether ee:4b:07:09:21:40 txqueuelen 1000 (Ethernet) RX packets 334381
bytes 47442501 (45.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1228025 bytes 210819199 (201.0 MiB) TX errors 0 dropped
0 overruns 0 carrier 0 collisions 0
tap105i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
ether 76:41:53:c5:f8:17 txqueuelen 1000 (Ethernet) RX packets 4354032
bytes 678995146 (647.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9927205 bytes 12012791415 (11.1 GiB) TX errors 0
dropped 825 overruns 0 carrier 0 collisions 0
tap105i1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
ether 82:86:71:4b:4d:f2 txqueuelen 1000 (Ethernet) RX packets 9998181
bytes 11985630850 (11.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5573107 bytes 877795901 (837.1 MiB) TX errors 0
dropped 2604 overruns 0 carrier 0 collisions 0
tap113i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
ether 42:d0:12:56:ad:37 txqueuelen 1000 (Ethernet) RX packets
137592592 bytes 9494602088 (8.8 GiB) RX errors 0 dropped 0 overruns 0
frame 0 TX packets 156304086 bytes 428142336375 (398.7 GiB) TX
errors 0 dropped 1420 overruns 0 carrier 0 collisions 0
vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet
192.168.20.2 netmask 255.255.254.0 broadcast 192.168.21.255 inet6
fe80::215:17ff:fed5:fb8d prefixlen 64 scopeid 0x20<link> ether
00:15:17:d5:fb:8d txqueuelen 1000 (Ethernet) RX packets 2155012 bytes
1062500000 (1013.2 MiB) RX errors 0 dropped 115 overruns 0 frame 0
TX packets 1335320 bytes 339766917 (324.0 MiB) TX errors 0 dropped
0 overruns 0 carrier 0 collisions 0
vmbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 public
prefixlen 64 scopeid 0x0<global> inet6 fe80::215:17ff:fed5:fb8c
prefixlen 64 scopeid 0x20<link> ether 00:15:17:d5:fb:8c txqueuelen
1000 (Ethernet) RX packets 166671 bytes 11273818 (10.7 MiB) RX
errors 0 dropped 0 overruns 0 frame 0 TX packets 175 bytes 15690
(15.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vmbr2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6
fe80::215:17ff:fe23:f82f prefixlen 64 scopeid 0x20<link> ether
00:15:17:23:f8:2f txqueuelen 1000 (Ethernet) RX packets 118684 bytes
28211461 (26.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0
TX packets 62 bytes 4516 (4.4 KiB) TX errors 0 dropped 0 overruns 0
carrier 0 collisions 0
Thanks again for your time and your help.
On Tuesday, February 16, 2021, 05:57:01 PM EST, Steve Frazier via pve-user
<[email protected]> wrote:
Wow, thanks so much! I will take a look and give it a try. Thanks Stefan!
Steve
On Tuesday, February 16, 2021, 05:40:38 PM EST, Stefan M. Radman
<[email protected]> wrote:
Here you go.
See interface enp9s0f0 in the config below.It also shows how to run tagged
(vmbr20,vmbr30) and untagged (vmbr10) traffic on the same trunk interface.
I normally use the VLAN tag ID as the bridge identifier (e.g. vmbr20 and
vmbr30).The host IP would typically be on vmbr0 and thus on the native
(untagged) VLAN.
Stefan
/etc/network/interfaces:
auto lo
iface lo inet loopback
iface enp9s0f1 inet manual
# Uplink for vmbr0
auto vmbr0
iface vmbr0 inet static
address 192.168.20.2/23
gateway 192.168.20.1
bridge_ports enp9s0f1
bridge_stp off
bridge_fd 0
# Host Management
iface enp11s0f0 inet manual
# Uplink for vmbr1
auto vmbr1
iface vmbr1 inet manual
bridge_ports enp9s0f0
bridge_stp off
bridge_fd 0
# Bridge for VMs on the Internet
iface enp11s0f1 inet manual
# Uplink for vmbr2
auto vmbr2
iface vmbr2 inet manual
bridge_ports enp11s0f1
bridge_stp off
bridge_fd 0
# Bridge for VMs on network 192.168.30.0/24
iface enp9s0f0 inet manual# Trunk interface carrying VLAN20 and VLAN30
auto vmbr10iface vmbr10 inet manual
bridge_ports enp9s0f0
bridge_stp off
bridge_fd 0
# Bridge for untagged traffic on trunk interface
auto vmbr20iface vmbr20 inet manual
bridge_ports enp9s0f0.20
bridge_stp off
bridge_fd 0
# Bridge for VMs on VLAN20
auto vmbr30iface vmbr30 inet manual
bridge_ports enp9s0f0.30
bridge_stp off
bridge_fd 0
# Bridge for VMs on VLAN30
iface enp3s0 inet manual
iface enp2s0 inet manual
On Feb 16, 2021, at 21:52, Steve Frazier <[email protected]> wrote:
Tried it and it worked as you explained! Thanks Stefan. I am taking this step
by step.I haven't tried the 192.168.30.0 nic yet but will shortly.
I will want to be able to trunk VLAN 20 and VLAN 30 down a NIC so that I will
be able to use my VOIP phones on VLAN30 and be able to offer VLAN20 for the
attached work stations, any suggestions and/or configuration file to do this?
Thanks again for your help!
On Tuesday, February 16, 2021, 01:52:54 PM EST, Stefan M. Radman <[email protected]>
wrote:
Hi Steve
Attached and below is an /etc/network/interfaces that should do what you want.
Just* keep interface enp9s0f1 connected to your private subnet 192.168.20.2/23*
connect interface enp9s0f0 to your internet subnet* connect internet VMs to
vmbr1* connect interface enp11s0f1 to your private subnet 192.168.30.2/23*
connect VMs on subnet 192.168.30.2/23 to vmbr2 If you keep the comment lines
(#) they'll show up in the web interface as well.
Disclaimer: I did not test it but it should give you the right idea to go ahead.
Stefan
/etc/network/interfaces:
auto loiface lo inet loopback
iface enp9s0f1 inet manual# Uplink for vmbr0
auto vmbr0iface vmbr0 inet static address 192.168.20.2/23 gateway
192.168.20.1 bridge_ports enp9s0f1 bridge_stp off
bridge_fd 0# Host Management
iface enp11s0f0 inet manual# Uplink for vmbr1
auto vmbr1iface vmbr1 inet manual bridge_ports enp9s0f0
bridge_stp off bridge_fd 0# Bridge for VMs on the Internet
iface enp11s0f1 inet manual# Uplink for vmbr2
auto vmbr2iface vmbr2 inet manual bridge_ports enp11s0f1
bridge_stp off bridge_fd 0# Bridge for VMs on network 192.168.30.0/24
iface enp9s0f0 inet manual
iface enp3s0 inet manual
iface enp2s0 inet manual
On Feb 14, 2021, at 18:29, Steve Frazier via pve-user
<[email protected]> wrote:
From:Steve Frazier <[email protected]>
Subject:Re: [PVE-User] Adding an Internet NIC to existing Proxmox
Date:February 14, 2021 at 18:29:14 GMT+1
To:"[email protected]" <[email protected]>
Here is my "interfaces" file:
auto loiface lo inet loopback
iface enp9s0f1 inet manual
auto vmbr0iface vmbr0 inet static address 192.168.20.2/23 gateway
192.168.20.1 bridge_ports enp9s0f1 bridge_stp off
bridge_fd 0
iface enp11s0f0 inet manual
iface enp11s0f1 inet manual
iface enp9s0f0 inet manual
iface enp3s0 inet manual
iface enp2s0 inet manual
On Sunday, February 14, 2021, 12:14:28 PM EST, Steve Frazier via pve-user
<[email protected]> wrote:
I need some help. I am new to Proxmox. I have it set up now using (1) one
NIC to an internal network of 192.168.20.0/23 and I would like to use another
NIC I have available for the internet which has (5) available IPs.
I have attached a view of my existing network.
I would like to set up an additional (NIC) when would allow me to assign to a
virtual server that has two virtual NICs with one being the internet and the
other being my internal network.
While I am at it, I have another networking 192.168.30.0/24 that I would like
to assign to an available NIC so that I could assign virtual servers to that
NICat a later time.
Could someone please help me on how to do this
Thanks very much.
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
[email protected]
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.proxmox.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpve-user&data=04%7C01%7Csmr%40kmi.com%7Cfb3db335b1844cd9162208d8d10e1613%7Cc2283768b8d34e008f3d85b1b4f03b33%7C0%7C0%7C637489205732810378%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bbtAAx1zpomz3hCKtKmrW3UIFF6iyprwmGcer1Q0njQ%3D&reserved=0
CONFIDENTIALITY NOTICE: This communication may contain privileged and
confidential information, or may otherwise be protected from disclosure, and is
intended solely for use of the intended recipient(s). If you are not the
intended recipient of this communication, please notify the sender that you
have received this communication in error and delete and destroy all copies in
your possession.
CONFIDENTIALITY NOTICE:This communication may contain privileged and
confidential information, or may otherwise be protected from disclosure, and is
intended solely for use of the intended recipient(s). If you are not the
intended recipient of this communication, please notify the sender that you
have received this communication in error and delete and destroy all copies in
your possession.
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
CONFIDENTIALITY NOTICE:This communication may contain privileged and
confidential information, or may otherwise be protected from disclosure, and is
intended solely for use of the intended recipient(s). If you are not the
intended recipient of this communication, please notify the sender that you
have received this communication in error and delete and destroy all copies in
your possession.
--- End Message ---
