1
General Discussion / Re: I port forwarded, but why is port still closed?
« on: August 28, 2023, 05:18:25 am »
This is my home network topology:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
General Discussion / Re: I port forwarded, but why is port still closed?
« on: August 27, 2023, 04:33:07 am »
Whilst attempting to remotely connect from my phone's RealVNC app,
I ran OPNsense's Packet Capture on Interfaces WAN and LAN for port 5900 and no traffic.
I ran OPNsense's Packet Capture on Interfaces WAN and LAN for all ports and traffic.
I ran Ubuntu's GUFW and the report shows:
No 2;
Protocol TCP6;
Port 3389;
Address *;
Application gnome-remote-desktop-daemon.
No 3;
Protocol TCP6;
Port 5900;
Address *;
Application gnome-remote-desktop-daemon.
The GUFW report doesn't show port 5901?
Not sure why packets from phone aren't shown on OPNsense or Ubuntu's traffic analysis?
I ran OPNsense's Packet Capture on Interfaces WAN and LAN for port 5900 and no traffic.
I ran OPNsense's Packet Capture on Interfaces WAN and LAN for all ports and traffic.
I ran Ubuntu's GUFW and the report shows:
No 2;
Protocol TCP6;
Port 3389;
Address *;
Application gnome-remote-desktop-daemon.
No 3;
Protocol TCP6;
Port 5900;
Address *;
Application gnome-remote-desktop-daemon.
The GUFW report doesn't show port 5901?
Not sure why packets from phone aren't shown on OPNsense or Ubuntu's traffic analysis?
3
General Discussion / Re: Help installing vm router OPNsense on KVM
« on: August 27, 2023, 04:14:35 am »
Yes.
A totally different process from using TUI, which is unnecessary and over complicates configuration.
I solved the setup by using Ubuntu's GUI to add appropriate bridges.
A totally different process from using TUI, which is unnecessary and over complicates configuration.
I solved the setup by using Ubuntu's GUI to add appropriate bridges.
4
General Discussion / I port forwarded, but why is port still closed?
« on: August 26, 2023, 07:52:11 am »
Hello, please help me port forward VNC 5900 for remote viewing.
I'm running vm router OPNsense 23.1.11_1-amd64
FreeBSD 13.1-RELEASE-p8
OpenSSL 1.1.1u 30 May 2023
These are the steps I processed:
Guide for Ubuntu, Access a remote desktop. https://ubuntu.com/tutorials/access-remote-desktop#1-overview
1: Ubuntu 22.04.3 LTS jammy > Sharing is turned on.
2: VMM 4.0.0 is running VM OPNsense port forwarded to 3389 for RDP as well as 5900 and 5901 for VNC.
OPNsense > Firewall > NAT > Port Forward >
3: I tested the port is forwarded, GRC Shields UP shows 3389, 5900 and 5901 have the status: stealth.
4: I also tested from my phone's RealVNC app with publicWanIP, publicWanIP:3389, publicWanIP:5900 and publicWanIP:5901, but error: The connection attempt timed out.
I'm running vm router OPNsense 23.1.11_1-amd64
FreeBSD 13.1-RELEASE-p8
OpenSSL 1.1.1u 30 May 2023
These are the steps I processed:
Guide for Ubuntu, Access a remote desktop. https://ubuntu.com/tutorials/access-remote-desktop#1-overview
1: Ubuntu 22.04.3 LTS jammy > Sharing is turned on.
2: VMM 4.0.0 is running VM OPNsense port forwarded to 3389 for RDP as well as 5900 and 5901 for VNC.
OPNsense > Firewall > NAT > Port Forward >
- Interface: WAN, Proto: TCP, Address: *, Ports: *, Address: WAN address, Ports: 3389 (MS RDP), IP: 192.168.1.120, Ports: 3389 (MS RDP), Description: RDP.
- Interface: WAN, Proto: TCP, Address: *, Ports: *, Address: WAN address, Ports: 5900 (VNC), IP: 192.168.1.120, Ports: 5900 (VNC), Description: VNC 5900.
- Interface: WAN, Proto: TCP, Address: *, Ports: *, Address: WAN address, Ports: 5901, IP: 192.168.1.120, Ports: 5901, Description: VNC 5901.
3: I tested the port is forwarded, GRC Shields UP shows 3389, 5900 and 5901 have the status: stealth.
4: I also tested from my phone's RealVNC app with publicWanIP, publicWanIP:3389, publicWanIP:5900 and publicWanIP:5901, but error: The connection attempt timed out.
5
General Discussion / Help installing vm router OPNsense on KVM
« on: May 11, 2023, 08:34:32 am »
Having some trouble pinging the VM guest OPNsense from the host VMM.
Here's my diagram/topology of the setup:
Host machine runs Ubuntu 22.04 Desktop and Virtual Machine Manager 4.0.0.
ISP router is bridged and Internet traffic is via NIC0 to the host machine.
2 physical NICs:
NIC0=WAN=enp3s0=a8:a1:59:6e:1f:8b=br0=0a:d4:78:1f:cd:41=vtnet0=52:54:00:c9:2f:af.
NIC1=LAN=enp2s0=1c:61:b4:6d:3B:4f=br1=d2:da:46:a2:b2:3e=vtnet1=52:54:00:ad:30:31.
I setup bridges, which show connected:
shortcuts: hit alt+s to submit/post or alt+p to preview
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
SMF 2.0.19 | SMF © 2021, Simple Machines
Privacy Policy | XHTML | RSS | WAP2
Here's my diagram/topology of the setup:
Host machine runs Ubuntu 22.04 Desktop and Virtual Machine Manager 4.0.0.
ISP router is bridged and Internet traffic is via NIC0 to the host machine.
2 physical NICs:
NIC0=WAN=enp3s0=a8:a1:59:6e:1f:8b=br0=0a:d4:78:1f:cd:41=vtnet0=52:54:00:c9:2f:af.
NIC1=LAN=enp2s0=1c:61:b4:6d:3B:4f=br1=d2:da:46:a2:b2:3e=vtnet1=52:54:00:ad:30:31.
I setup bridges, which show connected:
Code: [Select]
ubuntu@ubuntu:/etc/netplan$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0ad4781fcd41 yes enp3s0
vnet0
br1 8000.d2da46a2b23e yes enp2s0
virbr0 8000.52540088b4b4 yes
ubuntu@ubuntu:/etc/netplan$ bridge link show
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br1 state listening priority 32 cost 100
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
8: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
ubuntu@ubuntu:/etc/netplan$ nmcli conn show --active
NAME UUID TYPE DEVICE
netplan-br1 2f1c114b-0956-3743-a28b-800770c11963 bridge br1
netplan-br0 00679506-5c05-3c3d-bdfe-474849762078 bridge br0
virbr0 5cfb435c-dc5a-4741-8538-1664c7cb3693 bridge virbr0
vnet0 bd70d929-245f-4f7c-a870-3ebd51dfc6a5 tun vnet0
netplan-enp2s0 7ea6f90b-3495-3533-948a-ef0035687c34 ethernet enp2s0
netplan-enp3s0 6effa1b1-280b-3785-9b52-c723b445fb3e ethernet enp3s0 I edited the host Ubuntu's Network Manager so the host's LAN will ping the guest OPNsense router:Code: [Select]
ubuntu@ubuntu:/etc/netplan$ cat 01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
addresses: [192.168.1.120/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.8.4]
enp3s0:
dhcp4: no
bridges:
br0:
dhcp4: yes
interfaces:
- enp3s0
br1:
dhcp4: yes
interfaces:
- enp2s0
Host connections show no IP address 192.168.1.120?Code: [Select]
ubuntu@ubuntu:/etc/netplan$ ip -c 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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::31ca:9227:dcb3:d09e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
link/ether a8:a1:59:6e:1f:8b brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:88:b4:b4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0a:d4:78:1f:cd:41 brd ff:ff:ff:ff:ff:ff
inet 100.76.25.213/10 brd 100.127.255.255 scope global dynamic noprefixroute br0
valid_lft 217sec preferred_lft 217sec
inet6 2406:2d40:4100:8fb2:c261:34a2:7275:ff6e/64 scope global temporary dynamic
valid_lft 201sec preferred_lft 51sec
inet6 2406:2d40:4100:8fb2:8d4:78ff:fe1f:cd41/64 scope global dynamic mngtmpaddr
valid_lft 201sec preferred_lft 51sec
inet6 fe80::8d4:78ff:fe1f:cd41/64 scope link
valid_lft forever preferred_lft forever
8: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:c9:2f:af brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fec9:2faf/64 scope link
valid_lft forever preferred_lft forever
9: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether fe:54:00:ad:30:31 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fead:3031/64 scope link
valid_lft forever preferred_lft forever
499: br1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether d2:da:46:a2:b2:3e brd ff:ff:ff:ff:ff:ff
+ Attachments and other optionsshortcuts: hit alt+s to submit/post or alt+p to preview
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
SMF 2.0.19 | SMF © 2021, Simple Machines
Privacy Policy | XHTML | RSS | WAP2
6
General Discussion / Help installing vm router OPNsense on KVM
« on: May 11, 2023, 08:32:41 am »
Having some trouble pinging the VM guest OPNsense from the host VMM.
Here's my diagram/topology of the setup:
Host machine runs Ubuntu 22.04 Desktop and Virtual Machine Manager 4.0.0.
ISP router is bridged and Internet traffic is via NIC0 to the host machine.
2 physical NICs:
NIC0=WAN=enp3s0=a8:a1:59:6e:1f:8b=br0=0a:d4:78:1f:cd:41=vtnet0=52:54:00:c9:2f:af.
NIC1=LAN=enp2s0=1c:61:b4:6d:3B:4f=br1=d2:da:46:a2:b2:3e=vtnet1=52:54:00:ad:30:31.
I setup bridges, which show connected:
Here's my diagram/topology of the setup:
Host machine runs Ubuntu 22.04 Desktop and Virtual Machine Manager 4.0.0.
ISP router is bridged and Internet traffic is via NIC0 to the host machine.
2 physical NICs:
NIC0=WAN=enp3s0=a8:a1:59:6e:1f:8b=br0=0a:d4:78:1f:cd:41=vtnet0=52:54:00:c9:2f:af.
NIC1=LAN=enp2s0=1c:61:b4:6d:3B:4f=br1=d2:da:46:a2:b2:3e=vtnet1=52:54:00:ad:30:31.
I setup bridges, which show connected:
Code: [Select]
ubuntu@ubuntu:/etc/netplan$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0ad4781fcd41 yes enp3s0
vnet0
br1 8000.d2da46a2b23e yes enp2s0
virbr0 8000.52540088b4b4 yes
ubuntu@ubuntu:/etc/netplan$ bridge link show
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br1 state listening priority 32 cost 100
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
8: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
ubuntu@ubuntu:/etc/netplan$ nmcli conn show --active
NAME UUID TYPE DEVICE
netplan-br1 2f1c114b-0956-3743-a28b-800770c11963 bridge br1
netplan-br0 00679506-5c05-3c3d-bdfe-474849762078 bridge br0
virbr0 5cfb435c-dc5a-4741-8538-1664c7cb3693 bridge virbr0
vnet0 bd70d929-245f-4f7c-a870-3ebd51dfc6a5 tun vnet0
netplan-enp2s0 7ea6f90b-3495-3533-948a-ef0035687c34 ethernet enp2s0
netplan-enp3s0 6effa1b1-280b-3785-9b52-c723b445fb3e ethernet enp3s0 I edited the host Ubuntu's Network Manager so the host's LAN will ping the guest OPNsense router:Code: [Select]
ubuntu@ubuntu:/etc/netplan$ cat 01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
addresses: [192.168.1.120/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.8.4]
enp3s0:
dhcp4: no
bridges:
br0:
dhcp4: yes
interfaces:
- enp3s0
br1:
dhcp4: yes
interfaces:
- enp2s0
Host connections show no IP address 192.168.1.120?Code: [Select]
ubuntu@ubuntu:/etc/netplan$ ip -c 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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::31ca:9227:dcb3:d09e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
link/ether a8:a1:59:6e:1f:8b brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:88:b4:b4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0a:d4:78:1f:cd:41 brd ff:ff:ff:ff:ff:ff
inet 100.76.25.213/10 brd 100.127.255.255 scope global dynamic noprefixroute br0
valid_lft 217sec preferred_lft 217sec
inet6 2406:2d40:4100:8fb2:c261:34a2:7275:ff6e/64 scope global temporary dynamic
valid_lft 201sec preferred_lft 51sec
inet6 2406:2d40:4100:8fb2:8d4:78ff:fe1f:cd41/64 scope global dynamic mngtmpaddr
valid_lft 201sec preferred_lft 51sec
inet6 fe80::8d4:78ff:fe1f:cd41/64 scope link
valid_lft forever preferred_lft forever
8: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:c9:2f:af brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fec9:2faf/64 scope link
valid_lft forever preferred_lft forever
9: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether fe:54:00:ad:30:31 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fead:3031/64 scope link
valid_lft forever preferred_lft forever
499: br1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether d2:da:46:a2:b2:3e brd ff:ff:ff:ff:ff:ff
7
General Discussion / What is the VMM Network selection for a LAN and WAN NIC
« on: April 13, 2023, 08:39:44 am »
I am building pretty much a similar setup to Proxmox which is a host running a VM router for traffic for the LAN and WAN. As Proxmox uses KVM, I thought it should work direct from my machine's KVM?
My setup:
1 bridged router.
1 machine running Debian based OS Ubuntu 22.04.
2 physical LAN and WAN wired NICs.
1 host/hypervisor/VMM KVM/Qemu/Virtual Machine Manager 4.0.0.
1 guest/VM router OPNsense 23.1.
I need the LAN (including the host machine) and WAN to route traffic via the VM router only.
The machine recognises the 2 NICs.
I think the host needs 1 or 2 bridges to the machine's physical LAN and WAN NICs?
Here's my network topology which may not be the right setup, attached.
Configuring the network has a few options like
GUI: Virtual Manager.
TUI: Network scripts, Nmcli tool or Virsh command.
I tried the host GUI: New VM > Create a new virtual machine > Step 5 of 5 > Ready to begin the installation > Network selection > Bridge device… > Device name: enp3s0 > Finish > Unable to complete install: ‘Unable to add bridge enp3s0 port vnet0: Operation not supported’.
Details:
The host has an option for Macvtap device, but I don't know what this is?
My setup:
1 bridged router.
1 machine running Debian based OS Ubuntu 22.04.
2 physical LAN and WAN wired NICs.
1 host/hypervisor/VMM KVM/Qemu/Virtual Machine Manager 4.0.0.
1 guest/VM router OPNsense 23.1.
I need the LAN (including the host machine) and WAN to route traffic via the VM router only.
The machine recognises the 2 NICs.
I think the host needs 1 or 2 bridges to the machine's physical LAN and WAN NICs?
Here's my network topology which may not be the right setup, attached.
Configuring the network has a few options like
GUI: Virtual Manager.
TUI: Network scripts, Nmcli tool or Virsh command.
I tried the host GUI: New VM > Create a new virtual machine > Step 5 of 5 > Ready to begin the installation > Network selection > Bridge device… > Device name: enp3s0 > Finish > Unable to complete install: ‘Unable to add bridge enp3s0 port vnet0: Operation not supported’.
Details:
Code: [Select]
Unable to complete install: 'Unable to add bridge enp3s0 port vnet0: Operation not supported'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install
installer.start_install(guest, meter=meter)
File "/usr/share/virt-manager/virtinst/install/installer.py", line 695, in start_install
domain = self._create_guest(
File "/usr/share/virt-manager/virtinst/install/installer.py", line 637, in _create_guest
domain = self.conn.createXML(initial_xml or final_xml, 0)
File "/usr/lib/python3/dist-packages/libvirt.py", line 4400, in createXML
raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: Unable to add bridge enp3s0 port vnet0: Operation not supported
The host has an option for Macvtap device, but I don't know what this is?
8
General Discussion / Re: Hypervisor configuration not adding 2 NICs for virtual OPNsense
« on: April 13, 2023, 08:09:56 am »
I solved this by using VM GUI.
9
General Discussion / Re: Extracting iso bz2 file error
« on: April 12, 2023, 04:33:15 pm »
Can't see how to delete the post, but I solved it by using a different TUI command.
10
General Discussion / Extracting iso bz2 file error
« on: April 12, 2023, 04:03:30 pm »
Hello, I downloaded OPNsense-23.1-OpenSSL-dvd-amd64.iso.bz2 from https://opnsense.org/download/ and the checksum matches the website.
I extract the file in Ubuntu 22.04 and receive error:
There was an error while extracting "OPNsense-23.1-OpenSSL-dvd-amd64.iso.bz2". Ignoring out-of-order file @40f5ee (usr/sbin/chown) 481060864 < 1506377728
I searched for some solutions, but no luck so far.
I extract the file in Ubuntu 22.04 and receive error:
There was an error while extracting "OPNsense-23.1-OpenSSL-dvd-amd64.iso.bz2". Ignoring out-of-order file @40f5ee (usr/sbin/chown) 481060864 < 1506377728
I searched for some solutions, but no luck so far.
11
General Discussion / Hypervisor configuration not adding 2 NICs for virtual OPNsense
« on: March 24, 2023, 02:45:43 am »
I am trying to build:
1 bridged router.
2 physical wired NICs for WAN and LAN.
1 machine running Debian based OS, running hypervisor KVM/Qemu/Virt manager.
1 VM router OPNsense.
The machine sees the 2 NICs, however the hypervisor seems to set up 1 virtual bridge?
I think I need 2 bridges to see the 2 NICs?
Here's my network topology, attached.
Configuring the network has a few options like
GUI: Virtual Manager.
TUI: Network scripts, Nmcli tool or Virsh command.
I tried the GUI, but Virtual Manager seems to show 1 NIC using Virtual Network Interface with a Network source: Virtual network 'default':NAT. I'm wondering why Virtual Manager only shows 1 NIC and a NIC unrelated to my 2 physical NICs?
Virtual manager has an option in Virtual Network Interface Network source to select Host device enp2s0:macvtap. Maybe this should be selected for 1 of my 2 physics NICs?
Creating a new VM in the hypervisor offers an option at Network selection as default, Virtual network 'default':NAT, however maybe I should select the option: Host device enp2s0:macvtap, Source mode: Bridge?
Regardless, after selecting enp2s0:macvtap, the VM router OPNsense installs and only shows 1 LAN (vtnet0) -> v4: 192.168.1.1/24.
In VM router OPNsense install, I select 1) Assign interfaces and the only valid interfaces are:
vtnet0 52:54:00:6c:84:7a VirtIO Networking Adapter.
This interface is Virtual Manager's NIC MAC address, not any of my 2 physical NICs' MAC addresses?
I tried the TUI Network scripts, creating this file in /etc/network/interfaces, however same issue?
1 bridged router.
2 physical wired NICs for WAN and LAN.
1 machine running Debian based OS, running hypervisor KVM/Qemu/Virt manager.
1 VM router OPNsense.
The machine sees the 2 NICs, however the hypervisor seems to set up 1 virtual bridge?
I think I need 2 bridges to see the 2 NICs?
Here's my network topology, attached.
Configuring the network has a few options like
GUI: Virtual Manager.
TUI: Network scripts, Nmcli tool or Virsh command.
I tried the GUI, but Virtual Manager seems to show 1 NIC using Virtual Network Interface with a Network source: Virtual network 'default':NAT. I'm wondering why Virtual Manager only shows 1 NIC and a NIC unrelated to my 2 physical NICs?
Virtual manager has an option in Virtual Network Interface Network source to select Host device enp2s0:macvtap. Maybe this should be selected for 1 of my 2 physics NICs?
Creating a new VM in the hypervisor offers an option at Network selection as default, Virtual network 'default':NAT, however maybe I should select the option: Host device enp2s0:macvtap, Source mode: Bridge?
Regardless, after selecting enp2s0:macvtap, the VM router OPNsense installs and only shows 1 LAN (vtnet0) -> v4: 192.168.1.1/24.
In VM router OPNsense install, I select 1) Assign interfaces and the only valid interfaces are:
vtnet0 52:54:00:6c:84:7a VirtIO Networking Adapter.
This interface is Virtual Manager's NIC MAC address, not any of my 2 physical NICs' MAC addresses?
I tried the TUI Network scripts, creating this file in /etc/network/interfaces, however same issue?
Code: [Select]
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
# ip -c a, for interface details.
# loopback device.
auto lo
iface lo inet loopback
# WAN port (NIC1, top of case with I/O shield stuff).
auto enp3s0
iface enp3s0 inet manual
# LAN port (NIC2, bottom of case at PCIe slot).
auto enp2s0
iface enp2s0 inet manual
# WAN bridge OPNsense is connected with veth0. Veth0 is the FreeBSD Network Interface Name for virtio Network devices.
auto virbr0
iface virbr0 inet static
bridge_ports enp3s0
bridge_stp off
bridge-fd 0
# LAN bridge OPNsense is connected with veth1.
# Gateway is OPNsense.
auto virbr1
iface virbr1 inet static
address 192.168.1.120/24
gateway 192.168.1.170
bridge_ports enp2s0
bridge-stp off
bridge-fd 0
bridge-pvid 4095
bridge-vlan-aware yes
bridge-vids 1-4044
# Save, exit and restart networking service:~$ sudo systemctl restart NetworkManager > Enter.
What am I doing wrong please?
12
Hardware and Performance / Re: Help finding a compatible NIC
« on: March 24, 2023, 01:41:40 am »
Thank you.
I think the issue is more to do with the KVM hypervisor adding the NIC, rather than a drive issue.
I'll open a new post https://forum.opnsense.org/index.php?topic=33195.0.
I think the issue is more to do with the KVM hypervisor adding the NIC, rather than a drive issue.
I'll open a new post https://forum.opnsense.org/index.php?topic=33195.0.
13
Hardware and Performance / Help finding a compatible NIC
« on: March 17, 2023, 12:44:36 am »
Hello, I would like some help finding a wired pcie Nic from here https://www.umart.com.au/pc-parts/networking/network-adapters/wired-pcie-adapters-972
The FreeBSD hardware list for Ethernet interfaces is about 10 years old and doesn’t help https://www.freebsd.org/releases/13.0R/hardware/#support
I bought a tp-link tg3468 but opnsense didn’t see the Nic.
linixmint OS worked fine.
The FreeBSD hardware list for Ethernet interfaces is about 10 years old and doesn’t help https://www.freebsd.org/releases/13.0R/hardware/#support
I bought a tp-link tg3468 but opnsense didn’t see the Nic.
linixmint OS worked fine.
Pages: [1]