Menu

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.

Show posts Menu

Messages - LorneMalvo

#1
My OS are Windows 11. Network time services running, checked on 2 different computers. Checked logs, and they say problems related to network connection.

For trying something different, just downloaded open source NTP client compatible with windows and boom, working fine.. With non native Windows NTP client everything is working perfectly. Even with Firewall rule disabled. It must be a Windows 11 bug.

I'll use this open source client for now. Trully don't trust Windwos 11 stability.

Thank you very much for your kind assistance and all your advice. I'm sorry you lost time on this.
#2
Hello,
Changes done. But problem persist, opnsense itself is getting NTP hour, but not LAN clients.

See attached rule, I think it's OK.



#3
Here you have.
#4
Hi Patrick.
Thank you very much for your answer.

I've tried the following rule in LAN, but isn't working:



What I'm doing wrong? I've checked live logs and I can see WAN NTP logs working, but nothing about LAN.. Enable Logging on rule is marked.
#5
These are my autom. LAN rules:



These are my autom. WAN rules:



Is there anything suspicius?

Thanks.
#6
Hi,
I didn't notice, but for a long time ago my devices can't communicate with NTP servers.

I've checked OPNSense NTP service status and is working fine with multiple external NTP servers.

I've tried to config my OPNSense as main NTP Servers on my network device but again, can't communicate with NTP Server.

I've checked 123 traffic on Firewall live log but i can't see nothing. What I'm missing?

My Firewall does have NTP connection outside my net, but my network not. Clearly is firewall rules issue, how to address it with safe aproach in mind?

Thank you very much.

#7
20.7 Legacy Series / Re: Port Forwarding
January 22, 2021, 04:23:12 PM
My ISP was using CG Nat a few months ago. I asked them and they gave me a public IP Address, and since then I've opened ports without any trouble using OpenWRT.

They changed some config because now i can't open ports neither in OpenWRT or OpnSense. I'll talk with my ISP because it's so rare.

Thank you all of you for your help.
#8
20.7 Legacy Series / Re: Port Forwarding
January 15, 2021, 05:03:07 PM
Hello,
Thanks for your answer.
This is the Wan rule: https://i.imgur.com/ucRDzX1.png
And here we can see correctly created: https://i.imgur.com/Kbkfsw7.png

Do I have something wrong?

#9
20.7 Legacy Series / Port Forwarding
January 12, 2021, 08:55:14 PM
Hello,
I'm trying to open a range of ports and I can't get it to work.
I've been following this tutorial without success: https://forum.opnsense.org/index.php?topic=8783.0

I'm testing opened ports through an external website. I hope this is fine.

See attached images for more info.
https://i.imgur.com/Tr9qBgZ.png
https://i.imgur.com/KH4gZZI.png

Any help?

Thanks.
#10
Thanks for this fix. I was having the same problem after an upgrade.
#11
20.7 Legacy Series / Re: Testing Shaper
January 07, 2021, 08:53:49 PM
Quote from: Voodoo on January 03, 2021, 10:42:28 PM
@LornMalvo I can't find the thread but it was confirmed that there is a bug with the traffic shaper.

The higher the bandwidth limit the more it drifts off.

I'm also affected by it but it doesn't bother me.

Hi. Thanks for the info. I was sure this is a bug. I posted this with the hope devs can see this.
#12
20.7 Legacy Series / Testing Shaper
December 30, 2020, 04:47:39 PM
Hello,
I've installed OPNSense for the first time a few days ago and I'm doing some testing on QoS.

I've followed tutorials and created a Pipe because I want to limit bandwith. I have 600/600 optic fiber and I configured a bandwith limit of 550Mbit/s. When i do some download and upload tests, i get a maximum speed of 300Mbit/s +/-. It seems like the Pipe speed isn't working well, if I want to reach the 550Mbit/s target, I have to put a bandwith limit of 700 instead of 550.

I am doing something wrong or is this a bug?

Thanks.