[solved] Broken Pipe Error - now running
-
Today I encountered a not only horribly sounding but also horribly being "pipe error" on 22.05-RELEASE.
I got a new ISP and had to switch WAN from PPPoE to DHCP and while changing the necessary settings, after a reboot pfSense wanted to reconfigure all the interfaces...
Thankfully I had a backup that I rolled back, this time I made not to much changes at once, also I checked for having a WAN gateway in routing and in the end, it did work.Still confused why it didn't went through the first time. Any hint what "broken pipe" means in this context?
-
Where did that appear exactly? Do you have a log?
If it was asking you to re-assign the interfaces it must hve failed the interface check at boot. But that doesn't include sub-interface types like PPPoE so something else must have changed.
Steve
-
@stephenw10 No log left. And I didn't changed the "hardware" at all. That is why I was puzzled. Later I will describe what I did, maybe it is of interest.
-
@stephenw10 Now I am not remembering anymore all the details.
But what I do remember, the second time, I disabled the bufferbloat limiters because I had heard about pipes in that context. I also made sure that the changed WAN had a gateway set. Maybe that was the difference, I don't know. To tired already.
-
@stephenw10 This evening my vm host crashed several times, it looks like a hardware defect, so this topic can be closed.
-
@stephenw10 Is there an easy way for checking the file integrity of my whole pfSense installation after I had encountered bad RAM on my VM Host?
-
Not really unfortunately. None that I'm aware of at least.