I've been using a Netgear R6350 with OpenWRT v 23.05 configured to use wireless as a WAN in my RV. The thought was to have a wireless network with the same name/password that everything we use as we travel can connect to. Then I would either connect my Netgear router via wifi to a rv parks wifi or my mobile hotspot to get internet connectivity. The issue I've been having is that if I connect to a park wifi or my mobile hotspot, doesn't matter if I use 2.4GHz or 5GHz To connect to a internet source, eventually I have performance issues. Internet speed is way slower or causes constant buffering of streaming content when connected to the OpenWRT router as apposed to connecting directly to my internet source. Thinking there was something wrong with using WIFI interfaces in this manner, I decided to tether to my mobile hotspot via usb. I get the same issue.
Has anyone come across this issue before? If so how did do I get this issue fixed?
What should I be looking at on the router side to better troubleshoot.
You can delete all clients you added but the active one you need to configure travelmate.
Travelmate will handle all of them as you add them again when you start adding hotspots.
After having this up and running for a while and streaming a video I got a no internet available alert. I see the following in luci > services > travelmate > logview. OpenWRT was connected to my mobile hotspot.
Wed Feb 21 20:11:19 2024 user.info trm-2.1.2-2[3338]: travelmate instance started ::: action: start, pid: 3338
Wed Feb 21 20:14:14 2024 user.info trm-2.1.2-2[3338]: connected to uplink 'radio0/AtPlay-mobile guest/-' with mac '-' (1/3)
Wed Feb 21 20:14:32 2024 user.info trm-ntp [7234]: get ntp time sync
Wed Feb 21 21:40:00 2024 user.info trm-2.1.2-2[3338]: no signal from uplink
Wed Feb 21 21:40:26 2024 user.info trm-2.1.2-2[3338]: no enabled station on radio 'radio1'
Wed Feb 21 21:41:58 2024 user.info trm-2.1.2-2[3338]: connected to uplink 'radio0/AtPlay-mobile guest/-' with mac '-' (1/3)
Before I could get logged back in the connection seemed to reconnect.