Modify

Opened 8 years ago

Closed 7 years ago

Last modified 6 years ago

#669 closed bug (fixed)

Frequent error message: Your Internet is misconfigured

Reported by: Hypetribe <globalmediaco@…> Owned by: matthijs
Priority: normal Milestone: Firmware 2.3.6.1
Component: fon-network Version: 2.3.6.0 (Gari)
Severity: normal
Cc: carsten.schuette@…, decodecoding@…, admiral0@…, josemi@…, giuseppeg88@…, thejew@…, kaspervillum@… Hardware: 2.0n (FON2300)

Description (last modified by matthijs)

I am using developer version of 2.3.6 and get this error message randomly almost on a daily basis. Have a dsl modem that is plugged into fon2n and I am connected to myplace using wpa - tkip.

If you're looking to test the fix for this bug, scroll down to comment 39 by matthijs for instructions.

Attachments (3)

thinclient (1.6 KB) - added by matthijs 7 years ago.
Fixed thinclient
log1.txt (53.5 KB) - added by giuseppeg88@… 7 years ago.
log: Jul 11 14:00:47
log2.txt (53.2 KB) - added by giuseppeg88@… 7 years ago.
log: Jul 11 14:00:49

Download all attachments as: .zip

Change History (67)

comment:1 Changed 7 years ago by matthijs

  • Milestone Requests deleted

Milestone Requests deleted

comment:2 Changed 7 years ago by matthijs

  • Hardware set to unknown

#658 is a duplicate of this ticket.

comment:3 Changed 7 years ago by matthijs

  • Component changed from unknown to fon-network
  • Hardware changed from unknown to 2.0n (FON2300)
  • Status changed from new to infoneeded
  • Summary changed from In reference to Your Internet is misconfigured : Configure Internet Connection to Frequent error message: Your Internet is misconfigured
  • Type changed from request to bug
  • Version set to 2.3.6.0 (Gari)

It seems this issue occurs with more people. We need some more information to find out what causes it.

When you get this message, does it get fixed by waiting a bit, or do you need to restart the Fonera?

If you get this message, is your FON_FREE_INTERNET (or however you've called it) wireless network still available?

If you get this message, could you try connecting to your Fonera with SSH and try the following commands (terminate them with control-C after a few seconds):

root@Fonera:~# ping www.google.com
root@Fonera:~# ping 130.89.1.1

Please paste the output of these commands here (using preformatted text syntax to make things readable).

Lastly, if this problem occurs again, feel free to contact me through IRC (Internet Relay Chat) so we can do some interactive debugging. I'm called 'blathijs' on Freenode (you can use the web chat application at http://webchat.freenode.net/ if you don't have your own IRC program).

comment:4 Changed 7 years ago by Radu Andries <admiral0@…>

Connectivity on fonera present.

I tried using OpenDNS instead of fonera as nameserver. Problem still there.

Connectivity checks under stress are broken imo.

Usually this happens when i download torrents (on local machine, not fonera)

comment:5 Changed 7 years ago by matthijs

  • Status changed from infoneeded to confirmed

It seems this bug is caused by the change of MAC addresses in 2.3.6.0, which wasn't properly changed in the "thinclient" application. I don't know any details about this currently, but FON is working on a fix for this.

comment:6 Changed 7 years ago by matthijs

  • Cc carsten.schuette@… added

#679 is a duplicate of this bug.

comment:7 Changed 7 years ago by matthijs

  • Cc decodecoding@… added

#796 adds to this that the Fonera doesn't show up on the fon.com "user space" as well.

comment:8 Changed 7 years ago by Radu Andries <admiral0@…>

Is there a workaround to apply while waiting for next release?

comment:9 Changed 7 years ago by matthijs

decodecoding, when you say doesn't show up in the user space, do you mean at https://www.fon.com/en/userzone/myRouters ? Doesn't it show up at all, or does it get listed as offline, or? I'm asking since I'm seeing my 2.0n there normally.

Changed 7 years ago by matthijs

Fixed thinclient

comment:10 Changed 7 years ago by matthijs

  • Cc admiral0@… added
  • Owner changed from iurgi@… to matthijs
  • Status changed from confirmed to accepted

Radu (and others), I've attached a fixed version of thinclient. Could you install it on your Fonera to see if it fixes the internet connection issues?

