Yes, that would be a good test. It's hard to see how something in the config could do that, it seems more likely something in the filesystem has become out of sync somehow. Never seen it before though.

Of course if you are NATing between WAN and LAN (most soho installs) adding a rule like that will only allow traffic to reach services on the firewall itself. You would need inbound NAT rules to reach anything behind the firewall.

Steve

Do you mean?: /tmp/bootup_messages

If you reboot after removing it does the file return at a size you can open? What's in it?

Steve

@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.

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 ?