Connection error

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Connection error

Post by toonnoot »

Seems like there are problems with dropbear:
What is causing this?

Installing dropbear (2014.66-r0) on root.
Upgrading update-alternatives-opkg from 0.1.8+git0+53274f0875-r1 to 0.1.8+git0+53274f0875-r2 on root.
Downloading http://feed.hae.int/feeds/nxt/oe/angeli ... p-neon.ipk.
Collected errors:
* opkg_download: Failed to download http://feed.hae.int/feeds/nxt/oe/angeli ... p-neon.ipk: Couldn't connect to server.
* opkg_install_pkg: Failed to download update-alternatives-opkg. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package dropbear.
Flushing iptables: iptables.
Loading iptables settings: iptables.
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

@The Hog; I remember having similar problems a while ago, and I think you reset the server or something right?
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

seems like it was related to the VPN keys?

I have a toon2 with old software (recovered), that was activated.
i ran the rootatoon script, which kept throwing this error.

because dropbear couldnt be installed, I couldnt access it over SSH.
the script also ended with the same connection refused error.

now I have recovered the toon again, and reset to factory defaults.
toon is now in activation screen.

Do I know just wait here until I get a valid vpn key and can proceed with the activation script?
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

hmm alternative is that there are problems on the eneco side of things...
downloading of the 5.49.19 is progressing incredibly slow.


i managed to get a toon activated by connecting with my wifi, restarting a few times until I got connected to the SC, then connected to the rpi hotspot and immediately started the activation script.
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

getting the exact same error again.

The toon was activated and connected to the service center, so I do not understand why I cannot install dropbear.

yesterday it was working again, but now it is failing again.

anyone else having the same issues?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2112
Joined: Sun Aug 20, 2017 8:53 pm

Re: Connection error

Post by TheHogNL »

Your toon isn't trying to install dropbear. It is trying to install a package from an update. Please finish the normale update of the toon before installing dropbear.
Member of the Toon Software Collective
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

TheHogNL wrote: Thu Sep 29, 2022 12:34 pm Your toon isn't trying to install dropbear. It is trying to install a package from an update. Please finish the normale update of the toon before installing dropbear.
So the right way of working is:
- recover toon to 4.9
- normal update to 5.xx or 6.xx (depending on what eneco provides?)
- run rootatoon script
- update toon to latest version if applicable through updaterooted script

Weird though that yesterday it randomly started working again.

And the instructions dont make sense if the above is correct, unless eneco changed something lately:
“Best is to fall back to toon1 old-fashioned rooting with the ToonRooter script and for the toon2 first perform a recovery of the firmware to the factory default firmware which from there you can use this tool.”

Currently the tool end with a connection refused error on port22.
If i try to connect manually through SSH i get the same connection refused error.
I thought this was related to the failure of the dropbear installation right?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2112
Joined: Sun Aug 20, 2017 8:53 pm

Re: Connection error

Post by TheHogNL »

At the moment you connect a 4.9 Toon2 to wifi it immediatly starts download the update again. Which will cause problems with opkg install dropbear as you notice.
Reset to 4.9 and don't connect to normal wifi. Directly to the toonrooter wifi and make sure the script is running before connect the toon so it can't open a connection to eneco's service center.

Or just let it upgrade first indeed.
Member of the Toon Software Collective
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

TheHogNL wrote: Thu Sep 29, 2022 1:17 pm At the moment you connect a 4.9 Toon2 to wifi it immediatly starts download the update again. Which will cause problems with opkg install dropbear as you notice.
Reset to 4.9 and don't connect to normal wifi. Directly to the toonrooter wifi and make sure the script is running before connect the toon so it can't open a connection to eneco's service center.

Or just let it upgrade first indeed.
Ah, that makes a lot of sense!
I will try this as soon as I get home.

Thanks for the support as always Hog!
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

okay your tip worked Hog!
Many thanks.

Now trying to run the update script, but it keeps getting stuck at:
Are your sure you want to upgrade to 5.49.19 (yes)? This is the last moment you can stop the upgrade. Answer with 'yes' will start the upgrade.
Starting the upgrade now! Just wait a while... It can take a few minutes.
Progress: 0% ..

It stays on 0% for like 5 minutes and then the script finishes in like 4 seconds after all messages flash by.
anyone else seeing this behaviour with toon2s?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2112
Joined: Sun Aug 20, 2017 8:53 pm

Re: Connection error

Post by TheHogNL »

Check the update log file in /mnt/data/update dir
Member of the Toon Software Collective
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

one last question:

I had another Toon2 that when I go into the recover mode, it has a different screen than the others.
It shows different messages, like mentioning angelica, ' writing bootfs', ' swipe to start recovery'. , etc.

Now this toon also refuses to connect to the Service Center, it has been online for a while day and still isnt connecting.
Which means that it cannot be activated and thus cannot be rooted.

Could it be that there is a batch of slightly older Toon2s that have the same VPN issues as toon1s?
If not, how can I get this toon activated (or connected to the SC)?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2112
Joined: Sun Aug 20, 2017 8:53 pm

Re: Connection error

Post by TheHogNL »

There is a pre-release batch which has other config/certificates. Useless for rooting. Seems to me you have one of these.
Small chance that you can still root without activating. Keep the toon connected to the root wifi and have the script running. It should request an update once every 24 hours.
Also keep a tcpdump running in the background at port 53 and monitoring for dns requests for feed.hae.int. If this is the case you first need to respond to this dns request with an ip address in the normal range of the eneco service center (take 172.20.1.1 as example). You can use dnsmasq.conf to do this.
Member of the Toon Software Collective
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