To install you'll need to have development firmware installed. Download the attachment and overwrite the /bin/thinclient file on your Fonera with it. The easiest way to do this is to connect using SSH / PuTTY and use the wget command:

root@Fonera:~# wget -O /bin/thinclient http://trac.fonosfera.org/fon-ng/raw-attachment/ticket/669/thinclient

If the new thinclient is properly installed, you should be be able to update your settings (SSID's and passwords) again through fon.com. Please report if the connection issue still occurs after installing the fixed thinclient.

I haven't been able to reproduce the connection issue on my 2.0n, so it's not certain that this thinclient fix will actually fix the connection issue as well. Please test it and report.

comment:11 Changed 7 years ago by Radu Andries <admiral0@…>

Installed and started transmission on my laptop.. let's see if it works under stress :>

comment:12 Changed 7 years ago by Radu Andries <admiral0@…>

Nope, doesn't help. Connection issues still there.

Steps to reproduce: Start transmission with multiple torrents. Open a webpage Your internet connection bla-bla-bla

Info: In the meantime transmission still downloads (how is it possible? Even Ip pings fail). Laptop: Archlinux 2.6.34-ice, ath9k wireless driver, atheros 802.11n chip. Fonera: Latest Firmware.

To return normal: Stop transmission. reload firefox (that's to empty its cache)

comment:13 Changed 7 years ago by matthijs

  • Severity set to unknown

Ok, so the thinclient problem seems unrelated to this problem. #620 discusses the thinclient problem in detail.

comment:14 Changed 7 years ago by matthijs

  • Cc josemi@… added

comment:15 Changed 7 years ago by matthijs

  • Cc giuseppeg88@… added

comment:16 Changed 7 years ago by matthijs

Just got an email from Radu, that his problem was caused by actual connection problems in his setup. So this probably means that extensive load / multiple torrents are not causing this problem.

comment:17 Changed 7 years ago by matthijs

If anyone of you has this issue again, could you try running the following command (preferably while the connection is still broken).

root@Fonera:~# (logread; iptables -L -n -v ; iptables -L -n -v -t nat; dmesg; echo -n State: ;cat /tmp/run/fonstate; echo; ping -c 3 updates.fon.com; ping -c 3
 www.google.com; wget http://updates.fon.com/firmware/conncheck/conncheck.txt -O /dev/null) > /tmp/log.txt 2>&1

This is really a bunch of commands that collect information and write that to the file /tmp/log.txt. Please attach that file to this ticket so I can review it. See this page? for info on how to run commands and get files from your Fonera.

Please also make note of the time you first see that the connection is broken and the time when you see it working again.

comment:18 Changed 7 years ago by matthijs

Uh, I meant this page for info, I mistyped it...

comment:19 Changed 7 years ago by matthijs

  • Milestone set to Firmware 2.3.6.1

comment:20 Changed 7 years ago by matthijs

I just noticed something that influences the perception on this bug: While the internet connection is detected as Offline, the Fonera dns server will returned a fixed (fon.com) address for all DNS queries. This makes sense, since there is no upstream DNS available and it has to return _something. Returning nothing, or an error, would cause the browser to show its own error and would not allow the user to be redirected to the "Your internet is misconfigured" page through iptables.

However, since operating systems and/or browser usually cache DNS results for a bit, this can cause specific sites to remain broken for a bit longer when the connection is restored. Since the iptables redirect rule is removed now, you will no longer see the "Your internet is misconfigured" message, but instead get a fon.com page (probably a 404).

This is something we can't really fix (and it doesn't really matter that much, caches are only a few minutes), but this should be realised when debugging this problem.

comment:21 Changed 7 years ago by matthijs

  • Description modified (diff)

I've investigated a bit, it seems dnsmasq does set the DNS TTL (time-to-live) to 1 second when the Fonera is offline, and the DNS results do indeed have a TTL of 1, so it must be my Linux or Firefox that's ignoring the TTL and is caching for longer.

I've also added a note to the description with instructions for people coming here from the blog and other places.

comment:22 Changed 7 years ago by matthijs

Are you guys still seeing this problem? If so, could you try getting the output of this monster command for me while the connection is having problems?

root@Fonera:~# (logread; iptables -L -n -v ; iptables -L -n -v -t nat; dmesg; echo -n State: ;cat /tmp/run/fonstate; echo; ping -c 3 updates.fon.com; ping -c 3
 www.google.com; wget http://updates.fon.com/firmware/conncheck/conncheck.txt -O /dev/null) > /tmp/log.txt 2>&1

I really want to fix this problem, but we're really in need of your help.

comment:23 Changed 7 years ago by Josemi

Yes, I continue having the issue.Today I get the connection problem, but I was not able to run the commands beacause I was doing another thing :-(

Changed 7 years ago by giuseppeg88@…

log: Jul 11 14:00:47

Changed 7 years ago by giuseppeg88@…

log: Jul 11 14:00:49

comment:24 Changed 7 years ago by sal@…

I'm able to re-create this fairly easily. The formula is simple - just hammer the network connection. If I do a bunch of bit-torrents concurrently this is pretty much guaranteed to bring on the yellow-screen of death.

comment:25 Changed 7 years ago by thejew@…

I can reproduce the Bug almost anytime I want, since it happens ALL THE TIME!! I just shot a video when it happened. I need a fix, since this bug appears daily and makes it almost impossible to use the internet. If there is no fix soon, I have to buy a new router, which would be very unpleasant. Especially because the router did cost around 70 Euros.

When you get this message, does it get fixed by waiting a bit, or do you need to restart the Fonera?

get fixed by waiting...

If you get this message, is your FON_FREE_INTERNET (or however you've called it) wireless network still available?

Nope.

And emptying the cache of any browser doesn't do anything (Opera, Safari, Firefox,...) I am not an router expert, this side didn't help me at all. I think that a router should just work. If matthijs wants a better description, or has any questions, please feel free to ask me via mail. I can even send you the video.

comment:26 Changed 7 years ago by kaspervillum@…

I get the "Your Internet is misconfigured : Configure Internet Connection" 10-20 times a day which makes the Fonera almost useless.

Firmware Version: 2.3.6.0

Please help. Contact me if you need more information.

comment:27 follow-up: Changed 7 years ago by matthijs

  • Cc thejew@… kaspervillum@… added

Let me remind you that comment 17 contains a command to collect info. Giuseppeg has provided some output already, but it would help to get it from a few others to compare. Be sure to run the command shortly (up to tens of seconds) after the internet breaks, otherwise the most useful information will have been forgotten again.

Also note that the command is a single line, even though trac has wrapped it to two lines.

comment:28 in reply to: ↑ 27 Changed 7 years ago by anonymous

Hi Matthijs, thanks for your reply.

I am aware of comment 17, but I dont understand what to do.

Where do I run the command? How do I send the log file to you?

Thanks

BTW: I am not running the developer edition.

Replying to matthijs:

Let me remind you that comment 17 contains a command to collect info. Giuseppeg has provided some output already, but it would help to get it from a few others to compare. Be sure to run the command shortly (up to tens of seconds) after the internet breaks, otherwise the most useful information will have been forgotten again.

Also note that the command is a single line, even though trac has wrapped it to two lines.

comment:29 follow-up: Changed 7 years ago by matthijs

Have you read http://trac.fonosfera.org/fon-ng/wiki/reportbugs ?

You will need to change to the developer version to be able to collect information.

comment:30 Changed 7 years ago by koter84@…

why not only give this message the first time... so that when you haven't gone through the wizard you get this..

my internet connection isn't always on.. but i do have another network on the other side of the WAN port... but as soon as i've got no internet i can only visit the ugly orange page saying my internet is "misconfigured"

i am running a DEV-firmware... myabe i am dev-enough to use my own logic to realize my internet is offline! (and NOT misconfigured) just make sure the misconfigured-link goes to the internet page, and give an extra option there to disable this bug you call a "feature" i found some info on your old forum how to disable this, and it was: (not exactly sure, from the top of my head)

=> mv /etc/fonstatd/Redirect /etc/fonstatd/Redirect.old => edit /etc/fonstatd/RestartDns ?

put comments (#) on 2 lines (one line has "Offline" in it, and the one above that)

this is a really simple fix for such a problem!

comment:31 in reply to: ↑ 29 Changed 7 years ago by kaspervillum@…

@matthijs

I am no developer or programmer - I kinda just want my router to work.

I just upgraded to the developer version, but I have no idea how to use the SSH access.

I am one a Mac. There is no Mac-instructions on: http://trac.fonosfera.org/fon-ng/wiki/reportbugs

comment:32 Changed 7 years ago by koter84@…

@kaspervillum

on Mac it's even easy-r than on windows, since Mac already has a built-in command-line..

The shell is accessed through the Terminal program, which you will find under Applications->Utilities.

then just type:

ssh root@192.168.10.1

you will get a password: dialog, fill in your password, and you are in the router :) then you can copy paste the above commands

comment:33 Changed 7 years ago by matthijs

Hmm, good point, forgot about MacOS :-)

koter84 has given about the same instructions I've just added to the reportbugs page. The reportbugs page also has instructions on using scp to get the log file off the Fonera.

comment:34 Changed 7 years ago by thejew@…

I now have installed the developer firmware. But the commands are not working. gives me:

root@Fonera:~# => mv /etc/fonstatd/Redirect /etc/fonstatd/Redirect.old => edit /etc/fo nstatd/RestartDns

-ash: =: not found

I would love to fix the problem, if anyone has working commands, please help. Thanks everyone anyway ;-)

comment:35 Changed 7 years ago by matthijs

The instructions posted by koter84 aren't literal commands, but instructions on what to do. You'll have to understand what they first. Perhaps koter84 can explain a bit more closely, I'd rather spend time fixing the bug than working around it.

comment:36 Changed 7 years ago by koter84@…

Sorry for the late reply, i started this just 90 minutes after your message, but got busy with work-related stuff... so finishing the reply now... (this time with literal commands)

I found it on the deprecated fon boards.. i google-d for it again and found it quite fast... http://boards.fon.com/viewtopic.php?p=47646&sid=85f126f41db3eae7f204f21f5d61fe9a#p47646

On that page they explain what they are doing... but here is a short way to do it:

root@Fonera:~# mv /etc/fonstated/Redirect /etc/fonstated/Redirect.off
root@Fonera:~# vi /etc/fonstated/RestartDnsmasq

now you are editing the correct file (using the program 'vi') use the down arrow on your keyboard until you get to a part with this:

S=`cat /tmp/run/fonstate`
[ "$S" == "Offline" ] && X="--address=/#/213.134.45.154 -T 1"

and change that to (look carefully, it's the first character on the line)

#S=`cat /tmp/run/fonstate`
#[ "$S" == "Offline" ] && X="--address=/#/213.134.45.154 -T 1"

you can change this by getting the cursor to the right line, and make sure it is at the beginning of the line. now press the 'i'-key on your keyboard. (this is for "insert-mode") now type the "#" and use the arrow-keys to go down one rule and to the beginning again, type another "#" and then press the [ESC]-key (esc is for leaving the "insert-mode") then type ":wq" the ":" is for giving a command, "w" is the command to write the file to disk, "q" is the quit-command..

in short:

root@Fonera:~# mv /etc/fonstated/Redirect /etc/fonstated/Redirect.off
root@Fonera:~# vi /etc/fonstated/RestartDnsmasq
- use arrows to find the following:
S=`cat /tmp/run/fonstate`
[ "$S" == "Offline" ] && X="--address=/#/213.134.45.154 -T 1"
- change this to:
#S=`cat /tmp/run/fonstate`
#[ "$S" == "Offline" ] && X="--address=/#/213.134.45.154 -T 1"
- save the file and exit the router

these changes should take effect immediately... only problem i've noticed is that the FON_FREE_INTERNET doesn't work since this also uses the same system to check if the fonera is still online... so it really is only a small workaround, but for me... this suffices, at least until the problem is fixed.. :)

comment:37 follow-up: Changed 7 years ago by matthijs

Some more investigation shows that there's also a second problem: In some cases, the FON_FREE_INTERNET signal disappears due to some problem with the Fon heartbeat server. However, in this case, the orange page does not appear.

I would like to keep this report about the issue with the orange page If you have the issue of disappearing public signal, please don't comment on this ticket.

The logs posted by giuseppeg also seem to be from the other issue. This means I'll still need a log from someone who is actually seeing the orange page issue.

To help debugging, I've created a modified version of onlined that is a lot more verbose about any connection errors it sees. To install it, run the following command:

root@Fonera:~# wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-verbose

Afterwards, run the following command to keep a full log (instead of only the last 200 or so entries with normal logread).

root@Fonera:~# logread -f >> /tmp/logread.txt

This command will keep running indefinately. Please leave it running until the orange page has appeared and disappeared at least once (please also note the time when this happens). Afterwards, you can terminate the command by pressing CTRL-C. It will have put its output in the file /tmp/logread.txt.

See http://trac.fonosfera.org/wiki/reportbugs for info on how to run these commands, getting the output and putting the output in a trac comment.

comment:38 Changed 7 years ago by matthijs

I should really be previewing my comments. I meant http://trac.fonosfera.org/fon-ng/wiki/reportbugs of course...

comment:39 follow-ups: Changed 7 years ago by matthijs

  • Description modified (diff)

Okay, it seems we've finally got a solution for this problem. The analysis is as follows:

Every 10 seconds, onlined does a HTTP request to updates.fon.com to see if the connection is still up. If the request fails, the Fonera goes offline. However, it seems that every then and again, the connection to updates.fon.com fails, causing the Fonera to go offline. At least in our testing it seems there is no real reason for the failure. One would expect that the retransmission stuff of TCP would compensate for any packet loss or other transient network errors, but it seems the TCP SYN packet (that initiates the connection) is only sent three times before giving up. There is still a chance that all three of these packets get lost, making the connection fail. If the connection is heavily loaded, the chances of this happening increase considerably (which is consistent with what users have been seeing).

Even though the chances of such failure are really slim, the fact that the Fonera sets up a connection every 10 seconds probably causes the failure to actually show up repeatedly.

Before 2.3.6.0, onlined would also do a request to Google, but this was removed (probably for policy reasons, I'm not sure). So before, if the connection to updates.fon.com failed, it was even less likely that the connection to Google also failed. Some testing with us also shows that the connections to Google and updates.fon.com fail equally often, so it does not seem to be a server-side problem.

Testing the solution

The solution we have implemented is quite simple: Don't go offline on a connection error right away. Instead, retry the request up to two times, only if three subsequent requests fail. This should make sure that the Fonera goes offline only when real connection problems are happening.

If you are having this problem, we would be grateful if you could test this fix. If it works for a few people, we can go forward with releasing 2.3.6.1 with this fix. To get the fix, use the following commmand:

root@Fonera:~# wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-retry

Again, see this page for instructions on running commands. If you have applied the workaround koter84 proposed, don't forget to reverse it (or reset to factory settings _before_ running the above command).

comment:40 Changed 7 years ago by matthijs

Btw, don't forget to restart the Fonera after running the above command...

comment:41 Changed 7 years ago by Josemi <josemi@…>

I get this error while trying to get the fix: http://pastebin.com/1ZWpsQD4

comment:42 Changed 7 years ago by matthijs

Hmm, I've seen that one as well, but it was gone when I retried a minute later. If it sticks around for you, you can kill onlined first using:

root@Fonera:~# killall onlined

After that, the wget command should work.

comment:43 Changed 7 years ago by anonymous

I feel that this proposed solution is somewhat misguided.

Yes, it's a good idea to disable the PUBLIC access point in the event that the internet connection is believed to be unreliable, on the other hand, this should definitely not affect the private AP.

I think the error message is entirely unhelpful to most users.

May I suggest that one feature of the next firmware ought to be the the ability to disable this behaviour, so even if onlined cannot ping the fon update server we should never block or interfere with the user's browsing experience.

comment:44 Changed 7 years ago by koter84@…

i agree with the above anonymous post..

this "feature" should have an "off"-button... i'll install this fix to test it out.. and let you know if something goes wrong..

comment:45 Changed 7 years ago by matthijs

I agree that the current implementation of the orange page is a bit dubious. There is a genuine use case: When you misconfigure your internet connection, it makes sense to get redirected to the Fonera instead of just getting a generic browser timeout. When the internet connection is just failing, the page is probably less useful. I've noted your concern and I'll see if we can find some way to improve this).

Nevertheless, the solution is an actual solution to this problem: It makes sure that onlined functions again and does not think that connection is broken when it is not.

comment:46 Changed 7 years ago by koter84@…

Jul 22 22:45:50 Fonera user.emerg syslog: starting onlined
Jul 22 22:47:32 Fonera user.emerg syslog: onlined: connection to updates.fon.com:80 failed: Operation now in progress
Jul 22 22:47:33 Fonera user.emerg syslog: onlined: Check failed. Error count: 1
Jul 22 22:47:38 Fonera user.emerg syslog: onlined: Check ok, resetting error count

looks like the fix is working

comment:48 Changed 7 years ago by sal@…

I agree that the current implementation of the orange page is a bit dubious. There is a genuine use case: When you misconfigure your internet connection, it makes sense to get redirected to the Fonera instead of just getting a generic browser timeout. When the internet connection is just failing, the page is probably less useful. I've noted your concern and I'll see if we can find some way to improve this).

