Modify

Opened 8 years ago

Closed 6 years ago

#1119 closed enhancement (wontfix)

Instability between Fon2.0n and Virgin Media Router (no other hardware or service available to test) - workaround provided

Reported by: JonTheNiceGuy <jon@…> Owned by:
Priority: normal Milestone:
Component: fon-network Version: 2.3.6.1 (Gari jr.)
Severity: unknown
Cc: Hardware: 2.0n (FON2300)

Description

I have a Fon2.0n connected to my Virgin Media supplied Cable Modem.

Over the past few weeks, I've seen a degree of instability, particularly when performing large downloads from my Android phone over the WiFi?.

When away from the house today, I noticed that I was unable to reach the OpenVPN connection to my Fon router, so arranged for the Fon to be power cycled. It came up cleanly, and I was able to connect again.

The device is still reachable via the WiFi? connection (where I can simply reload the network with /etc/init.d/network reload to fix it), and I'm sure a cabled connection would also work.

Ideally, I'd rather not know I've had a problem, just had it resolve itself.

To achieve this, I wrote a script to reboot the router when it fails to connect to it's default gateway, and it's DNS server on 5 separate occasions, spaced 30 seconds apart. If the eth0.2 connection is not listed as UP or RUNNING (a hold over from other devices I manage via work - I don't know whether this would still be the case on a Fon device), it will sleep for 120 seconds before performing the check again.

I have attached the script I wrote, and would appreciate some guidance as to whether this is something which might be useful, either in the Fon code, or as a script to suggest if someone else is suffering from a similar issue (such as, perhaps ticket #1082?)

Attachments (1)

rebooter (3.7 KB) - added by JonTheNiceGuy <jon@…> 8 years ago.
rebooter (AkA CheckWanForDropouts?)

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by JonTheNiceGuy <jon@…>

rebooter (AkA CheckWanForDropouts?)

comment:1 Changed 6 years ago by matthijs

  • Status changed from new to infoneeded

Is this still a problem for you? The instability might have improved with the recent 2.3.7.0 releases perhaps?

As for your rebooter script, it looks ok at first glance (didn't look closely though). However, the checks it peforms are similar to the ones ran by onlined, so you might get away with putting a reboot in /etc/fonstated/Offline as well (though you'd have to make sure that there is no Offline event triggered at startup, which I'm not sure of).

comment:2 Changed 6 years ago by Jon "The Nice Guy" Spriggs <jon@…>

My upstream device has changed now, and I've not noticed the issue since then. It's probably worth closing this.

comment:3 Changed 6 years ago by matthijs

  • Resolution set to wontfix
  • Status changed from infoneeded to closed

Add Comment

Modify Ticket

Action
as closed The ticket will remain with no owner.
Author


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

 
Note: See TracTickets for help on using tickets.