WiFiX NEXQ6GO & Upgraded GO FIrmware Quectel EP06 - Bandl GUI (solved) - IPv6 (resolved)

[Mr.Taco]

Greetings,,

I finally got around to upgrading my WiFiX NEXQ6GO to a newer version of the GoldenOrb firmware. I upgraded from GoldenOrb_2021-09-10 (the version that arrrived) to version GoldenOrb_2021-09-17. It could have been from a lack of sleep, but when I had tried other builds (newer 2022 builds), I was having issues getting ip6 addresses.So I just downgraded.

I could not find my original version anywhere, including the google drive repo of archived builds.Closest was 9/17/21.

I noticed that now I'm missing my band configure box thingy. Um...how can I get this back? I enclosed examples of what I'm talking about. I don't have this page on the router anymore. I'm an idiot.

[Didneywhorl]

The newer builds require you to delete the IPV6 prefix on the Network->Interfaces global options/settings tab at the top of the page. Delete the setting there, leave blank, and reboot.

You'll need a newer build to get the band locking UI

[Mr.Taco]

The newer builds require you to delete the IPV6 prefix on the Network->Interfaces global options/settings tab at the top of the page. Delete the setting there, leave blank, and reboot.

You'll need a newer build to get the band locking UI

Thank you! I shall try that. I'll go ahead and try reflashing again. By newer builds, if I use one of the WiFiX provided ones from their support site, that should restore the band GUI? I think they have 2 versions on there posted, 10-05a for their newest and 07-23a for the previous. 404 error for the beta. Or, should I use the newest build (official) from https://www.ofmodemsandmen.com (WiFiX-NEXQ6GO-GO2022-10-31.zip)?

[Mr.Taco]

So I flashed the router to 2022-10-05 which is the WiFix supplied firmware and default settings on flashing. When it connects, it still just gets an IPv4 address. Under Network->Interfaces global options/settings, that field is blank as well.

I noticed this firmware dumped a bunch of various carrier profiles under the modem->connection profile menu. I went ahead and deleted all of them and set the default profile to "VZWINTERNET" apn.custom ttl 65.protocol type IPv4+IPv6. DIsable automatic apn is checked and all custom profiles removed.

It connects, and I get just an IPv4 address. Under interfaces " WAN1_6" it shows "Device: Not present Connected: no, Protocol: Virtual dynamic interface (DHCPv6 client). Clicking edit just shows blank screen with no options. The older firmware I would get get both IP4 and IP6 like normal.

Also, with this firmware, I still do not have any band-lock GUI page.

Not sure what to do now. Any guidence appreciated.

[Didneywhorl]

So it is connecting to the internet? You're just not getting an IPV6 address? This is common, I've seen it from one connection to the next, and even one system to the next. It is odd.

Run the AT command AT+CGDCONT? to see if the IPV stack is being presented as dual stack or IP only. The rest is up to the network to hand out.

For the band locking, that is odd. I'll have to dig out an NEXQ6 and EP06 and load that firmware and see what it shows me.

Are you using an incognito web browser page with no web cache loaded in? Just making sure.

[Mr.Taco]

So it is connecting to the internet? You're just not getting an IPV6 address? This is common, I've seen it from one connection to the next, and even one system to the next. It is odd.

Run the AT command AT+CGDCONT? to see if the IPV stack is being presented as dual stack or IP only. The rest is up to the network to hand out.

For the band locking, that is odd. I'll have to dig out an NEXQ6 and EP06 and load that firmware and see what it shows me.

Are you using an incognito web browser page with no web cache loaded in? Just making sure.

I'm sorry, I lied. I DO have the Band Locking GUI now, yay.I wasn't using private browsing but I am now. Very possible I missed the modem->misc screen.

Yes, it connects and I have internet. Just, with this newer firmare it doesn't seem to work like the older builds. The older ones (2021) would connect w/ both IP4 and IP6 addresses. If I upgrade the firmware, mirroring the settngs of the older firmware, it will connect but only give IP4 address.

Issuing the

Code: Select all

AT+CGDCONT?

command yields:

Code: Select all

+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

OK

[Mr.Taco]

One thing to note is that after awhile WAN1_6 will change from

Code: Select all

Device: Not present Connected: no, Protocol: Virtual dynamic interface (DHCPv6 client)

to

Code: Select all

WAN1_6 Type: Ethernet Adapter Device: wwan0 Connected: yes RX: 706.96 MB (575157 Pkts.) TX: 62.38 MB (320595 Pkts.) wwan0 Protocol: Virtual dynamic interface (DHCPv6 client) Uptime: 1h 39m 17s

