Gateway - Send to Error 65
-
Additional update: I give up with pfsense as the gateway. I've done a compromise of sorts, I have my pfsense box just with the LAN interface active, and it's doing my DHCP and DNS. The T3200M is just doing routing. I lose some stuff, like bandwidthd and the ability to see what's using my bandwidth, but I don't have a double NAT and I'm not just randomly losing the ability to contact the gateway every 3-6 hours like clockwork. I haven't tried a non-pfsense host on bridge mode but I think I just give up at this point. At least my LAN hostname resolution isn't terrible with the pfsense box doing that. I might split that off to another linux host like my NAS or something, but this works and I'm just so tired of this.
I don't know where the fault lies. None of it ever made a lot of sense with how it was manifesting and I never did get around to packet captures. Thanks again for the help. This will work well enough I guess.
-
@shortspecialbus Sorry to necro an old thread, but I have the same ISP and am having the exact same issue! It seems to be related to the DHCP lease time. Right around the time when there is 10% lease time remaining, I have the same issue. A release/renew or modem reboot fixes the issue, however.
Did you ever come up with a solution? You're the only person I've found having the exact same issue! Created an account just to reply :-)
-
@toaday Unfortunately, no. In my case, DHCP release/renew wouldn't work either - only a reboot would. I have no idea why. I gave up on this and just accepted that I had to use TDS's lousy router (not in bridge mode), and I just have pfsense running as a DHCP server effectively at this point. For what it's worth, I purchased a couple different modems that theoretically met TDS's specifications, but even working with the modem developers and having them try to write custom firmwares, we were never able to get better than half-speed or so. (edit: scrolling up I seem to have already chronicled this, it's been a while and I forgot) I have no idea what TDS does, but it seems to be completely proprietary.
What I have now is working well enough and I don't really want to go through the frustration again, so I just accept it. I will say "good luck!" and I suppose if you ever figure out an actual fix, I'd for sure be interested if you posted it here. Seriously though, good luck!
-
@toaday Did you ever have any luck with this? I'm trying something new now (not with pfsense) and while I had the same old issues with bridge mode failing as soon as the lease gets near expiration, I may have gotten Advanced DMZ mode to work, although I'd like to give it a full day or two of testing to be sure.
Sorry to necro this old thread again, but as toaday and I are the only people on the planet who've ever run into this issue and I have no other way to get a hold of them, I'm using the thread ;)
-
@shortspecialbus no worries! Feel free to google my username and we can collaborate on this. The solution for me was to switch to a static ip.
-
@shortspecialbus and @toaday, I am from Kenya and have the same exact issue although I have two fibre links from two different ISP's, WAN 1 link always gets the error then my pfsense box stops working. I have had the problem for about 3 months now, tried changing the whole fibre but still having the same issue with the WAN 1 link. Mine goes for around 24hrs, then ceases to work. Although I noticed that when my pfsense stops working the ISP router still has internet, today I am going to try and change the LAN IP of my ISP modem to see if it will change anything. Will keep you updated
-
This post is deleted! -
Check out this thread:
I have a Carrier Grade NAT provider and I would lose connection at least once every couple of days. The only way to fix it was to reboot pfSense OR unplug the WAN cable, wait a few seconds, and the plug it back in. Alternatively I could go into pfSense, disable the WAN, Apply Settings, and then Enable the WAN and Apply Settings.
The thread I linked above is a script that does all this automatically. It pings out and when too many pings are lost it disables then enables the WAN which usually fixes it. It if doesn't work after a few attempts it will automatically reboot your pfSense box.
It even creates a log file so you can go back and see when it happens.
-
@thatguy Hello there, thanks for your help, although I do not understand where the code to be copy-pasted is, could you guide me please since I am still a noob at programming.
-
This post is deleted!