Mac Filtering ISP Side
-
How does one tell if the ISP has blocked the WAN's mac address. Our current ISP Charter Communication had issues on Friday with their service and 3 days later we are still down, they are saying its pfsense. I call BS and say their equipment is blocked us since we plug a laptop into the Charter router and get Internet.
Not only am I thousands of miles away from this device but its now experiencing 100% packet loss. I'm a firm believer 99.999999% of the time its always the ISP not the device all of a sudden. I can ping the static assigned IP but not the gateway ip itself. My monitor IP is 8.8.8.8. And if you are wondering why WAN2, over a year ago a similar issue occurred and they said the same thing and configured WAN2 with the same static info and everything connected. So sick of this ISP and their garbage.
This is what the interface i currently displaying (WAN2)
-
@StormGate said in Mac Filtering ISP Side:
Our current ISP Charter Communication had issues ... since we plug a laptop into the Charter router and get Interne
So [ ISP ] <=> [ Charter router ] <=> [ pfSense ] <=> [ LAN with devices ]
Right ?If you think that for some reason [ Charter router ] doesn't 'like' your [ pfSense ] anymore, do the MAgiC trick :
Change your pfSense WAN MAC address.
-
@Gertjan Yes I am going to try that when the staff person gets back form lunch and hotspots back onto a PC. I have tried that in the past and it didn't work but can't remember if we power cycled both the Charter equipment and Pfsense. I have had very similar issues in the past, hence I am on WAN2, some users thought I had a faulty Netgate 6100. You are correct in the network diagram, added one item. All Static info for our WAN, not DHCP.
[ ISP ] <=> Charter Modem <=> [ Charter router ] <=> [ pfSense ] <=> [ LAN with devices ]
-
Be ware that a MAC address, for example the one used on your pfSense WAN or WAN interfaces, doesn't travel very far.
It will get replaced by the next upstream router, your [ Charter router ]. This means that your MAC (pfSense) will not leave your home. Your ISP can't "see" the pfSense WAN (or WAN2) MAC. Same thing for the originating requester device, probably a device on your pfSense LAN. -
@Gertjan Ahh good to know, thanks for the info. Well in the end, it wasn't a Mac issue itself but it was a configuration issue on their end. I knew not to make any changes as it is always the ISP. So the tech came on site, verified everything was perfect and working and then they called me, I asked for verification of the settings, and they couldn't get them, he said he is not getting a gateway IP. I told them this is my issue, I am unable to ping the gateway, after a few calls to higher level technician, they figured out they could see the equipment but no gateway. It was a configuration issue they had to fix then just like that, everything greenlit. All good.
Rule#1 - 99.9999% of the time dropped WAN is ISP
Rule#2 - Don't accept "everything" is working perfect without a confirmation
Rule#3 - Never make any changes on your end -
@StormGate said in Mac Filtering ISP Side:
I knew not to make any changes as it is always the ISP
Put that one first
