Guest User!

You are not Sophos Staff.

Thread Info
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 2769 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

3G backup still is considered as "failed" when in standby mode.

Slawski

I have upgraded SFOS to 16.01 and then to 16.05 (although I don't use Sandstorm) and I am still observing the same bug from 15.01.

When you configure 3G WWAN modem as a "backup" it will be disconnected until primary ISP is ok. It will connect if primary fails and will go back to disconnected state when primary will recover.

However... 3G interface in "stand by" mode is consider by XG as "failed" and an interface fail signal is displayed on the dashboard.

Why it is so long to fix such an easy usage scenario? What is stopping (besides time) the dev team from having a look at it? Can someone with paid contract submit it as a bug, please?

 

BTW: I can see in the licensing status that my XG has "Enhanced Support" enabled the same way as other features? Is that mean I can submit a bug report?

Sophos guys: I know that I'm not paying so I'm not entitled for support, but submitting bug reports may be actually helpful for you. Maybe it would be nice to reconsider the policy and allow submitting bug/suggestion reports for registered XG home users. I think that whoever decides to own a PC with SFOS on it in their home is knowledgable and passionate enough to be considered trustworthy for those reports? Don't you think?



This thread was automatically locked due to age.
Parents

  • HI Slawski, 

    I have checked in XG and able to connect with Mobile WWAN with failover condition as a backup to my Primary WAN link , I have disconnected the WAN link and able to successfully conduct failover. So the new session is created with the Backup WWAN and the internet would work with XG . On the other hand if the WWAN is still up and running and the Primary link is restored the current sessions will not be disconnected automatically. Only New sessions will able to communicate with the internet via the Primary link. 

    But the Mobile WAN should be in connected state a simple reboot may not re-connect the device again which is dependent on the dongle itself and dependent on Linux compatible. 

Reply

  • HI Slawski, 

    I have checked in XG and able to connect with Mobile WWAN with failover condition as a backup to my Primary WAN link , I have disconnected the WAN link and able to successfully conduct failover. So the new session is created with the Backup WWAN and the internet would work with XG . On the other hand if the WWAN is still up and running and the Primary link is restored the current sessions will not be disconnected automatically. Only New sessions will able to communicate with the internet via the Primary link. 

    But the Mobile WAN should be in connected state a simple reboot may not re-connect the device again which is dependent on the dongle itself and dependent on Linux compatible. 

Children
  • in reply to Aditya Patel

    Sorry, but i have a feeling you haven't understand what I have wrote.

    I will try to make it clear.

    I don't have a problem with failover functionality. The problem is with Dashboard. It shows connection as failed when it is in perfectly good condition but standing by. XG can bring 3G up automatically when it is needed and it brings down 3G configured as backup if it is not needed. That's fine. This is exactly as it should be. I complain about two things:

    1) 3G interface in standby state is shown on the Dashboard as failed
    2) switching off WWAN shuts down mwan service and it is also shown as failed neverless it has been legitimately brought down on purpose.

    So getting to the point. The bug is in the way UI shows failed state of services which has been shutdown by XG itself.

    Is it clear now ?