I’ll try the script trick first.
If that doesnt do the trick in 24hrs i’ll try the dns tip also.
Or do i need to do both for it to work?

I’ll report back once I know more
toonnoot
Member
Member
Posts: 63
Joined: Mon Jun 15, 2020 11:22 am

Re: Connection error

Post by toonnoot »

tcpdump with the -n host feed.hae.int command throws an error that feed.hae.int doesnt exist. any workaround here?
and how do I setup dnsmasq to respond to those requests?

seeing some traffic indeed from feed.hae.int after restarting:
12:14:13.406752 IP qb-100000021600-0000Q00000.wlan.34385 > 192.168.4.1.domain: 63946+ A? ping.quby.nl. (30)
12:14:13.407120 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.34385: 63946 1/0/0 A 8.8.8.8 (46)
12:14:15.578789 IP qb-100000021600-0000Q00000.wlan.60705 > 192.168.4.1.domain: 51533+ A? time.quby.nl. (30)
12:14:15.579646 IP qb-100000021600-0000Q00000.wlan.60705 > 192.168.4.1.domain: 6296+ AAAA? time.quby.nl. (30)
12:14:15.614863 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.60705: 6296 1/1/0 CNAME time.hub.quby.com. (139)
12:14:15.625851 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.60705: 51533 3/0/0 CNAME time.hub.quby.com., A 18.198.187.55, A 3.72.112.20 (93)
12:14:20.729311 IP qb-100000021600-0000Q00000.wlan.42110 > 192.168.4.1.domain: 51954+ A? time.quby.nl. (30)
12:14:20.729583 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.42110: 51954 3/0/0 CNAME time.hub.quby.com., A 3.72.112.20, A 18.198.187.55 (93)
12:14:20.732852 IP qb-100000021600-0000Q00000.wlan.42110 > 192.168.4.1.domain: 35917+ AAAA? time.quby.nl. (30)
12:14:20.733045 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.42110: 35917 1/0/0 CNAME time.hub.quby.com. (61)
12:15:23.561787 IP qb-100000021600-0000Q00000.wlan.59373 > 192.168.4.1.domain: 38513+ A? eneco.bd.toon.eu. (34)
12:15:23.580453 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.59373: 38513 3/0/0 A 54.72.188.154, A 52.208.171.35, A 52.213.90.84 (82)
12:16:03.520463 IP qb-100000021600-0000Q00000.wlan.52276 > 192.168.4.1.domain: 52845+ A? feed.hae.int. (30)
12:16:03.639640 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.52276: 52845 NXDomain 0/1/0 (87)
12:16:03.647548 IP qb-100000021600-0000Q00000.wlan.48590 > 192.168.4.1.domain: 15957+ A? feed.hae.int.wlan. (35)
12:16:03.664403 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.48590: 15957 NXDomain 0/1/0 (110)
12:16:03.670688 IP qb-100000021600-0000Q00000.wlan.40718 > 192.168.4.1.domain: 32946+ A? feed.hae.int. (30)
12:16:03.670932 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.40718: 32946 NXDomain 0/0/0 (30)
12:16:03.674253 IP qb-100000021600-0000Q00000.wlan.46599 > 192.168.4.1.domain: 40448+ A? feed.hae.int.wlan. (35)
12:16:03.674430 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.46599: 40448 NXDomain 0/0/0 (35)
12:16:23.520397 IP qb-100000021600-0000Q00000.wlan.46715 > 192.168.4.1.domain: 28101+ A? eneco.bd.toon.eu. (34)
12:16:23.540274 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.46715: 28101 3/0/0 A 54.72.188.154, A 52.208.171.35, A 52.213.90.84 (82)
12:18:04.706430 IP qb-100000021600-0000Q00000.wlan.33185 > 192.168.4.1.domain: 35084+ A? ping.quby.nl. (30)
12:18:04.706734 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.33185: 35084 1/0/0 A 8.8.8.8 (46)
12:18:06.846389 IP qb-100000021600-0000Q00000.wlan.39232 > 192.168.4.1.domain: 45089+ A? time.quby.nl. (30)
12:18:06.846663 IP qb-100000021600-0000Q00000.wlan.39232 > 192.168.4.1.domain: 38463+ AAAA? time.quby.nl. (30)
12:18:06.846705 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.39232: 45089 3/0/0 CNAME time.hub.quby.com., A 18.198.187.55, A 3.72.112.20 (93)
12:18:06.846855 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.39232: 38463 1/0/0 CNAME time.hub.quby.com. (61)
12:18:11.936980 IP qb-100000021600-0000Q00000.wlan.40227 > 192.168.4.1.domain: 56231+ A? time.quby.nl. (30)
12:18:11.937535 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.40227: 56231 3/0/0 CNAME time.hub.quby.com., A 3.72.112.20, A 18.198.187.55 (93)
12:18:11.941092 IP qb-100000021600-0000Q00000.wlan.40227 > 192.168.4.1.domain: 12304+ AAAA? time.quby.nl. (30)
12:18:11.941337 IP 192.168.4.1.domain > qb-100000021600-0000Q00000.wlan.40227: 12304 1/0/0 CNAME time.hub.quby.com. (61)
12:19:02.310846 IP qb-100000021600-0000Q00000.wlan.42575 > 192.168.4.1.domain: 38535+ A? eneco.bd.toon.eu. (34)
Post Reply

Return to “Toon Rooting”