But of course no IPv6 address.

[Mr.Taco]

Also, another thing I tried was to power cycle the router. When it came back up, the modem would NOT connect--I think due to a time mismatch, was getting alot of device not found /usb2 and error AT command...so while it was attempting/reattempting to connect, I opened another brower window and I went to system->general and synced (and saved applied) time to my local time. Then the modem connected, but with IPv4 only.

[Mr.Taco]

Then I started messing with APN names 'vzwinternet' vs 'VZWINTERNET'...still getting only IPv4. I tried shutdown/rebooting shutdown/power-cycle...and um..that's when I got 'SIM is locked with no SIM Pin entered in Profile!!' and no IMEI and/or no /dev/usb2 found error in debug log. I freaked out and I went ahead and downgraded back to 9-17-21 cleared settings and reloaded my backed up settings, power cycled and everything is OK now. For a second I thought my sim was fried or blackballed or something. But was able to get back w/o touching my sim w/ proper sim credentials shown on the modem->network status page.

There is definitely something different in how it processes the modem/connection in a fundamental way because reverting to older firmware resolves it. I could try an older but newer build and see if that fixes the issue. I haven't done anything to change the modem config low level in any way. The ONLY AT commands that I have manually entered have been ATI , and AT+CGDCONT? . That's it. I've made no low level changes to the modem. My guess is there a difference on the automatic AT commands that are scripted when initializing the modem, and there must be something majorly different between the older and the new builds? I dunno. I'm just glad I didn't fry anything. That sim lock error in red, scared me, hahaha.

[Mr.Taco]

I'm going to try flashing WiFiX-NEXQ6GO-GO2021-11-02-AB.zip and see if that works. I guess that's the last version before AB19. Then I will try WiFiX-NEXQ6GO-GO2021-11-16-AB19.zip which is the first of the AB19 releases. My current/reverted version is GoldenOrb_2021-09-17 flashed with WiFiX-NEXQ6GO-GO2021-09-17-AB.zip.

I'll report back with findings.

[Mr.Taco]

GoldenOrb_2021-11-02 worked (WiFiX-NEXQ6GO-GO2021-11-02-AB.zip) got IPv4+IPv6 no band GUI
GoldenOrb_2021-11-16(WiFiX-NEXQ6GO-GO2021-11-16-AB19.zip) worked got IPv4+IPv6 no band GUI

I guess will try newer build and see if I can find one new but not too new? AB19 seems to work. I'll try the latest archived build WiFiX-NEXQ6GO-GO2022-12-29-AB19.zip
and see what happens...

[Mr.Taco]

GoldenOrb_2022-12-29(ab19) flaky connection but finally got it to connect ,Band GUI exists. only getting Ipv4, no IPv6. was getting alot of timeout and no /usb2 found in debug log until i reset/power cycled and it finally connected but ipv4 only.


Wll try WiFiX-NEXQ6GO-GO2022-01-01-AB19.zip.

[Mr.Taco]

This is weird.

With WiFiX-NEXQ6GO-GO2022-01-01-AB19. I was getting no connection and / usb errors. Another weird thing too:

Code: Select all

Tue Jun 27 20:32:44 2023 : /dev/ttyUSB2 AT+CNMI?
+CNMI: 1,1,0,2,0
OK
  
Tue Jun 27 20:32:46 2023 : /dev/ttyUSB2 AT+QINDCFG="smsincoming"
+QINDCFG: "smsincoming",0
OK
  
Tue Jun 27 20:32:47 2023 : /dev/ttyUSB2 AT+QINDCFG="all"
+QINDCFG: "all",0
OK
  
Tue Jun 27 20:32:49 2023 : /dev/ttyUSB2 AT+CGMM
EP06
OK
  
Tue Jun 27 20:32:50 2023 : /dev/ttyUSB2 AT+QCFG="band"
+QCFG: "band",0x0,0x1008,0x0
OK
  
Tue Jun 27 20:32:52 2023 : /dev/ttyUSB2 AT+CGMM
EP06
OK
  
Tue Jun 27 20:33:09 2023 : /dev/ttyUSB2 
  
Tue Jun 27 20:33:27 2023 : /dev/ttyUSB2 AT+QINDCFG="all",1
OK
  
Tue Jun 27 20:33:30 2023 : /dev/ttyUSB2 AT+COPS=3,2;+COPS?
+COPS: 0,2,"311480",7
OK
  
