Messages

rhyse, well I suspected some configuration error as well.

I was doing a clean install already but restored my configuration from backup.

Looks like I need to set things up from scratch to check if the problem persists.
Would have been great if there was another solution, though.

Don't want to give up the switch from pfSense yet.

Hi franco,

oh that was my bad, really.
First mistake was I thought I need to address the paramenter with the interface description name (in my case WAN2) and the second mistake was not using lowercase!

Thanks for your help, works as expected now!

Cheers,
Markus

Isn't the default lan up 192.168.1.1 ? Not 192.168.10.1

Yes, but not in my environment.

Cheers,
Markus

For what it is worth, after a couple of minutes the "request timed out" changed to:

Code Select Expand


C:\Windows\system32>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:
Reply from 62.155.240.203: Destination host unreachable.
Reply from 62.155.240.203: Destination host unreachable.
Reply from 62.155.240.203: Destination host unreachable.


62.155.240.203 is my WAN2 gateway, this looks like some sort of bug.

Cheers,
Markus

Hey guys,

I am running opnsense 17.1.7 and have a multi WAN setup employing WAN (DHCP) and WAN2 (PPPOE).

A cronjob was created as follows:

Code Select Expand


Enabled, Minutes, Hours, Days, Months, Weekdays, Description, Command
<x>      30       7      *     *       *         Redial VDSL  Periodic interface reset


As parameter I added "WAN2", so everything should work as expected.

For whatever reason when I browse the log file I see:

Code Select Expand

configd.py: [8a8b6c9e-2fca-44e1-a37a-e2e67d331e5a] Configuring interface WAN2

which indicates the cronjob is being executed but the interface doesn't reconnect. No change of IP address visible in the log.

I already tried using pppoe1 and OPT2 as parameter but that doesn't change anything.

Ideas?

Cheers,
Markus

I do have the same issue.

Interestingly enough I can ping the firewall while it is rebooting for a couple of times, then I receive "Request timed out."

Cheers,
Markus

Thanks franco, seems to work :-)

Hey Guys,

shouldn't there be an option for the periodic reset of dialup connections? I am unable to find a way to make my pppoe connection reset at a given time.

I searched the forums, but all I came up with was this ancient thread from 2015
https://forum.opnsense.org/index.php?topic=657.msg2364#msg2364

Anything I am missing here?

Cheers,
Markus

Hi Fabian,

sorry for my laggy response. I didn't realize that I need to enable e-mail notification per thread in the forum.

Maybe the problem is related to OPNSense locking up completely (i.e. https://forum.opnsense.org/index.php?topic=4414.0)?

It did that once, pretty fast after the reboot that took place after the update to 17.1.1. I was in the middle of configuring the IDS when I wondered why the box became unresponsive.

In any case, having to reboot OPNSense multiple times per day to get back out to WAN isn't an acceptable workaround. If all else fails I'll try 16.x and see if that works.

Funny thing was, 17.1 did not issue any problems...

Does your hardware setup have something in common with mine? Just to make sure this doesn't come from some FreeBSD 11.0 driver issue.

Not that much. It runs on a Lex Barebone with em0 (LAN) and igb0-igb4 (WAN1, WAN2, GUEST) network devices. So I'd rule out a driver problem since we use different vendors.

Will perform a clean 17.1.1 install this weekend to ensure the update process didn't mess things up.

Cheers,
Markus

Hi Fabian,

I just updated to 17.1.1 and I am also stuck with the problem, that I can not ping the LAN address from my LAN clients. Everything else seems to be working alright, though.

Did you find any solution to this, yet?

Cheers,
Markus