Opened 7 years ago

Last modified 5 years ago

#1106 infoneeded bug

Wifi restarts often when 3G signal low

Reported by: mihaly.reg@… Owned by:
Priority: normal Milestone:
Component: fon-network-3g Version: beta2
Severity: unknown
Cc: Hardware: 2.0g (FON2202)

Description (last modified by matthijs)

F2G connected to internet on 3G dongle. No LAN cable plugged in (no internet nor intranet). Using wifi from a mobile device. 3G signal is at lower value and have some fluctuations, for short time it can disconnect then immediately reconnect.

The problem:

every time 3G is disconnecting/reconnecti4g the wifi interface is restarting ! This is not good at all because the device (e.g. smartphone) connected to wifi lose connection and must reconnect. All programs using that connections must be restarted (e.g. If I was listening to internet radio station I must reconnect first to wifi then search again for the radio station)

My opinion is that the 3G disconnect/reconnect has to be transparent for the wifi user, not disturbed by wifi disconnects. Ticket #1105 may improve also this situation...

p.s. Tested only on F2G. May be also a problem for F2N, but not tested.

Attachments (1)

puttywf.log (18.2 KB) - added by mihaly.reg@… 7 years ago.
logread after restart 3g from webui wifi restarted

Download all attachments as: .zip

Change History (9)

comment:1 Changed 7 years ago by matthijs

  • Description modified (diff)

Adding some newlines to the description for readability.

comment:2 Changed 7 years ago by matthijs

  • Status changed from new to infoneeded

Just to confirm: You are talking about a restart of the private wifi, not the public wifi?

Could you capture a logread from shortly after such a wifi restart? That might help figuring out why this is happening.

Changed 7 years ago by mihaly.reg@…

logread after restart 3g from webui wifi restarted

comment:3 Changed 7 years ago by mihaly.reg@…

Added logread for scenario restarting 3g from webui, the wifi restarted shortly after pressing button in webui. The original scenario is harder to reproduce, but I guess this is somehow the same case.

comment:4 Changed 7 years ago by anonymous

yes the private wifi is restarting, actually i have the public disabled anyway.

comment:5 Changed 7 years ago by matthijs

With an explicit restart, this behaviour can be explained. Restarting calls the UMTS event, which pretty much restarts the entire network. This is needed when enabling or disabling the UMTS connection (since switching from or to bridge mode completely turns around the networking configuration). Strictly speaking, this would not be needed when just restarting 3G, but I'm not sure if we can easily make that distinction. I can look into this, though.

However, when the signal strength is low and 3G is reconnecting because of that, the above should not apply AFAICS. This is handled all internally in umtsd.lua, so the UMTS even is not called and the wan network is not restarted in this case. So, if you could get a logread of this auto-reconnect case, that would still be a help. If you have trouble capturing the logread (because you're not always around when such a restart happens), you could enable a full syslog by uncommenting the logread lines in /etc/init.d/boot.

comment:6 Changed 7 years ago by mihaly.reg@…

Yes, the low signal scenario is hard to reproduce, tried to move around with fonera in the house but it did not restarted wifi. Couple of days ago it happened very often, now it's not happening at all.

If I enable full syslog by uncommenting the logread lines in /etc/init.d/boot there is a danger of running out of disk ? I'm reffering to a scenario when there is no SD Card or HDD attached to fonera so the logfile could be saved only in /tmp which is limited.


comment:7 Changed 7 years ago by matthijs

/tmp/ is a memory device, so there is a danger of running out of memory, I think (which will cause a reboot). I've never seen it happen, but I've only ran with full logging enabled for a few hours. You might want to keep an eye on your memory usage if you try this, I guess.

Alternatively, you could attach some USB storage and store the logread there instead (you'll want to manually start it instead of from /etc/init.d/boot, since the USB disk is probably not mounted so early.

comment:8 Changed 5 years ago by RichardPt

New username suffer two evaporative patients. Volume changes are long impressive, as sorties can directly convert further into stimulus and opposition.

Add Comment

Modify Ticket

as infoneeded The ticket will remain with no owner.

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

Note: See TracTickets for help on using tickets.