Wireless Joint

@Didneywhorl yah it's just /etc/init.d/firewall restart in the startup script area,

@Dairydude thanks, that's a better solution!

Correction, it doesn't look like applying the zone of 'lan' made the difference. All that was needed was a firewall restart after the modem connects. I now have a start up script that auto reconnects firewall after 5 minutes from boot.

After a little more trial and error, I realized that the auto-created CLAT1 device needed to have the "lan" firewall zone. But since the device only appears when the modem connects, and the UI "edit" doesn't allow for setting the firewall zone, I just modified the /etc/config/firewall "lan" zone to ...

I'm 0.67 miles from mine, getting 500mbps average.

I feel like a monkey jumping and smashing keys but I managed to lock onto n41 band and my network speeds are significantly better now. Still trying to solve the ethernet issue but I did find out (through resetting and retrying) that adding the xlat interface myself did make the wifi work.

Yah I've been flashing using the recovery method (chinese recovery page with massive button), and each time I'd do a reset for good measure.
What I meant when I said earlier that wifi connects fine but ethernet doesn't... I meant that wifi clients get WAN access, but ethernet LAN clients do not ...

As it turns out... my wifi connects fine, but my ethernet ports don't.

No, just pings and nslookup.

I tried the regular wS1208 and getting effectively same result. ECM works the best, but DNS queries on rooter via ssh no longer resolves IPV6. In wg1608 firmware, if I run "ping www.google.com, I get an ipv6 address and successful pings in the WS1208 firmware, that times out and I have to explicitly ...

Should I be flashing the V2 firmware for ws1208?

ECM mode seems to work the best as I seem to have full network capabilities like opkg update within the router but still no WAN access for lan.

Thanks unfortunately QMI wouldn't connect at all.

I'm thinking this is no longer a cellular / modem issue. When I ssh into the router and run "route -n"
I see the CLAT device as the default route. This is likely why I can ping and connect to stuff on the router. (Although opkg update fails). But ...

I'm still learning here but I understand the 464XLAT device is meant for allowing IPV4 request over IPV6 connections through some translation service on (I presume on T-Mobile side). The T-Mobile sim in the mifi2000 hotspot device results in an ip address of 192.0.0.2 and gateway of 192.0.0.1 which ...

Thanks I tried a 2022 build and I see the option. And choosing the protocol type does make a difference in terms of connection, but if IPV4 is selected, it does not connect. Anything else I can get IPV6 address but no ipv4. I do have this 464-CLAT1 virtual interface in place of IPV4 but still an ...

Thanks yah, I have noticed that but most people seem to have issue with connectivity and throttling. I only found two threads about not getting IPV4 and they both just got resolved automatically. I'm going to try a later build of Goldenorb as mine is dated May of 2021 to see if it improves. As I ...

I'm not entirely sure, it's a mobile citizen unlimited plan through Calyx as far as I know. Is there other way I can tell what kind it is?

I have t-mobile 5g sim and I recently tried it my new WG1608 + Quectel RM502Q-AE and after some fiddling around I can get it to connect and register on tmobile network. However, I only get assigned an IPV6 address, IPV4 is assigned as:

Protocol: MBIM Cellular
Address: 255.255.255.255/32
Gateway: 0 ...