Thanks for this - I agree, there are some users who will find this helpful. For example, the beginner user who does not realize that he has to connect the Fon up to his existing modem might benefit from some instructions. Perhaps the orange-screen could be given a basic wiring diagram, so that it's more helpful to the casual user.

this "feature" should have an "off"-button... i'll install this fix to test it out.. and let you know if something goes wrong..

Definitely, but to be clear, I think the feature should always be active for the public FON Access-Point. The switch determines if the orange-screen affects the private users as well. Is that possible?

FYI, after installing the onlined-retry I have not yet had an orange-screen today. It's a clear improvement.

There is still a chance that all three of these packets get lost, making the connection fail. If the connection is heavily loaded, the chances of this happening increase considerably (which is consistent with what users have been seeing).

I agree with this... it sounds like we need to be a little more relaxed about this. For example, if fewer than 10% of the packets are returned over a sufficiently long period (e.g. 1 minute), then it makes sense to disable the public-access point, since there's unlikely to be any service worth paying for.

Salim Fadhley

comment:49 in reply to: ↑ 37 ; follow-up: Changed 7 years ago by anonymous

Replying to matthijs:

I would like to keep this report about the issue with the orange page If you have the issue of disappearing public signal, please don't comment on this ticket.

Where should we comment disappearing public signal issue then?

