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.

Messages - allebone

Pages: 1 2 [3] 4 5 ... 25

Hardware and Performance / Re: Deciso DEC850 - CPU speed goes up only to 1500MHz instead of 3100MHz?

« on: January 31, 2022, 06:11:53 pm »

I see what you mean, sorry no. I am using an intel on a protectli box. I was unaware AMD dont allow reporting of the frequency above the base clock. I guess intel must be different because mine seems to report.

Hardware and Performance / Re: Deciso DEC850 - CPU speed goes up only to 1500MHz instead of 3100MHz?

« on: January 31, 2022, 05:13:01 pm »

Strange, I do see a difference between my results and the people affected. Mine does show frequencies above 2700 which you can see above, as the CPU can turbo to 3100. Im wondering if a little more checking should be performed personally.

Hardware and Performance / Re: Deciso DEC850 - CPU speed goes up only to 1500MHz instead of 3100MHz?

« on: January 30, 2022, 10:07:47 pm »

If I use the command:

sudo powerd -v

I see the similar:
load 39%, current freq 1104 MHz ( 0), wanted freq 3163 MHz
load 101%, current freq 1104 MHz ( 0), wanted freq 5400 MHz
load 20%, current freq 1104 MHz ( 0), wanted freq 5231 MHz
load 8%, current freq 1104 MHz ( 0), wanted freq 5067 MHz
load 0%, current freq 1104 MHz ( 0), wanted freq 4908 MHz
load 18%, current freq 1104 MHz ( 0), wanted freq 4754 MHz
load 14%, current freq 1104 MHz ( 0), wanted freq 4605 MHz
load 7%, current freq 1104 MHz ( 0), wanted freq 4461 MHz

So this command does not seem like a good test. If I use this command I do see frequency changing higher:

gnu-watch "sysctl -a dev.cpu | grep 'freq_levels\|freq'"

dev.cpu.3.freq_levels: 2700/-1
dev.cpu.3.freq: 1003
dev.cpu.2.freq_levels: 2700/-1
dev.cpu.2.freq: 1399
dev.cpu.1.freq_levels: 2700/-1
dev.cpu.1.freq: 3035
dev.cpu.0.freq_levels: 2700/-1
dev.cpu.0.freq: 2812

Not sure if you see similar?

Hardware and Performance / Re: Pretectli FW6E up to the task?

« on: January 26, 2022, 03:39:42 am »

Not sure but if this is just for home then out of those protectli boxes you referenced the FW6C looks more than enough. You wont need more than 16gb ram. Its more expensive though than what you found on ebay but has no fan so would be super quiet at home.

Hardware and Performance / Re: Pretectli FW6E up to the task?

« on: January 25, 2022, 08:50:29 pm »

How many users behind the device? You wont need so much RAM as opnsense doesnt use that much.

Intrusion Detection and Prevention / Re: Block connection to IPs which are not in DNS cache

« on: December 02, 2021, 02:06:52 pm »

This sounds like a problem for Zenarmor (sensei) to solve, not for opnsense. You should ask them if they can or have plans to do this.

Virtual private networks / Re: Wireguard-go multiple endpoints question

« on: December 01, 2021, 04:39:31 am »

No you only need one local config. You will need to check you are not missing steps when adding additional endpoints or misconfiguring.

21.7 Legacy Series / Re: Wireguard road warrior (followed default guide) - all work but cant ping clients

« on: November 30, 2021, 10:55:59 pm »

Its ios specific I believe. I have tested this at a nearby location that has the same lan range as my local lan network. Without this setup I cant access anything on the 192.168.2.0 range as it sends it local to the coffee shop. Adding in the additional range in allowed ips sends everything over the tunnel except the default gateway of the coffee shop which is 192.168.2.1. I can make a video from my phone on Saturday showing this working if you want as I can go past but not before then unfortunately.

21.7 Legacy Series / Re: Interfaces randomly go down/unroutable

« on: November 30, 2021, 10:44:11 pm »

Ninja in your case check arp table of oth the client you are pinging from and the arp table on opnsense during the issue. Hopefully you can attach a screen and keyboard to it while its happening. Check the arp table is good as the lan is not pingable this indicates a possible issue here.

21.7 Legacy Series / Re: Wireguard road warrior (followed default guide) - all work but cant ping clients

« on: November 30, 2021, 10:25:52 pm »

Actually one thing I noticed if I dont add the specific subnets is if I happen to go to a network (eg: coffee shop) that has the same range as my home (192.168.2.0/24 is common unfortunately) then I cant get back to my home network. The 0.0.0.0 is so all traffic is sent down the tunnel.

Luckily if you add the 2 routes they get a lower metric (higher priority) (eg adding 192.168.2.x and 192.168.200.x on the iphone allowed ips) and so long as the firewall or gateway at the coffee shop is not 192.168.2.2 (my opnsense firewall IP on the LAN) then I can still connect back home despite the network overlapping.

Thanks anyway for your help.

Pete

21.7 Legacy Series / Re: Wireguard road warrior (followed default guide) - all work but cant ping clients

« on: November 30, 2021, 10:08:51 pm »

Im really sorry I found my issue. I wish I could delete this post. I found a firewall rule that was blocking it that was created in a semi dynamic way. I have multiple vlans and had created a rule to prevent communication between vlans a while back and it was blocking the traffic. Once I saw this and added an allow rule above it for the WG network it started working fine. Sorry man I dont think I can delete threads but I would as its been a waste of time for you.

Hope its not a big deal.

Pete

Pages: 1 2 [3] 4 5 ... 25