@stephenw10 It was the most convenient bug in the history of computing.

@stephenw10 said in VoIP passing through Firewall with no audio: Ok, so that traffic is all direct, nothing goes through pfSense so it cannot be blocking it. The phones would usually start sending RTP traffic directly between each other but it relies on the PBX sending them the correct IPs to connect to. Steve I fixed by changing Network NAT Settings on PBX and poiting to pfSense.

OpenVPN can be configured as either.

The first thing is to get the client connecting so try to connect it then check the OpenVPN logs.

@stephenw10 Just to confirm, if anyone else reads this thread and have the same problem. Installing a 1G transceiver in the SFP+ port on auto negotiation, did solve my problem, and I'm using it as a WAN interface now on 1G speed.

@furom said in NTP woes: Thanks! I will have a look at that too. :) When you have time.

@alpaca EDIT: Sorry, but I had cleared my packages - and had deleted Backup/Restore pkg. How embarrassing! Reinstalled pkg, updated and everything is OK. Shame on me ... Regards, Sebastian

@steveits Unchecking "Allow IPv6" under System->Advanced->Networking seems to stop the errors... However, it should work with IPv6 enabled ?! edit** Enabled it back again, and now I don't have any errors in my log... Thank you for your help! //T

@mrjoli021 Issue has been resolved. Once I removed the DNSSec setting PfBlockerNG started up and so far Resolver has not crashed.

Putting a device in passthrough mode like that usually disables DHCP but if it doesn't I see no reason why it wouldn't work. I have configured static IPs on PPPoE parent NICs to access the modem many times. I have that setup here. Steve

@dobby_ Thanks for your reply. I have been looking into it and I think that my current switch can do basic inter vlan routing so I think I will try that. But thanks for your reply.

You could just assign the interfaces correctly at that point. To reach the console menu just assign the minimum required interfaces. So answer 'n' to vlans then set WAN as ix3 and LAN as igc1. Then you can finish booting and reset the config if you need to. Is your 4860 config complex? Steve

Hi, Just want to let you guys know that this problem is not pfsense or my current setup. I called Verizon and it has to do with that the internet which is Verizon 5G Home Internet is utilizing the same cell towers so when the iPhones connect through pfsense, Verizon is just not switching them to WIFI Calling because its on the same network.

@viragomann that did it, thanks a mil!

@gertjan I think i will test Oxidized I'll let you know on Monday, thank you for your help

@danlad2030 They are all very much of a muchness. Just remember to enable don't pull routes otherwise the default gateway for everything becomes the OpenVPN gateway. [image: 1648817351175-screenshot-2022-04-01-at-13.47.23.png]

@bmf7777 Apr 1 00:28:57 Apr 1 00:28:57 Apr 1 00:28:57 Apr 1 00:28:57 Apr 1 00:28:57 Apr 1 00:28:57 What is the order of these massages ? Top to bottom or bottom to top ? A request came in : DHCPREQUEST for 192.168.1.254 from 70:88:6b:10:5e:5d (AWAIR-R2-105E5D) via ix1 So, device 70:88:6b:10:5e:5d known as "AWAIR-R2-105E5D" wants to use 192.168.1.254. Or it was granted this lease already very recently (less then 25% of the previously accorded lease time) @bmf7777 said in Don't understand these DHCP entries: this device (.254) has been removed from my network Was this the same device ? If so, your efforts were not enough, or 'they' are not telling the truth to you, they did not disconnect it. Remove its battery, or take it for a walk in the forest. Or ban "70:88:6b:10:5e:5d". Btw : the name of the device AWAIR is a wifi device ? So, you have two more things to check : The DHCPREQUEST came to pfSense from this device. Do the answers from pfSense reach the device back, because if they don't, the device will keep requesting ... Check also your AP. Can it show you the radio strength of the connected devices, and the negotiated throughput ?

There isn't enough information to go on here, there aren't any known issues that match what you describe exactly. Are you certain your users aren't set with the privilege that denies config changes? It's a common error people make when setting up users and groups to select the entire list, which also includes the privilege which denies them the ability to change the configuration. Check the system log and see if it's logging any errors when you try to make changes. It's also possible you have a hardware problem. Some SSDs and similar media can fail into a read-only state where they won't persistently store changes.

@bingo600 said in Difference of whitebox vs SG-6100: @nimrod That is NOT correct ... Whats not correct ? Did you even watch the youtube video i posted in previous post? Im not the only one having this issue and there is a good reason why is there a jumper in the first place. Maybe you can force it to to Power-On with the jumper , and that might not be a bad choice. You dont seem to understand. What i did is not "forcing it to power on". Its the ONLY WAY to make it power on after power loss. Jumper is set to position 1-2 by default. Changing the BIOS setting does nothing. Setting the jumper to postion 2-3 powers on device as soon as the power is applied. At that point, BIOS setting is still doing nothing. Is that so difficult to accept or understand ? But I have tested the power settings on my Qotoms , and it has been doing precisely what i told it to in the Bios. And i absolutely believe what you said. Thats exactly what the problem is. You are talking about YOUR higher end device which is obviously not the same model as the cheapest device im talking about. But when the Bios is "cleared" due to checksum error (bad battery) , and the default is to "Power Off" after powerfailure, then it is what it is doing. I dont have any checksum errors, nor i have need to clear BIOS. As i said, this is brand new device. Not even month old. I will exit from this discussion, as i thought you would be open for new info. I dont know why are you taking this personally? Im very open to new info. Im just saying that MY device is not behaving same as YOUR device. This is cheap Celeron J series device, and you are having higher end i3/i5/i7 devices that are obviously designed differently. But you just seems determined to "Bash Qotom" , and that is your choice. i have absolutely no reason to bash Qotom or glorify any other brand. Im way too old for that, and this is just a cheap aluminium box that gets the job done. You need to accept the fact that this cheaper model is not built and designed the same way as the higher end Qotom devices you have. Again, im not glorifying Protectli, but from chepest FW2 model to highest end FW6E model, BIOS is behaving the same. If the hardware feature is not on the board, there will be no setting(s) for it in the BIOS. Obviously, thats not the case with Qotom. On the cheapest model that i have, there is a setting in the BIOS for a feature which is not BIOS controlled, but jumper controlled. And then, there are higher end i5 and i7 models which YOU have, and they have this same setting that actually works as it should. Thats called quality inconsistency. So what i said, are facts, not bashing. I will just not participate longer. /Bingo Never get emotionally attached to a brand. Its just a cheap metal box. I have nothing against you or Qotom. I will continue to buy them and recommend them despite the issues i had with cheapest models. At the end, you get what you pay for.