Messages

I am finally getting back to work on setting up cron jobs to start and stop wireguard instances at a specific time each day and I was wondering if there is a way to add these commands to the drop-down menu in the cron section so I could pick to them from the menu and just add the cron times in the web GUI?

Thank again for all your help.

-Flamez

I noticed that I was getting similar errors like that in the wireguard logs. I applied the patch you provided, and I am no longer getting any errors in the logs.

Thank you,

-Flamez

That worked!   Reviewing the firmware plugins page, I noticed it showed the plugin os-wireguard-devel (misconfigured). Is the normal since it's a development version?  I did notice under vpn/wireguard there is a log file tab now.  It shows 3 errors, and everything seems to be working ok.


Thank you so much for your help with this.  I will continue to test and let you know if i run into any issues.

-Flamez

I first removed the wireguard plugin and then installed the os-wireguard-devel.  I did a reboot of the firewall, and everything came online normal. Reviewing the firmware plugins page, I noticed it showed the plugin os-wireguard-devel (misconfigured).   It did not show this before.  Both vpn tunnels seem to be working just fine.

What would be the correct command to start or stop an individual vpn tunnel?

Thank you,

-Flamez

Thank you for the fast response.  Looking forward to the update.

-Flamez

I am wanting to stop and start a couple different wireguard tunnels at a preset time each day. I used to be able to do this with OpenVPN using "pluginctl -s openvpn start <tunnel name>" inside a cron job.

So far, I have only been able to use pluginctl -s wireguard start to start and pluginctl -s wireguard stop. This start/stops all wireguard tunnels at the same time.   I tried using the tunnel name and it didn't work.

Any ideas?

Thank you.

I wanted to say Thank You koushun!!!   You're step by step guide helped me get nordlynx working.

Awesome upgrade!   Everything is working great!   Thank you!

I just noticed this patch will fix the issue i was reporting.  Applied it and it resolved my issue.

https://github.com/opnsense/core/commit/8a3040fecdd93bd9bf457c281b7994e92c166ede

I will do better next time and provide screenshots. 

-Flamez

Looks like this fix below is missing in the latest update (OPNsense 23.1.6-amd64). I may be wrong, but it's not showing on my box after updating.


A hotfix release was issued as 23.1.5_4:

o openvpn: fix typo in widget missing virtual address display

I have also ran into this issue.  It was working before updating from 23.1_2. to 23.1_3.

I wanted to provide an update.  The only way I can get a static IP from my new fiber ISP is to move to their 2-gig fiber plan. I really don't need the extra speed, but it will finally get me a static IP and allow me to remote into my servers. My ISP is using CGnat and will not allow access to the fiber ONT and this is only solution they are offering.

My fiber ONT is a 10-gig model # 621 XGS-PON ONT.  It has a 10 Gbps ethernet port.

To benefit from the additional speed, I would need to upgrade my current USW-24-G1 switch and add 10-gig card to my OPNsense box and any additional computers in my house.

Any suggestions on what equipment to purchase?   What about 2.5 gig cards?  How about only adding the 10-gig card to my OPNsense box, NAS and one computer.

I am looking for any suggestions.

Thank you.

Sorry for the delay in responding. I am working with my ISP to get a static IP assigned to me.

Thank you for your suggestions. The last call I had with my ISP the tech stated that I would be double NAT using my own router.

My old internet provider was Suddenlink using a cable modem, and I moved to a new internet provider which had fiber 1 gig service.  The new ISP installed a Adtran SDX 621 XGS-PON ONT and fiber is connected to it and then I connected the network jack from the ONT to my opnsense box. I cannot access the web GUI of the ONT.  Looking at Opnsense I can see the wan gateway of the ONT is set to 100.64.xx.x range by my ISP. My Opnsense box is setup to use 192.168.2.x.  On my old cable modem setup, I could access my home server equipment using VPN. This stopped working when I moved to the new Fiber ISP.  When I performed a tracert it showed the first few hops as private address provided by my new Fiber ISP. 

Hopefully this helps.  Sorry I should have provided more information in my first post.