Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - elektroinside

#77
I noticed that first RDS_DHCPv6 is first reported down in the GUI.
WAN2 is still up, managed to stabilize the modem.
Then my guess is it crashes when RDS_PPPoE is down as well, cause after that, no GUI, no network, and from what i'm seeing, it doesn't come back until a physical reset.
#78
Screenshots attached.

OK, switched to "member down". Will get back with the results, I'll try a simple PPPoE disconnect.

UPDATE:
Nope, either it panics and never reboots, or simply just hangs. I had to reset the box.
#79
18.1 Legacy Series / Re: cron to check wan ip?
March 30, 2018, 04:04:04 PM
Ok then.
I can tell you how it's done, but you have to do the rest, unfortunately I'm way to busy to try writing one. Can you handle sh scripts?
You need to write a script which collects the ip of your PPPoE interface and add execute permissions to it. If the IP begins with 100.xxx you could bring down the interface, wait for a few secs the bring it back up.
Schedule this with cron, say every 5 minutes. You can do that from the GUI.

How to schedule your custom script (an example) from the GUI:
https://forum.opnsense.org/index.php?topic=7316

But this might not be such a good idea if your ISP assigns, let's say, 15 IPs consecutively, from this private class. You will get disconnected 15 times in a very short period...
#80
18.1 Legacy Series / Re: [Solved] 18.1.5 issues
March 30, 2018, 03:45:17 PM
Well.. I did revert the patch. But it works now! I don't know what's going on.

One thing changed though. I set up multiwan, which I cannot test, because of this:
https://forum.opnsense.org/index.php?topic=7772.0

I guess multiwan influenced this issue as well...
#81
Yep...
If I restart and the WAN is still down (the interface physically disconnected), it never comes back, no network, no GUI. I think it keeps crashing. I don't have a monitor attached to it as it is back in the rack so it's just a guess.
#82
Hi guys,

So.. testing multiwan on my system...
I have a WAN1 which is my PPPoE link and WAN2 which is a Mikrotik with a Huawei 3G modem in it.

I configured a failover group with "packet loss", having as TIER1 the IPv4 gateway of the PPPoE link and as TIER2 the IPv4 gateway of the Mikrotik.

OPNsense crashes every time I disconnect the PPPoE link from Interfaces: Overview.

I submitted the crash report from the WebGUI, don't know if it got uploaded...

Any ideas what's happening?
#83
Better not hijack this thread with unrelated issues, and open a new topic if this is still an ongoing issue. If not, I'm glad you worked it out :)
#84
18.1 Legacy Series / Re: Testing Multi Wan
March 30, 2018, 06:51:09 AM
I'll soon jump in as well the multi-wan testing (on a regular basis).
I stupidly insist doing this with a second Miktrotik + a Huawei E3131 modem, for which I need an external antenna to stabilize the signal a little :)
Hopefully, I'll get one today.
#85
Indeed. We should do this more often :-))
#86
18.1 Legacy Series / Re: pppoe password
March 29, 2018, 10:35:48 PM
You could open a ticket here to get rid of the mandatory password check for PPPoE links:
https://github.com/opnsense/core/issues

It's the first time I ever heard of a passwordless PPPoE link. This setup might not be that popular and so the bug (or missing feature) might not get a high priority. But the devs will know better :-)
#87
General Discussion / Re: No internet PPPoE setup
March 29, 2018, 01:35:41 PM
Thank you for your feedback :)
#88
You're welcome, glad it worked :)
#89
18.1 Legacy Series / Re: [Solved] 18.1.5 issues
March 29, 2018, 08:01:51 AM
Sure, I'll do this once I get home.
After reverting the first patch, do you want me to apply both sequentially or just the latter, the one which you will provide?
#90
General Discussion / Re: No internet PPPoE setup
March 29, 2018, 07:45:40 AM
Question: did you managed to install 18.1 directly without getting a segmentation fault error? Or you worked around the issue by installing 17.5 first, then upgrade to 18.1.5?