There are a few ways you can do this. That should work. What I would do is create the PPPoE session on the VLAN in Interfaces > Assignments > PPPs. Then assign the WAN as that new PPPoE 'port'. But either should work. Steve

@stephenw10 Thank you thank you thank you for responding

@ghost-0 Tell that to the thousands of people that bought the switch that said it would do vlans. Which it can't. Pretty much amounted to just running multiple layer 3 on the same layer 2. Any freaking dumb switch could do that.. With zero compensation and no fix.. If you were v1 or v2 you just got hung out to dry.. Oh well I guess - buy version X, we fixed it... I don't go out of my way to bad mouth them.. But there are plenty of other brands to choose from - if people ask me what I would suggest. They are just not one of them.. btw - notice I stated "But current model would prob work as well." I just didn't link to one.. They have a bad track record... Lookup vlan 1 tplink yourself if you don't believe me..

@jerothle Aug 31 19:36:31 dpinger 28952 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr ##.##.##.1 bind_addr ##.##.##.49 identifier "WAN_DHCP " Aug 31 19:36:32 dpinger 35290 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr ##.##.##.1 bind_addr ##.##.##.49 identifier "WAN_DHCP "

I previously setup 3 ring devices with pfSense without any issues. Now, I have two behind it since I moved. You need to rule out that a firewall rule on PF isn't blocking it. I never setup any special ports for Ring devices, but I'm also not restricting outbound traffic - are you?

Yeah, I would also block it without logging. It shouldn't be there IMO but the volume is not high enough to be anything but a nuisance.

Do you see states/traffic on the port forward WAN firewall rules when you try to connect? Or you can enable logging on those rules connections using them will show in the firewall log as passed. Steve

Thanks. I've removed the NTP NAT entry, but alas it still doesn't sync. O. M. G. I feel like such a !@%$#@ idiot. I was collecting screen shots of NAT and firewall status for the thread, and when I went to LAN rules there was a block for NTP on *. It was part of a bunch of rules I had setup to block Alexa at one point when I had Googled what ports it uses, as my friend kept annoying me asking the Echo to play stupid crap. I totally forgot I had done that. Removed the rule and wouldn't you know it, time sync'd :) God I feel stupid lol. Thanks!

Mmm, this seems more likely to be a problem in that client that the firewall. However, try setting a different static on that client. Does the behaviour change? Try booting a live Linux distro on that client. Since you have policy routing for some clients you might be hitting that from this client. So check it's IP is not in some alias somewhere. Since it affects only TCP traffic check there is not a policy routing firewall rule that is still set to the default TCP only and should be using protocol 'any'. Steve

@johnpoz If I understand you correctly. I do have other devices connected to my US-24, some computers, Smart TV's but most of them are using my LAN network (my main network) and one Smart TV using profile - VL30_KIDS, the rest of the ports on my US-24 using profile "ALL" :) Btw, my pfSense and UniFi "setup"(almost) is from this video made by Lawrence Systems https://www.youtube.com/watch?v=b2w1Ywt081o

@stephenw10 said in *SOLVED* pfSense freezing for a second or two every 15 minutes: The other table that can be massive is bogons v6. Not too horrible at 124297 entries. Some tables as pfctl seems them -pa-r-- bogonsv6 Addresses: 124297 Cleared: Fri Aug 20 01:07:38 2021 References: [ Anchors: 0 Rules: 1 ] Evaluations: [ NoMatch: 537822 Match: 0 ] In/Block: [ Packets: 0 Bytes: 0 ] In/Pass: [ Packets: 0 Bytes: 0 ] In/XPass: [ Packets: 0 Bytes: 0 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass: [ Packets: 0 Bytes: 0 ] Out/XPass: [ Packets: 0 Bytes: 0 ] -pa---- pfB_NAmerica_v6 Addresses: 505938 Cleared: Fri Aug 20 01:07:38 2021 References: [ Anchors: 0 Rules: 0 ] Evaluations: [ NoMatch: 2 Match: 12 ] In/Block: [ Packets: 0 Bytes: 0 ] In/Pass: [ Packets: 0 Bytes: 0 ] In/XPass: [ Packets: 0 Bytes: 0 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass: [ Packets: 0 Bytes: 0 ] Out/XPass: [ Packets: 0 Bytes: 0 ] -pa-r-- pfB_Top_v6 Addresses: 16341 Cleared: Fri Aug 20 01:07:38 2021 References: [ Anchors: 0 Rules: 3 ] Evaluations: [ NoMatch: 51426 Match: 150 ] In/Block: [ Packets: 150 Bytes: 10800 ] In/Pass: [ Packets: 0 Bytes: 0 ] In/XPass: [ Packets: 0 Bytes: 0 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass: [ Packets: 0 Bytes: 0 ] Out/XPass: [ Packets: 0 Bytes: 0 ]

All the package data is stored in the main config file in /conf/config.xml. If you're doing something that is impractical to manage via the gui you should probably be using a separate Radius server. Steve

@stephenw10 thanks

@bangui91 first go into the bios and disable hyperthreading. secondly, list your network adapters. are they all intel or do you have realtek? Everyone hates realtek because for the longest time, BSD was shipped with broken drivers.. pfsense version 2.5 finally included working drivers for realteks, however unlike intels that just 'install and work out of the box', you have to direct pfsense to use the new realtek drivers. i've seen the commands, it's very simple. just have to search for the instructions on what to do.. again, it's very simple and as a noob myself, i wouldn't be concerned. third, you should list the packages you have installed for the seasoned vets to go through.. someone here will know

PPPoE cannot be DHCP. I assume you just mean it's dynamic? You are suggesting using those subnets? I would avoid 192.168.1.X as it's very common. It's the default LAN subnet.

Anything that is just a modem will not be addressable outside it's own segment. It might have a management interface but it will be using a non-routable private IP address. What sort of DSL service are you connecting to? Steve

@carl123 said in Problem with packages: What confused me was that when I loaded my copy of pfsense, it returned the problem Most probably : When you install pfSense, updates/upgrades work, as default DNS settings work. When you import your own settings, with your config.xml, "breaks" DNS. pfSense itself can't resolve any more, and thus can't contact the Netgate update-upgrade server : the Package lists stays empty - and you're not notified any more when updates are avaible. Solution : 'repair' your DNS.

The matching thread on reddit for this says he already started the rma process.

@bingo600 said in MINIX NGC-3: His Minix book is worth a read I haven't read that book, but I do have his (with David J. Wetherall) Computer Networks book.

The client export by default will use the WAN IP as the server IP in the conf file. But in Azure the WAN is a NAT'd private IP so clients will fail to connect. You need to set the Host Name Resolution field to other and enter the public IP there. Or use an FQDN is you have a public host name for that. Steve