Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 43 subscribers
  • Views 31353 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

'Real' Shell Access to modify config-Files (edit Dyndns-Settings)

MarkusArndt

I must quickly migrate from UTM 9 to XG because my private network (3 families) exceeds the limit of 50 devices (handys for the Kids ... :-)
To reach my homenet from the outside is (unfortunately ;-) a core-requirement of my family and we can't get a static IP from my provider.

The new firewall has no DynDNS-Support for my (free) DynDNS provider selfhost.eu, but the Protocoll is DynDNS.org-kompatible, which is directly supported in the dropdownbox.

I thought it must be possible to change the service-url for the ip-update in a config-file. So I found an old post, which adresses this problem and someone wrote (for UTM9): "Modify /var/confd/res/dyndns/features.ph to change URI from DynDNS directly"

But in the console of the new XG I can only choose predefined commands and can't edit and navigate the underlying filesystem (except using a hard-disk editor and change the bits directly).

Can somebody give me a tip, how I can solve this problem? (e.g. free console-acess or another workaround to modify the right config file in the new UTM version)

(Loosing support / warranty for the whole system after file-modification is no big problem for me, because it's a private license at home and nobody dies when something goes wrong ... :-)



This thread was automatically locked due to age.
Parents
  • +1
    I solved the Problem myself and it works with selfhost.eu now:

    - Logon to Sophos XG via Putty
    - Select 5 and 3 for Console (Thanks to lferrara!)
    - List all Dyndns-Provider with command
    psql -U nobody -d corporate -c "select * from tblddnsserviceprovider"
    - The Entry with ID 1 is Provider 'Dyndns' with Protokoll 'dyndns2' and the korrekt Provider-URL
    - My free Dyndns-Provider, selfhost.eu, offers the same Protocoll dyndns2 with his own Update-URL (= carol.selfhost.de)
    - I upgraded the URL with the folowing command:
    psql -U nobody -d corporate -c "update tblddnsserviceprovider set serverstring = 'carol.selfhost.de' where serviceproviderid=1"
    - I restarted the XG but I don't know, if it's really necressary.
    - I added Dyndns-Config for Provider "Dyndns" in the WebConsole with HostName and Credetials from selfhost.eu.

    After Reconnecting the WAN-Interface (DSL/PPPoE) the Sophos sucessully upgrades the Public IP at selfhost!! :-)

    (
    At first I try to insert an own entry in the table tblddnsserviceprovider but this was a bad idea. The Dyndns-client-Service from XG-OS went "red" and doesn't start anymore!?? To get it working again I and dropped my new entry.
    Unfortunally I can't update or delete Dyndns-Lines in WebConsole after this try. After deleting the Account via database
    psql -U nobody -d corporate -c "delete from tblddnsaccountdetail"
    the client-process starts without problems, when I restarted the XG.
    So - no warranty for not destroying your Database ... :-)
    )

    But when you only upgrade the URL from an existing Provider-Entry the risik is very small I think.

    This hack will surly work with many other Dyndns-Providers, when they offer the dyndns2-Protokoll to update the IP.
  • 0 in reply to MarkusArndt

    Hello,

     

    now more then 4 years later this is still an issue!

    I'm using my own ddns server now for years. I setup a static dns entry and this made it possible to reroute the members.dyndns.org request to my own ddns server.

    But now, updating from v17.5 to v18 it stopped working.

     

    Some deeper inverstgation showed that now the XG tried to verify the ssl certificate, and this naturaly failed.

     

    thanks to your solution I was able to change an entry in the config db to match my ddns server.

    It is also possible to change the name of the ddns provider to reflect the setting. In your usecase this could be:

    psql -U nobody -d corporate -c "update tblddnsserviceprovider set displayname = 'Selfhost DDNS' where serviceproviderid=1"

     

    Works like a charme.

     

    Thank you very much for your work, you saved my day!

     

Reply
  • 0 in reply to MarkusArndt

    Hello,

     

    now more then 4 years later this is still an issue!

    I'm using my own ddns server now for years. I setup a static dns entry and this made it possible to reroute the members.dyndns.org request to my own ddns server.

    But now, updating from v17.5 to v18 it stopped working.

     

    Some deeper inverstgation showed that now the XG tried to verify the ssl certificate, and this naturaly failed.

     

    thanks to your solution I was able to change an entry in the config db to match my ddns server.

    It is also possible to change the name of the ddns provider to reflect the setting. In your usecase this could be:

    psql -U nobody -d corporate -c "update tblddnsserviceprovider set displayname = 'Selfhost DDNS' where serviceproviderid=1"

     

    Works like a charme.

     

    Thank you very much for your work, you saved my day!

     

Children
No Data
Unfiltered HTML