comment:50 in reply to: ↑ 39 ; follow-up: Changed 7 years ago by anonymous

The fix is not working for me. Maybe I am doing it wrong?

After running """wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-retry""" I get this message:

http://peecee.dk/upload/view/259391

And after rebooting/restarting the Fonera I get the orange page on every URL (Your Internet is Misconfigured).

It failed doing the command three times. Every time I have to do af factory restore to get the Fonera to work again.

comment:51 Changed 7 years ago by anonymous

After a few days of testing, the 1st onelined fix does not entirely eliminate the orange-screen bug.

I've been doing a bunch of large video uploads, and maxing out the upload bandwidth is still enough to occasionally produce the screen.

comment:52 in reply to: ↑ 50 Changed 7 years ago by anonymous

Replying to anonymous:

The fix is not working for me. Maybe I am doing it wrong?

After running """wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-retry""" I get this message:

http://peecee.dk/upload/view/259391

And after rebooting/restarting the Fonera I get the orange page on every URL (Your Internet is Misconfigured).

It failed doing the command three times. Every time I have to do af factory restore to get the Fonera to work again.

The command must look like this:

root@Fonera:~# wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-retry
Connecting to www.stdout.nl (94.142.244.14:80)
onlined              100% |***********************************************************************|  6799  --:--:-- ETA
root@Fonera:~#

