[384.14_Alpha - builds] Testing all variants.

[L&LD]

Dear @RMerlin how long to wait for release 384.14?

Seriously?

It will be ready when it's ready.

 

[Treadler]

Dear @RMerlin how long to wait for release 384.14?

Sigh...........

 

[dave14305]

Aren’t there still models missing GPLs from ASUS?

 

[Gar]

The A2 has been working great for me, the final will be a bonus whenever it's ready.

 

[RMerlin]

Dear @RMerlin how long to wait for release 384.14?

No ETA.

 

[swejuggalo]

I did some quick searches. And didn't find much on it here other than some temporary issues... But now it seems we have a more permanent issue. Let's encrypt seems to need an update to continue to function.

https://community.letsencrypt.org/t/certificate-not-updating-anymore-asus-router/103647

 

[skeal]

I did some quick searches. And didn't find much on it here other than some temporary issues... But now it seems we have a more permanent issue. Let's encrypt seems to need an update to continue to function.

https://community.letsencrypt.org/t/certificate-not-updating-anymore-asus-router/103647

Problem on Asus' end. It's being researched.

 

[Butterfly Bones]

I did some quick searches. And didn't find much on it here other than some temporary issues... But now it seems we have a more permanent issue. Let's encrypt seems to need an update to continue to function.

https://community.letsencrypt.org/t/certificate-not-updating-anymore-asus-router/103647

https://twitter.com/RMerlinDev/status/1187404491806662657

 

[swejuggalo]

https://twitter.com/RMerlinDev/status/1187404491806662657

Aww. Hoped it was possible to do something about it without waiting on Asus

 

[skeal]

Aww. Hoped it was possible to do something about it without waiting on Asus

You can. Change your DDNS provider to say No-IP for instance. Asus DDNS works but not with LE.

 

[swejuggalo]

You can. Change your DDNS provider to say No-IP for instance. Asus DDNS works but not with LE.

Hmm... Tried No-IP and it works ofcourse (just like the Asus DDNS did) but I get "bad comm" in sys logs in the acme-client and the server certificate status in DDNS is permanently "updating"... Just because the ddns is changed does not change the fact that LE needs a newer client (and my problem was only LE). Am I missing a point or something?

 

[skeal]

Hmm... Tried No-IP and it works ofcourse (just like the Asus DDNS did) but I get "bad comm" in sys logs in the acme-client and the server certificate status in DDNS is permanently "updating"... Just because the ddns is changed does not change the fact that LE needs a newer client (and my problem was only LE). Am I missing a point or something?

No, you're right it's a LE problem. I use a pixelserv-tls generated certificate. I had the same issue as you.

 

[Vexira]

do i need to worry about this?
kernel: jffs2: warning: (27859) jffs2_sum_write_data: Not enough space for summary, padsize = -8

 

[Adamm]

do i need to worry about this?
kernel: jffs2: warning: (27859) jffs2_sum_write_data: Not enough space for summary, padsize = -8

https://lmgtfy.com/?q=jffs2:+warning:+(27859)+jffs2_sum_write_data:+Not+enough+space+for+summary&s=g

 

[Vexira]

https://lmgtfy.com/?q=jffs2:+warning:+(27859)+jffs2_sum_write_data:+Not+enough+space+for+summary&s=g

Did that already or I wouldn't be asking, I'm not even using traffic analyser, which was what cause it for someone.

 

[Adamm]

Did that already or I wouldn't be asking, I'm not even using traffic analyser, which was what cause it for someone.

As per the first (and multiple other results);

This has been reported multiple times, search the forum. For example:

https://www.snbforums.com/threads/c...er-these-event-log-entries.47031/#post-409970
https://www.snbforums.com/threads/k...rite_data-not-enough-space-for-summary.47231/

Following those links you find your anwser;

This one is just a transient warning...

JFFS2 has an erased block summary, and sometimes it's too big to write, so you get the error - it's slows down mounting a bit, once the garbage collector runs through and cleans things up, should be fine...

Along with;

I don't know/understand the inner workings of flash memory. I'm only going by what those two links said and the fact that the message is a "warning" not an error. I looked at the source code for that message and doesn't seem to be an issue AFAICT. It even says it's "non-fatal".

    /* Is there enough space for summary? */
    if (padsize < 0) {
        /* don't try to write out summary for this jeb */
        jffs2_sum_disable_collecting(c->summary);

        JFFS2_WARNING("Not enough space for summary, padsize = %d\n",
                  padsize);
        /* Non-fatal */
        return 0;
    }

 

[Vexira]

As per the first (and multiple other results);



Following those links you find your anwser;



Along with;

So a simple no is extremely difficult, Ive already read about the flash memory, I also read about Merlin saying that in one case it was triggered by the traffic analyser.

 

[RMerlin]

I also read about Merlin saying that in one case it was triggered by the traffic analyser.

Anything that writes to jffs2 can potentially trigger the message. Traffic Analyzer is one thing, but there are quite a few others, including system logging.

 

[MoonPie2000]

Any inside scoop from ASUS if AC3200 will get a component update?

 

[Vexira]

Anything that writes to jffs2 can potentially trigger the message. Traffic Analyzer is one thing, but there are quite a few others, including system logging.

I was just concerned, due to when a factory reset the router the jffs directory was locked, couldn't write to it, so I had to downgrade and re format then upgrade back to the alpha to get SSH working again and the jffs partion to have the scrips folder that was missing, I almost thought it was a carry over issue.