1
Hardware and Performance / Re: OPNsense and CPUs with P- and E-cores
« on: January 01, 2024, 06:34:05 am »
Did you ever test this? I was considering this for opnsense. Obviously overkill but a good price and 10gb + 2.5gb
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
22.1 Legacy Series / Re: os-ddclient
« on: June 26, 2022, 03:31:33 am »
Hi All,
Edit: solution was to disable force ssl
Trying to configure DDclient on 22.1.9 but running into the following error (replaced IP):
Edit: solution was to disable force ssl
Trying to configure DDclient on 22.1.9 but running into the following error (replaced IP):
Code: [Select]
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="4"] WARNING: Wait at least 5 minutes between update attempts.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="3"] WARNING: last updated <never> but last attempt on Sat Jun 25 18:28:53 2022 failed.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="2"] WARNING: skipping update of example.com from <nothing> to 111.111.111.111.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84222 - [meta sequenceId="1"] WARNING: file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
3
General Discussion / Re: UDP Broadcast Relay
« on: April 07, 2021, 07:49:58 am »
@MarJohn56
What's the recommended solution to use both UPNP - 1900 and having UDPbroadcast relay handle forwarding 1900 to different subnets. I get port conflicts and surprised not more people have mentioned this as an issue.
What's the recommended solution to use both UPNP - 1900 and having UDPbroadcast relay handle forwarding 1900 to different subnets. I get port conflicts and surprised not more people have mentioned this as an issue.
4
20.7 Legacy Series / Re: No log files on Let’s Encrypt
« on: January 14, 2021, 03:24:48 am »
I just ran into this issue recently. Did you end up just recreating the log file with root and chmod it 600?
Some reason acme won't generate any log file when running. It's so strange.
Some reason acme won't generate any log file when running. It's so strange.
5
20.7 Legacy Series / Re: High Ping with passthrough on ESXI 7.0u1
« on: December 23, 2020, 12:17:12 am »
Interesting discovery, this issue is not present on OPNsense 20.1. Could this have been caused by the recent net map changes or the 12.1 HardenBSD upgrade?
Booting a HardenBSD 13 build from the same VM config with the X710 passed through it pings fine. This is looking like something specifically done in 20.7 that I cannot pin down.
Booting a HardenBSD 13 build from the same VM config with the X710 passed through it pings fine. This is looking like something specifically done in 20.7 that I cannot pin down.
6
20.7 Legacy Series / High Ping with passthrough on ESXI 7.0u1
« on: December 22, 2020, 02:18:46 am »
Hi all,
I just install OPNsense 20.7.7 onto a virtual machine using a intel x710-T4 passthrough to the opnsense VM. However, I'm running into a strange latency issue with packets dropping and taking insane amounts of time to respond back.
I have tested this on a fresh default installation with the 192.168.1.1 interface IP address and I can't determine what exactly is going on. With the intel igb0/1 interfaces no such ping issue exists. Live booting a ubuntu VM and giving it a static IP it pings as expected on the IXL0-4 interfaces as expected.
Testing the same ESXi Host with a live opnsense CD and assigning the interface to the same one (IXL0) works as expected (highest ping is 3ms), indicating this is something happening under OPNsense when the machine is being virtualized.
Below is a list of the ping results:
Reply from 192.168.1.1: bytes=32 time=204ms TTL=64
Reply from 192.168.1.1: bytes=32 time=584ms TTL=64
Reply from 192.168.1.1: bytes=32 time=498ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=587ms TTL=64
Reply from 192.168.1.1: bytes=32 time=968ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=857ms TTL=64
Reply from 192.168.1.1: bytes=32 time=78ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=62ms TTL=64
Reply from 192.168.1.1: bytes=32 time=61ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=128ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=155ms TTL=64
Reply from 192.168.1.1: bytes=32 time=155ms TTL=64
Reply from 192.168.1.1: bytes=32 time=144ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=291ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=97ms TTL=64
Reply from 192.168.1.1: bytes=32 time=187ms TTL=64
Reply from 192.168.1.1: bytes=32 time=212ms TTL=64
Reply from 192.168.1.1: bytes=32 time=56ms TTL=64
Reply from 192.168.1.1: bytes=32 time=606ms TTL=64
Reply from 192.168.1.1: bytes=32 time=587ms TTL=64
Reply from 192.168.1.1: bytes=32 time=263ms TTL=64
Reply from 192.168.1.1: bytes=32 time=237ms TTL=64
Reply from 192.168.1.1: bytes=32 time=202ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=215ms TTL=64
Reply from 192.168.1.1: bytes=32 time=849ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=115ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=248ms TTL=64
Reply from 192.168.1.1: bytes=32 time=463ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=31ms TTL=64
Reply from 192.168.1.1: bytes=32 time=77ms TTL=64
Reply from 192.168.1.1: bytes=32 time=326ms TTL=64
Reply from 192.168.1.1: bytes=32 time=616ms TTL=64
Reply from 192.168.1.1: bytes=32 time=249ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1590ms TTL=64
Reply from 192.168.1.1: bytes=32 time=307ms TTL=64
Reply from 192.168.1.1: bytes=32 time=261ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=464ms TTL=64
Reply from 192.168.1.1: bytes=32 time=158ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=250ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=294ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=124ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=231ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=248ms TTL=64
Reply from 192.168.1.1: bytes=32 time=32ms TTL=64
Reply from 192.168.1.1: bytes=32 time=276ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=135ms TTL=64
Reply from 192.168.1.1: bytes=32 time=93ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=309ms TTL=64
Reply from 192.168.1.1: bytes=32 time=67ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=218ms TTL=64
I just install OPNsense 20.7.7 onto a virtual machine using a intel x710-T4 passthrough to the opnsense VM. However, I'm running into a strange latency issue with packets dropping and taking insane amounts of time to respond back.
I have tested this on a fresh default installation with the 192.168.1.1 interface IP address and I can't determine what exactly is going on. With the intel igb0/1 interfaces no such ping issue exists. Live booting a ubuntu VM and giving it a static IP it pings as expected on the IXL0-4 interfaces as expected.
Testing the same ESXi Host with a live opnsense CD and assigning the interface to the same one (IXL0) works as expected (highest ping is 3ms), indicating this is something happening under OPNsense when the machine is being virtualized.
Below is a list of the ping results:
Reply from 192.168.1.1: bytes=32 time=204ms TTL=64
Reply from 192.168.1.1: bytes=32 time=584ms TTL=64
Reply from 192.168.1.1: bytes=32 time=498ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=587ms TTL=64
Reply from 192.168.1.1: bytes=32 time=968ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=857ms TTL=64
Reply from 192.168.1.1: bytes=32 time=78ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=62ms TTL=64
Reply from 192.168.1.1: bytes=32 time=61ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=128ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=155ms TTL=64
Reply from 192.168.1.1: bytes=32 time=155ms TTL=64
Reply from 192.168.1.1: bytes=32 time=144ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=291ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=97ms TTL=64
Reply from 192.168.1.1: bytes=32 time=187ms TTL=64
Reply from 192.168.1.1: bytes=32 time=212ms TTL=64
Reply from 192.168.1.1: bytes=32 time=56ms TTL=64
Reply from 192.168.1.1: bytes=32 time=606ms TTL=64
Reply from 192.168.1.1: bytes=32 time=587ms TTL=64
Reply from 192.168.1.1: bytes=32 time=263ms TTL=64
Reply from 192.168.1.1: bytes=32 time=237ms TTL=64
Reply from 192.168.1.1: bytes=32 time=202ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=215ms TTL=64
Reply from 192.168.1.1: bytes=32 time=849ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=115ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=248ms TTL=64
Reply from 192.168.1.1: bytes=32 time=463ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=31ms TTL=64
Reply from 192.168.1.1: bytes=32 time=77ms TTL=64
Reply from 192.168.1.1: bytes=32 time=326ms TTL=64
Reply from 192.168.1.1: bytes=32 time=616ms TTL=64
Reply from 192.168.1.1: bytes=32 time=249ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1590ms TTL=64
Reply from 192.168.1.1: bytes=32 time=307ms TTL=64
Reply from 192.168.1.1: bytes=32 time=261ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=464ms TTL=64
Reply from 192.168.1.1: bytes=32 time=158ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=250ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=294ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=124ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=231ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=248ms TTL=64
Reply from 192.168.1.1: bytes=32 time=32ms TTL=64
Reply from 192.168.1.1: bytes=32 time=276ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=135ms TTL=64
Reply from 192.168.1.1: bytes=32 time=93ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=309ms TTL=64
Reply from 192.168.1.1: bytes=32 time=67ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=218ms TTL=64
7
General Discussion / Re: UDP Broadcast Relay
« on: June 09, 2020, 10:56:12 pm »
I noticed when trying to launch the plugin I cannot successfully launch it. Running it from the CLI I get the following error. Note: This is caused by miniupnpd (Killed it and the process started okay afterwards)
root@OPNsense:/ # /usr/local/etc/rc.d/os-udpbroadcastrelay start
osudpbroadcastrelay is not running.
Starting osudpbroadcastrelay.
bind: Address already in use
rcv bind
/usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I also noticed another issue with the the black theme on opnsense you cannot read any of the plugin info at all.
https://imgur.com/a/eUPetuU
root@OPNsense:/ # /usr/local/etc/rc.d/os-udpbroadcastrelay start
osudpbroadcastrelay is not running.
Starting osudpbroadcastrelay.
bind: Address already in use
rcv bind
/usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I also noticed another issue with the the black theme on opnsense you cannot read any of the plugin info at all.
https://imgur.com/a/eUPetuU
Pages: [1]