Bug #6611
closed
Kernel panic when running PPPoE Server on tun/tap interface
0%
Description
2.3.1-RELEASE-p5, running in 64 bit kvm vm.
After updating PPPoE settings and confirmation by clicking the green save button on PPPoE page the webinterface stalls. Browser is waiting for response. I waited about 2 minutes and pressed the green save button again. No reponse from webinterface. Contacting webinterface by a second browser instance ended with no response at all. In fact, pfsense was hanging in a boot loop. Check of file system with fsck, returns some fixes made to it, but still looping after reboot. This happened twice. I had the issue yesterday. I exchanged the vm image against a backup and tried it again. Same result.
Updated by Chris Buechler almost 6 years ago
- Status changed from New to Feedback
what's the parent interface of the PPPoE? only way I know of doing something like this is making a PPPoE server interface the parent of a PPPoE client, which is a seriously bad config, but not one we prevent (there's another ticket open to prevent such configs).
Updated by Frank Schmied almost 6 years ago
I've seen the other ticket. The first attempt was on wan interface, which has a fixed ip (no PPPoE client). The second time I set it to an openvpn interface, which has its own ip.
Updated by Chris Buechler almost 6 years ago
- Subject changed from Boot loop / corrupt file system after saving PPPoE server settings to Kernel panic when running PPPoE Server on tun/tap interface
- Category set to PPPoE Server
- Status changed from Feedback to Confirmed
- Affected Version changed from 2.3.1 to All
also makes no sense to run on OpenVPN. That should be prohibited. other ticket is #4510
Updated by Frank Schmied almost 6 years ago
Setting it to ovpn interface was just an attempt to see the result.
Updated by Kris Phillips 29 days ago
Since redmine 4510 no longer allows this, this should be marked as resolved. I have verified that OpenVPN interfaces are no longer selectable. Tested on 22.01 of pfSense Plus.
Updated by