Tue Jun 27 20:33:31 2023 : /dev/ttyUSB2 AT+COPS=0
OK
  
Tue Jun 27 20:33:33 2023 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)
OK
  
Tue Jun 27 20:33:35 2023 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CFUN: 1
OK
  
Tue Jun 27 20:34:05 2023 : /dev/ttyUSB2 AT+CGDCONT=1,"IPV4V6","internet.freedommobile.ca";+CFUN=4
TIMEOUT ERROR
  
Tue Jun 27 20:34:32 2023 : /dev/ttyUSB2 
TIMEOUT ERROR

MERGED LOG SAME ERROR/FLOW

Code: Select all

Tue Jun 27 20:44:38 2023 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)
OK
  
Tue Jun 27 20:44:39 2023 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CFUN: 1
OK
  
Tue Jun 27 20:45:00 2023 : /dev/ttyUSB2 AT+CGDCONT=1,"IPV4V6","internet.freedommobile.ca";+CFUN=4Can't open device .   [color=#FF0000](older fw did AT+CGDCONT=1,"IPV4V6","VZWINTERNET";+CFUN=4)[/color]
  
Tue Jun 27 20:45:00 2023 : /dev/ttyUSB2 Can't open device /dev/ttyUSB2.
  
Tue Jun 27 20:45:02 2023 : /dev/ttyUSB2 Can't open device /dev/ttyUSB2.
  
Tue Jun 27 20:45:03 2023 : /dev/ttyUSB2 Can't open device /dev/ttyUSB2.
  
Tue Jun 27 20:45:05 2023 : /dev/ttyUSB2 Can't open device /dev/ttyUSB2.
  
Tue Jun 27 20:45:15 2023 : /dev/ttyUSB2 
  
Tue Jun 27 20:45:18 2023 : /dev/ttyUSB2 AT+CPMS="SM"
ERROR
  
Tue Jun 27 20:45:46 2023 : /dev/ttyUSB2 AT+CMGL=4
+CMS ERROR: 303

TIMEOUT ERROR
  
Tue Jun 27 20:45:51 2023 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,99,0,99
OK

For some reason this build is trying to overridde the verizon one with

Code: Select all

Tue Jun 27 20:15:57 2023 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","internet.freedommobile.ca","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CFUN: 1
OK

when it should always be this:

Code: Select all

Tue Jun 27 20:33:35 2023 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CFUN: 1
OK

Even trying to overridde it myself with:

Code: Select all

AT+CGDCONT=1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
AT+CFUN=1

that "internet.freedommobile.ca" stlll manages to creep into the scripts, no idea where it's coming from. There are no custom profiles, just the default.
I downgraded back to GoldenOrb_2021-11-16(ab19) which gives me IPv4+IPv6 but no Band GUI.

This is crazy.

Hopefully I can find a happy version between Nov2021-Dec2022, maybe WiFiX-NEXQ6GO-GO2022-01-01-AB19 is just a weird one out of bunch.
Will try WiFiX-NEXQ6GO-GO2022-04-21-AB19

[Mr.Taco]

