@paolobyte Appreciate the reply, I actually ended up nuking this VM though so I'll have to spin up a new one and test it again to see. I'll report back once I do that but it might be a bit.

Usage of PRTG & Kentix SMS Gateway together may be informing you by SMS and eMail.
Perhpas not the or a low budget solution, but very well working and able to set up in 30
minutes for everybody

The pki commands in the docs are meant to be run from within the TNSR CLI, not at a shell prompt. There is no need to install any additional packages for that to work.

@tkerr Amazing job on the GUI!
I'm not an expert linux user, but i was able to follow your documentation and I did just as you said.
I set up TNSR on wmare esxi 7 using cli, setup wireguard for testing and experimenting, and setup the gui.
Again, beautiful job, and I learned alot.
tnsrgui.PNG

UPDATE, not sure why, but changing the "Adapter Type" under the VM's setting from VMXNET3 to E1000e resolved the issue.
Important to note, prior to this, I injected additional network drivers from fling in the same fashion as I did from a previous lab system where i was able to use USB network adapters with Esxi7 for a successful tnsr guest install.

Also, after injecting the network drivers from FLING, the network adapters now display as follows:
flingnet1.PNG

@derelict

OK but at what traffic level do you start seeing the misses?

I made some runs. The problem beginns above 30Gbits

stf-cap2-imix_1518-m300-d10-c16.png

stf-cap2-imix_1518-m350-d10-c16.png

stf-cap2-imix_1518-m400-d10-c16.png

And you are right. the performance without span interfaces is better. I don't know what I did wrong.

Thank you for the reply.

@swinn

Sorry about that, I do network address translation with aliases in pfSense plus for lan traffic right now

Screenshot 2023-03-29 at 8.26.06 PM.png

Again Static nat for WAN connection can also be done with port ranges 8080:8081 or 8080-8081

Screenshot 2023-03-29 at 8.27.29 PM.png

https://docs.netgate.com/pfsense/en/latest/nat/outbound.html

Does that help?

@fatred
if crowdsourcing is a thing, i have the following BTW:

526275cf9021846401076f454df9a4631a6d2676868479079e8ed78128fd3b04 TNSR-DVD-22.10-2-x86_64-jammy.iso e3b703e3b97657197d93e32bfea2913f8c135f06940c0ae64abc76e50e263c73 TNSR-DVD-23.02-3-x86_64.iso

Agreed - great start. I have been working with TNSR for 3-4 years and have found that the CLI combined with the documentation is very useful. The added benefit of a GUI will certainly increase the adoption of the platform.

@sentein Not sure what you are asking. TNSR will almost certainly be able to communicate with it at layer 2/3 it as a switch/router in the regular sense, but loading TNSR directly on it is probably not going to be possible.

After speaking to someone at Netgate, this looks like it is a potential bug with 22.10-2.

Thanks,
Mike

My specific issue came down to the fact that the BondInterface needs to be enabled before it can be used as a track-interface.

e.g.

interface bond 1 mode lacp load-balance l34 exit

NOTE: interface BondEthernet1 is not enable.

When trying to add the track-interface

rtrexllab01 tnsr(config)# interface GigabitEthernet1/0/0 rtrexllab01 tnsr(config-interface)# ip vrrp-virtual-router 1 rtrexllab01 tnsr(config-vrrp4)# tr BondEthernet0 BondEthernet0.610 GigabitEthernet1/0/0 GigabitEthernet1/0/1 TenGigabitEthernet2/0/0 TenGigabitEthernet2/0/1 rtrexllab01 tnsr(config-vrrp4)# track-interface

As seen above, the BondInterface1 is not available.

rtrexllab01 tnsr(config)# interface BondEthernet1 rtrexllab01 tnsr(config-interface)# enable rtrexllab01 tnsr(config-interface)# exit rtrexllab01 tnsr(config)# interface GigabitEthernet1/0/0 rtrexllab01 tnsr(config-interface)# ip vrrp-virtual-router 1 rtrexllab01 tnsr(config-vrrp4)# tr BondEthernet0 BondEthernet0.610 BondEthernet1 GigabitEthernet1/0/0 GigabitEthernet1/0/1 TenGigabitEthernet2/0/0 TenGigabitEthernet2/0/1 rtrexllab01 tnsr(config-vrrp4)# track-interface

BondEthernet1 is not available to use as a track-interface.

Thanks,
Mike

@machoherbivore9 Use failover on the Vswitch instead so the TNSR works like normal but Vsphere takes over the failover unnoticed.

@talwell Perhaps the subnet is not routed properly by the ISP?

@russellc

You are indeed correct. Looking though syslog I see:

Feb 10 13:33:57 tnsrlab01 ModemManager[821]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1': not supported by any plugin Feb 10 13:33:57 tnsrlab01 ModemManager[821]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0': not supported by any plugin Feb 10 13:35:05 tnsrlab01 ModemManager[821]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0': not supported by any plugin Feb 10 13:35:05 tnsrlab01 ModemManager[821]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1': not supported by any plugin Feb 10 13:49:49 tnsrlab01 vpp[1534]: vpp[1534]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.0 Feb 10 13:49:49 tnsrlab01 vpp[1534]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.0 Feb 10 13:49:49 tnsrlab01 vpp[1534]: vpp[1534]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1 Feb 10 13:49:49 tnsrlab01 vpp[1534]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1 Feb 10 14:00:04 tnsrlab01 vpp[1573]: vpp[1573]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.0 Feb 10 14:00:04 tnsrlab01 vpp[1573]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.0 Feb 10 14:00:04 tnsrlab01 vpp[1573]: vpp[1573]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1 Feb 10 14:00:04 tnsrlab01 vpp[1573]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1 Feb 10 14:01:16 tnsrlab01 vpp[1593]: vpp[1593]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1 Feb 10 14:01:16 tnsrlab01 vpp[1593]: dpdk: Unsupported PCI device 0x14e4:0x168e found at PCI address 0000:01:00.1

Thank you for the information.

Mike

@heinola Can you provide more details? SDWAN is a very broad topic.
What are you trying to accomplish with TNSR and PA?