Note that this is a one line command.

comment:53 Changed 7 years ago by anonymous

Works for me. Maybe just release 2.3.6.1? and not add other bugs since this one is a blocker.

comment:54 in reply to: ↑ 49 Changed 7 years ago by matthijs

Replying to anonymous:

Replying to matthijs:

I would like to keep this report about the issue with the orange page If you have the issue of disappearing public signal, please don't comment on this ticket.

Where should we comment disappearing public signal issue then?

I've just created #874 for this issue.

Regarding the future of onlined, it is likely that we will remove it alltogether in the future. For 2.3.6.1, we'll still go with this fix, to keep the amount of changes minimal. It seems that this fix prevents the orange page in most cases, which is enough for releasing 2.3.6.1.

We've waited a bit with releasing 2.3.6.1 to collect some test results (also on the other bugs), but things look promising.

comment:55 in reply to: ↑ 39 Changed 7 years ago by anonymous

Replying to matthijs:

Okay, it seems we've finally got a solution for this problem. The analysis is as follows:

Every 10 seconds, onlined does a HTTP request to updates.fon.com to see if the connection is still up. If the request fails, the Fonera goes offline. However, it seems that every then and again, the connection to updates.fon.com fails, causing the Fonera to go offline. At least in our testing it seems there is no real reason for the failure. One would expect that the retransmission stuff of TCP would compensate for any packet loss or other transient network errors, but it seems the TCP SYN packet (that initiates the connection) is only sent three times before giving up. There is still a chance that all three of these packets get lost, making the connection fail. If the connection is heavily loaded, the chances of this happening increase considerably (which is consistent with what users have been seeing).

