Bug #8736
closed
default gateway not working after upgrade to 2.4.3-RELEASE-p1
0%
Description
Hello,
the upgrade told me, it will eat 37MBs more, it has eaten over 150. But thats not the issue, I understand, that the package manager is not the only thing that writes to disk during upgrade.
Problem is, that my system no longer uses the checked default gateway the way 2.3 version did. Maybe it has something to do with troubles with virtual interfaces (it is openVPN) that I have seen in the recent bugs. But this one is different by when it happened and the tunneling protocol.
Updated by Jim Pingle over 7 years ago
- Status changed from New to Rejected
This is not a platform for support or diagnostic discussion. There is not enough information there for a valid bug report.
Please post on the forum or pfSense subreddit to discuss your problem.
Updated by david ricar over 7 years ago
Wow, it feels to you like support request? Well the border between that and bug report is nonexistant, so I undertstand this is a free product and nobody cares about bugs. Too bad, it was cool working for a few years, now I will have to use something else.
Just to sum up my report to make it very clear it was a bug report:
1) upgrade said it will eat 37MBs, it has eaten 150MB - whole thing have grown to double size during the time, so free space is scarce and bad info (not even advertised BEFORE the upgrade) may lead to trouble.
2) default gateway set to openvpn is no longer working after upgrade. This was reported with pppoe interfaces too, so I suppose it has a common root.
Good bye