Does anyone have any copies of any older WiFiX-NEXQ6GO-GO2021-2022 firmwares they downloaded directly from the WiFix help
page (https://thewirelesshaven.com/help-page-nexq6go/ )? Not from http://aturnofthenut.com/autobuilds/ , or https://drive.google.com/drive/folders/ ... drive_link, or https://www.ofmodemsandmen.com/download.html.
Specifically anything from late Sept-Dec 2021 to Early 2022?

[Mr.Taco]

Nevermind, RESOLVED (sorta).

I found my original version shipped via this drive link posted from thread (https://wirelessjoint.com/viewtopic.php ... rive#p9752)
The google drive link shown there (https://drive.google.com/drive/folders/ ... bD7Y2WNETn) hosts some older builds including my 09-10 version. These are squashfs images so if you (try) to upgrade it via system->Backup / Flash Firmware it will bork and boot into the rescue/Chinese menu. From there, proceed normally as if you if are flashing via rescuemode, because you are.

After a few longer than usual minutes (these images are bigger than the regular 10-12mb ones), it reverted to the exact version/build I had before going down this rabbit-hole. I can now again connect via IPv4+IPv6 and I have band lock gui again--yay. It would seem my upgrade options are limited, oh well.

**RESOLVED** (sorta)

[Didneywhorl]

Your details are extremely appreciated. So many people do not follow through with the troubleshooting steps logging.

It is odd that the older version better served the IPv4/V6 as most of all of it is modem handled, though the router firmware does control much of the modems protocols via constant requests/responses.

If you don't need to change band locks very often, you can just set the bands, then update to the firmware version you want that might not have the locking embedded. You can also use AT commands to band lock if needed. I know this is dumb, as it is a feature in the firmware of the router you purchased, but as side hacky method it is possible.

The freedom mobile APN is a very weird one.

On the topic of IPV6 addresses, what is your use case/need for IPV6 on the cell connection side?

[Mr.Taco]

Before starting, I was banging my head on the table because I never had a copy of my original firmware. I regretted not using that MTD option to pull a copy of the ROM. Something I can revert back to if all else fails. Luckily by finding that firmware, all is good and I have more confidence to try messing with it to see if I can get IPv4+IPv6 via a later build.

Yeah, I just like the UI look to make it quick to view/change/lock bands. I'm in rural area, and I generally only get bands 13 and sometimes 4 and it will do CA on B4+B13 if it picks up. I wanna say sometimes I get 66 as well, so I might try B66+B13, and lock it to keep it *if* it's faster and stable, which I''m not sure it will be, 66 is more weak. I haven't done much in terms of placement/RF experiments because frankly, it works just about nothing short of excellent (I do have an old set of Linksys High Gain antennas I could try for LTE, hehe). I have potential speeds (VPN slows it down--which is fine) of around 30mbps down. Right now I'm getting 9.09 Mbps download and 6.86 Mbps upload on VPN which is more than adequate for my purposes. I'm just messing with things because I felt the need to make up for the lack of fixing things that don't need fixing,lol. Just to see if there is potential to get faster speeds--but I'm not complaining by any means.

Yes I could just use AT commands for band-locking, and I might end up doing that. I wanted to exhaust all possibilities.

There were a couple things I noticed that may/may not resolve w/ a newer GO build w/ band GUI and IPv4+IPv6.

After the flash back to the original WiFix 9-10-2021 firmware (squashfs), for some weird reason I got an error/notice I needed to upgrade "proto" software packages on the router. I remember the names because I think it told me to look up "proto" and I just did on router now to get the names:

Code: Select all

luci-proto-3g	unknown-1	
luci-proto-3x	1.0-1	
luci-proto-ipv6	unknown-1	
luci-proto-mbim	1.0-1	
luci-proto-ppp	unknown-1	
luci-proto-wireguard	unknown-1

The weird thing is that the versions were exactly the same that were already (pre)installed so no need to upgrade. But I thought it weird, and maybe it was a weird bug or maybe the router was still "internally building itself" because I ignored the error and just rebooted and that notice went away, and everything is fine on this version.

Another thing that got me thinking, and in order to do this I would have to do a flash and compare/set (basically flash the router with orig and newer build) and go through each and every setting making sure it's EXACTLY the same to test further--my thinking on that is maybe there was a default DHCP setting on one of the interfaces that is slightly off vs the original shipped firmware (i.e. DHCP vs server DHCP, or v6 DHCP, etc. etc. etc. I dunno ¯\_(ツ)_/¯ ). I never really did try messing with those to see if I would get an IPv4+IPv6 address--just kept them to default. Note: I DID change profile protocol from "Default" to "IPv4+IPv6" on later builds because default still did the same thing, I do remember trying that. Older builds will set to "IPv4+IPv6", and newer builds will set to "Default"--I've tried both and on the builds where I get just IPv4, this setting has no effect.

My need for IPv6 is only , as far as Big Red is concerned, that my connection looks like it's actually coming from a tablet. And one thing that does (slightly) concern me, is if I will stick out if I am using band(s) that the device is not sped'd for (like 66). I think the tablet only does bands 2,4,5,13, so I don't know if I'm inviting myself to potential issues or not. TTL is set of course. I even have hostname changed so it "looks" like a tablet. And VPN (or 2).

Yeah it ain't broke, I shouldn't "fix" it-- but it's just so much fun--ya know? I love this stuff.

Another thing I could try doing is flashing GoldenOrb for a ZBT_WE826-Q and see if anything is different as far as IPv4+IPv6 is concerned. I'm just curious.

If anyone is interested, I have version EP06ALAR02A08M4G_01.004.01.004 (Date: 2022-05-19) of the EP06-A firmware which according to Quectel is the latest. I thought version EP06ALAR02A08M4G (Date: 2020-05-12) was the latest, but I guess not. I haven't updated mine yet.

[Mr.Taco]

So I looked inside the 9-10-2021 firmware and I randomly (I have so many versions to choose from now, downloading so many builds, lol) chose 10-15-2022 to compare it against, and there are some major differences. I came upon this thread https://wirelessjoint.com/viewtopic.php?p=2600#p2600 showing the inner workings of the create_connect.sh script which inspired me to open both versions and look at how they do things.

From WiFiX-NEXQ6GO-GO2021-09-10 Firmware:

Code: Select all

check_apn() {
	local IPVAR="IP"
	local COMMPORT="/dev/ttyUSB"$CPORT
	if [ -e /etc/nocops ]; then
		echo "0" > /tmp/block
	fi
	ATCMDD="AT+CGDCONT=?"
	OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
	if [ -n "$(echo $OX | grep -o "IPV4V6")" ]; then
		IPVAR="IPV4V6"
	fi
	ATCMDD="AT+CGDCONT?;+CFUN?"
	OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
	if `echo $OX | grep "+CGDCONT: 1,\"$IPVAR\",\"$NAPN\"," 1>/dev/null 2>&1`
	then
		if [ -z "$(echo $OX | grep -o "+CFUN: 1")" ]; then
			OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "AT+CFUN=1")
		fi
	else
		ATCMDD="AT+CGDCONT=1,\"$IPVAR\",\"$NAPN\";+CFUN=4"
		OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
		OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "AT+CFUN=1")
		sleep 5
	fi
	if [ -e /etc/nocops ]; then
		rm -f /tmp/block
	fi
}

From WiFiX-NEXQ6GO-GO2022-10-05 Firmware

Code: Select all

check_apn() {
	IPVAR="IP"
	local COMMPORT="/dev/ttyUSB"$CPORT
	if [ -e /etc/nocops ]; then
		echo "0" > /tmp/block
	fi
	ATCMDD="AT+CGDCONT=?"
	OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")

	[ "$PDPT" = "0" ] && PDPT=""
	for PDP in "$PDPT" IPV4V6; do
		if [[ "$(echo $OX | grep -o "$PDP")" ]]; then
			IPVAR="$PDP"
			break
		fi
	done

	uci set modem.modem$CURRMODEM.pdptype=$IPVAR
	uci commit modem

	log "PDP Type selected in the Connection Profile: \"$PDPT\", active: \"$IPVAR\""

	if [ "$idV" = "12d1" ]; then
		CFUNOFF="0"
	else
		CFUNOFF="4"
	fi

	ATCMDD="AT+CGDCONT?;+CFUN?"
	OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
	CGDCONT2=$(echo $OX | grep "+CGDCONT: 2,")
	if [ -z "$CGDCONT2" ]; then
		ATCMDD="AT+CGDCONT=2,\"$IPVAR\",\"ims\""
		OXy=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
	fi
	if `echo $OX | grep "+CGDCONT: $CID,\"$IPVAR\",\"$NAPN\"," 1>/dev/null 2>&1`
	then
		if [ -z "$(echo $OX | grep -o "+CFUN: 1")" ]; then
			OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "AT+CFUN=1")
		fi
	else
		ATCMDD="AT+CGDCONT=$CID,\"$IPVAR\",\"$NAPN\""
		OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "$ATCMDD")
		OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "AT+CFUN=$CFUNOFF")
		OX=$($ROOTER/gcom/gcom-locked "$COMMPORT" "run-at.gcom" "$CURRMODEM" "AT+CFUN=1")
		sleep 5
	fi
	if [ -e /etc/nocops ]; then
		rm -f /tmp/block
	fi
}

I'm too lazy to show it but the create_hostless.sh script shows similar changes. $PDP vs IPV4V6, ¯\_(ツ)_/¯ .

One thing I could try is taking a copy of this script from one of the latest ""working IPv4+IPv6 builds" (for me at least) , (probally one of the Autobuilds, or even 9-10-2021 official), and replacing the create_connect.sh (and create_hostless.sh) script(s) that resides on the newer/latest official WiFix build, with that one.

* Also it appears that "internet.freedommobile.ca" is coming from the get_profile.sh script located in /usr/lib/rooter/connect/ along with the other connect scripts. I did a contents search of the 9-10-2021 firmware and no iteration of "internet.freedommobile.ca" was found (nor on 3-15-2023..maybe it was unique to just 10-05-2022 firmware--*edit , it's not, it was also found in WiFiX-NEXQ6GO-GO2022-01-01-AB19 ). So I could also swap this script too.