Even though the chances of such failure are really slim, the fact that the Fonera sets up a connection every 10 seconds probably causes the failure to actually show up repeatedly.

Before 2.3.6.0, onlined would also do a request to Google, but this was removed (probably for policy reasons, I'm not sure). So before, if the connection to updates.fon.com failed, it was even less likely that the connection to Google also failed. Some testing with us also shows that the connections to Google and updates.fon.com fail equally often, so it does not seem to be a server-side problem.

Testing the solution

The solution we have implemented is quite simple: Don't go offline on a connection error right away. Instead, retry the request up to two times, only if three subsequent requests fail. This should make sure that the Fonera goes offline only when real connection problems are happening.

If you are having this problem, we would be grateful if you could test this fix. If it works for a few people, we can go forward with releasing 2.3.6.1 with this fix. To get the fix, use the following commmand:

root@Fonera:~# wget -O /sbin/onlined http://www.stdout.nl/static/tmp/onlined-retry

Again, see this page for instructions on running commands. If you have applied the workaround koter84 proposed, don't forget to reverse it (or reset to factory settings _before_ running the above command).

it seems it need more than two retry cause it still occur, but less often.

comment:56 Changed 7 years ago by matthijs

Could you provide a logread of directly after this happens (and after it has been solved as well)?

comment:57 Changed 7 years ago by kaspervillum@…

The fix works ok for me.

Last week I got the orange screen 10-20 times an hour. Since I applied the fix I had three orange screens in 24 hours.

But the orange screen still pops up once in a while. Mostly when visiting websites with video or audio streaming.

comment:58 Changed 7 years ago by matthijs

  • Resolution set to fixed
  • Severity changed from unknown to normal
  • Status changed from accepted to closed

I've commited this fix as r1695 and backported it for 2.3.6.1 in r1698.

comment:59 Changed 7 years ago by Josemi <josemi@…>

Great! Nice work! For when can we expect 2.3.6.1?

Best regards,

comment:60 Changed 7 years ago by koter84@…

why is this closed? the problem still exists, it just happens less often...

comment:61 Changed 6 years ago by anonymous

My ISP uses capture portal to login and the orange screen won't let me get to the login screen. One nice work around could be to let the onlined make a post request as defined by the user after the login fails and checking once again before declaring offline state.

comment:62 Changed 6 years ago by sal@…

Is anybody at all working on fixing this serious bug? I get the impression that development of Fon's platform has ground to a halt.

I agree - this ticket should be re-opened. It's still a bug in the latest & beta versions of the firmware.

comment:63 Changed 6 years ago by matthijs

To keep things organized, and because the very frequent orange page has been fixed, this ticket remains closed. However, see #898 for discussion on a more permanent solution to the underlying problem.

comment:64 Changed 6 years ago by anonymous

i don't know if you allready found a solution/workaround to your problem but i would like to make a suggestion.. i think there are 2 options with the ISP capture..

1) use the fix i placed here it's post 36, it just turns off the dns-redirect so you don't get redirected to the orange page if onlined goes offline

2) also use my post 36, but instead off commenting out (using the #) the two lines, change the ip (213.134.45.154) to the ip of your ISP-portal.. like so:

change this
S=`cat /tmp/run/fonstate`
[ "$S" == "Offline" ] && X="--address=/#/213.134.45.154 -T 1"

to this
S=`cat /tmp/run/fonstate`
[ "$S" == "Offline" ] && X="--address=/#/ip.of.isp.capture -T 1"

i haven't tested this, and it's just an idea, but my guess is that it should get you redirected to the ISP-capture page instead of the orange-page... i still don't know if that's what you want, when you start firefox and let it reopen/restore your tabs they all get redirected to that page. After you login you can't just reload all tabs, because then they reopen the ISP page... but your milage may vary :D

comment:65 Changed 6 years ago by koter84@…

sorry, the previous post is mine, but i forgot to enter my email in the input-box.. doh. :P

Add Comment

Modify Ticket

Action
as closed The owner will remain matthijs.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.