search

MonkWho / pfatt

Enable true bridge mode for AT&T U-Verse and pfSense (this is a fork of an original repository https://github.com/aus/pfatt. Since it is not available anymore, I'll do my best to maintain a copy for people that still need a bypass)
440 stars 171 forks source link

PFsense Restart required after internet loss #20

Closed ReignBock closed 3 years ago

ReignBock commented 3 years ago

Hardware: Netgate SG4860 Desktop w/ USB ethernet adapter Pace 5268AC

Issue: After an internet outage (normally from power loss) PFSense does not regain an internet connection until PFSense is rebooted.

Attached is the relevant section of my pfatt.log Please let me know what other information you need to troubleshoot this issue. pfatt.log

ReignBock commented 3 years ago

adding packet captures of the ONT and RG side. It appears that the gateway is not bridging the EAP packets when the connection goes down. 5268AC script possibly failing to reconnect the bridge after loosing connection? pcaps.zip

ReignBock commented 3 years ago

Tested the ngctl commands used in pfatt-5268AC.sh and confirmed they're valid. Next I'll be conducting the following test to see if the rmhook/connect method used by pfatt-5268AC.sh is causing the issue:

  1. Disable pfatt-5268AC-startup.sh
  2. Restart PFsense
  3. Confirm Internet connection
  4. Power cycle ONT to simulate outage
  5. Confirm internet connection (If I regain an internet connection w/o issue the problem is likely rmhook/connect)
  6. Manually disconnect bridge using command from pfatt-5268AC.sh: /usr/sbin/ngctl rmhook laneapfilter: eapout
  7. Power cycle ONT to simulate outage
  8. Manually reconnect bridge using command from pfatt-5268AC.sh: /usr/sbin/ngctl connect waneapfilter: laneapfilter: eapout eapout
  9. Confirm internet connection (If I don't regain an internet connection rmhook/connect is highly likely causing the issue.

If I can confirm rmhook/connect is causing the issue I'll be downloading the the ng_etf.ko from this package and perform the same tests above using it instead of the version I compiled using the FreeBSD11.3 src.

MonkWho commented 3 years ago

Have you had a chance to run more tests and get this working?

MonkWho commented 3 years ago

No activity in a while. Closing the issue for now.

stansanders commented 3 years ago

i've experienced what i believe to be the same issue. power outage affecting only ONT and presumably some amount of upstream gear will take the connection down even after power is regained until pfsense is rebooted. in today's case I can confirm that all gear downstream of the ONT remained operational during the outage as I was in the control panels during it. let me know if I can do anything else helpful here. my box in this case is a rack server running pfsense on the bare metal with an online UPS powering it and the rest of the network equipment.

AndrewReaganM commented 3 years ago

Just to clarify, the issue was cause by at least the ONT being offline for some amount of time?

stansanders commented 3 years ago

Just to clarify, the issue was cause by at least the ONT being offline for some amount of time?

yes, ONT not on a UPS

AndrewReaganM commented 3 years ago

I haven't actually run into this problem before, but I have a way you can keep it from happening. If you power the ONT with PoE you can avoid it going down until AT&T's network itself goes down. I did this just because I wanted my wife to be able to continue working from home if the power went out for awhile, but didn't want to buy two UPS. You can check out a little write up I did here.