Does it reconnect as expected using the old mpd5/netgraph?

Is it failing at both IPv4 and IPv6?

If you disable IPv6 does it then reconnect correctly?

We have seen one other report from an A&A user but that failed to connect after reboot.
https://forum.netgate.com/topic/198027/if_pppoe-problems-with-php-fpm-causing-loops-resolved

Ok I don't know why but when testing it this weekend it was working. I did not change anything neither did I reinstall and fresh setup.

Would this have to do with the static routing that was setup previously but the device it was pointing to was removed the same day it was setup till recently when the client went over to the new system and was installed again. I mean it makes sens that the pbx server was speaking to the firewall and the firewall was pointing to a device on the network that was not available.
NAT is now disabled and siproxd is kinda setup.

I'll arrange to test the DNS rebinding check to disable and the preferred work around and the same for Browser HTTP_REFERER enforcement and get back if it works now. Though the client registration check for the App was an issue even before static routing was setup.

Please let me know if there is clarity needed.

@Bob-Dig thanks for your feedback again!

Yeah, I think they are assigned properly, unless I'm missing something here and PPPoE actually requires a different assignment.

assigments.png

gateways.png

Thank you!

@stephenw10 ok thank you I will try🙏🏼

The wireless interface type in pfSense is for wifi hardware in pfSense itself which is not what you have.

Your access point should simply be connected to one of the LAN ports in the 2100. Devices that connect to the AP will just get an IP from pfSense in the LAN subnet. Later you may want to move those to a new subnet so you can filter between them but I would only attempt that after first making it work as part of LAN.

The pfSense WAN should be set to PPPoE but that can only work if the upstream device is bridging the PPPoE connection correctly.

Steve

@bob-dig Vodafone gigafiber it works find on dedicated box

@stephenw10 I guess there is VLAN configured because I didn't need to set it on the pfsense

@g-luke said in Configurazione OpenFiber WAN - PPPoE VLAN:

@wifi75 non mancava nulla.
Avevo fatto tutto esattamente come hai suggerito tu, ma non c'era login.
Ho chiamato il provider il quale ha inizialmente detto che poteva essere un problema del mio router, così mi sono procurato un altro router ma neanche con questo c'era login.
Di conseguenza hanno aperto un ticket con OpenFiber, e alla fine è venuto fuori che quando hanno fatto l'allacciamento si sono dimenticati di attivare qualcosa, per cui non c'era possibilità di connettersi.
Io avevo dato per scontato che fosse un problema di configurazione perché dopo che OpenFiber ha fatto l'allacciamento ho chiesto espressamente se la linea dovesse essere attivata dal provider, ma mi hanno assicurato che "potevo già navigare!"

Che provider?

OK, can anyone advice what would be better to get TOPTON i7-1165G7 i211AT 6LAN or QOTOM Q575G6 i7-7500U i211AT 6LAN. I'm on PPPoE FTTP (UK). With current electricity prices I'm trying to find most efficent solution(without breaking the bank [ie. SG-6100 max]).

@enwod said in PPPOE - Fibre issues:

MAC address for my PfSense router their end.

Hi,

What HW are you using?
I need the first 3 segments of MAC,

BTW:

I encountered this problem, which is due to the strict MAC filtering of the service provider (ISPs)

so, use "spoofed", well known manufactures MAC address block, Intel, Cisco, Supermicro, etc....

I dig some more on the problem. It seems to be a dns problem with pfsense-pppoe and Windows.
I will update when i discover some more info

@chpalmer I tried. Unfortunately not.

Next I would do a packet capture on your LAN for anything going on for address 192.168.1.2

Then do some attempted surfing and see if the traffic is actually making it to the LAN port. If it is do the same for the PPPoE/WAN interface.

Diagnostics / Packet Capture

I would reboot the pfSense and when it completed, then reboot/repowered your CenturyLink modem. You'll then obtain an IP address for WAN.

@muppet said in SG-1100 PPPoE Performance:

@akuma1x Yes it's easy enough to buy some secondhand/commodity hardware.

Anything you can find with enough network ports and an Atom C3XXX, or Intel i3/i5/i7 processors, or even some of the more recent fast Celeron and Xeon processors. Those are all good for a pfsense box. Try to stay away from the laptop-grade mobile processors, and the older Celeron J1900 stuff. Those are going to show their age and weaknesses quicker than the other ones.

HP and Dell made/make some good small form factor stuff. Just make sure you can add at least 1 multi-port INTEL network card in there and you'll be all set with a nice pfsense firewall box.

Jeff

@alpineaudio said in pfSense hardware selection help:

@akuma1x said in pfSense hardware selection help:

firewall black-boxes

and more specific, this one's an i5 https://www.amazon.com/QOTOM-Q355G4-Factory-Firewall-Multi-Function-Appliance/dp/B06XNWLR3J/ref=sr_1_fkmr2_2?keywords=pfsense+firewall+black-boxes+i5&qid=1553882807&s=gateway&sr=8-2-fkmr2

This one is a much better choice!

I'm going to get up on my soap box here... keep in mind, you should try to support the pfsense open source project as much as you can. With the Qotom box you found, you're only about $60 away from the "official" Netgate SG-3100 box. I'm not trying to guilt you into a purchase, and I'm not saying you're going to get a better experience with name-brand or not, but being that close in price, I would send my money to Netgate and the firewall project itself.

Jeff

I haven't tried across subnets yet, I'll have a look at that next time it dies. Thanks again for everyones help so far.

te VM sofware locking VLAN packet!