Vodaphone Suresignal: Difference between revisions

← Older edit

Vodaphone Suresignal (view source)

Revision as of 00:25, 18 August 2018

30 bytes added , 18 August 2018

→‎top: clean up, typos fixed: etc → etc. , eg: → e.g.:

Reedy

editor

699

edits

Revision as of 10:09, 5 May 2017 (view source) AA-Andrew (talk \| contribs) mNo edit summary ← Older edit		Latest revision as of 00:25, 18 August 2018 (view source) Reedy (talk \| contribs) (→‎top: clean up, typos fixed: etc → etc. , eg: → e.g.:)
(3 intermediate revisions by 2 users not shown)
<indicator name="Front">[[File:Menu-document.svg\|link=Category:Technical Documents\|30px\|Back up to the Technical Documents category]]</indicator> Occasionally we get questions from customers about their Vodafone suresignal devices not working. Typically this is when the broadband ~~server~~service has just been moved over to us. The device was working ~~previosly~~previously, but since the change in broadband provider it has stopped working. This page is probably also relevant to devices used by other carriers,eg e.g.: Vodafone's Suresignal O2's Boost Box TMobile's Signal Box etc. Here are some notes to help get it working again. The carrier may unblock the device automatically after 24 hours, so waiting a while may be the fix! ==The change in IP address being used may have caused ~~Vodafone~~the mobile carrier to block the device== This may be due to the carrier needing to keep a record of IPs and postcodes where the device is being used as they use radio frequencies that are controlled by OFCOM and require this data to be tracked. Contacting the Carrier's support team and saying the IP has changed and ask them to check if it has been barred. ==A change in the MTU size may have broke it== (Less likely) The device may be using a 1500 MTU size with df (don't fragment) set. If your new broadband service is using an MTU of 1492, then changing it to use 1500 may help.