2020.2 OpenVPN Client restarting

Issue #10 invalid
Jonathan Michiels created an issue

Hi,

I manually compiled the 2020.2 version today and flashed it on my Linksys EA6900.
When the router reboots and adblock & OpenVPN client are both enabled, adblock can’t download the hosts files.

If I disable the OpenVPN client, adblock downloads the host files correctly.

The OpenVPN client also keeps restarting after the config is completely loaded.
I use a routing policy, and to add the entries, this takes +/- 30 seconds per rule, while on 2019.4 all the rules (11) are loaded in 2-3 seconds.
So on 2020.2 it takes 5-6min to add all the entries, and after adding, the client restarts always.

I flashed back to 2019.4 and now adblock & OpenVPN client works perfectly, but my DDNS does not work (this is fixed in 2020.2).

Comments (6)

  1. pedro repo owner

    You didn’t provide any additional info, logs or something.

    I presume (as stated on Issues' how-to) that it was a clean install…

  2. Jonathan Michiels reporter

    I upgraded my 2019.4 to 2020.2, didn’t clear NVRAM (too many IP assignments and port forwards 🙂 )

    I’ll try to upgrade again next week and post log file.

  3. pedro repo owner

    2020.2-commit-unknown:

    Feb 4 13:44:31 RT-94103E9CE411 user.info adblock[1430]: No internet, will try again in 5 minutes

    Your router does not connect to the network at all, so nothing will work properly here.

    I close, because I will not waste time on it, it is not known how the image was built, on what commit, with what settings, etc.

    On three different routers here (MIPS/ARM), Adblock, OpenVPN, Routing Policy work without a problem

    I still don't know if it was a clean installation, btw (I don't think so).

    Next time, report problems only to existing versions.

  4. Jonathan Michiels reporter

    Weird thing is, I’m at work and I’m connected to my PC at home the whole time over RDP to manage my router, so the internet is OK.
    Image was built on latest commit (built it this morning), following the instructions in the readme file.

    As I previously stated, upgraded from 2019.4 to 2020.2 without clearing NVRAM, no clean install, too many IP bindings and port forwardings…

    But I will wait until the official release of 2020.2 and try again. Sticking to 2019.4 atm (because 2020.1 gives same problem).

  5. Log in to comment