The client has a terrible, unreliable FTTC connection.
-
The client has a terrible, unreliable FTTC connection. So, this morning, I've been testing several devices and 4G carriers to find a reliable alternative when the FTTC is full/down.
The good, old LTE12 Chateau is the best for this task, giving a stable and reliable 220/50 Mbit/sec thanks to carrier aggregation.
The newer but smaller hAP ax lite LTE6 is still giving a good result, around 100/50 - expected, as it's "only" a LTE6. This will probably come to my office, while I'm waiting for the Chateau 5G (LTE20) to arrive - probably not before middle of November.Now, I need to create proper queues and rules to manage the two connections - at the moment, I've implemented only the failover and some simple queues on the FTTC.
Lunch time.
-
The client has a terrible, unreliable FTTC connection. So, this morning, I've been testing several devices and 4G carriers to find a reliable alternative when the FTTC is full/down.
The good, old LTE12 Chateau is the best for this task, giving a stable and reliable 220/50 Mbit/sec thanks to carrier aggregation.
The newer but smaller hAP ax lite LTE6 is still giving a good result, around 100/50 - expected, as it's "only" a LTE6. This will probably come to my office, while I'm waiting for the Chateau 5G (LTE20) to arrive - probably not before middle of November.Now, I need to create proper queues and rules to manage the two connections - at the moment, I've implemented only the failover and some simple queues on the FTTC.
Lunch time.
@stefano need to get one of those Chateau 5Gs in here to test (backordered everywhere!)
-
The client has a terrible, unreliable FTTC connection. So, this morning, I've been testing several devices and 4G carriers to find a reliable alternative when the FTTC is full/down.
The good, old LTE12 Chateau is the best for this task, giving a stable and reliable 220/50 Mbit/sec thanks to carrier aggregation.
The newer but smaller hAP ax lite LTE6 is still giving a good result, around 100/50 - expected, as it's "only" a LTE6. This will probably come to my office, while I'm waiting for the Chateau 5G (LTE20) to arrive - probably not before middle of November.Now, I need to create proper queues and rules to manage the two connections - at the moment, I've implemented only the failover and some simple queues on the FTTC.
Lunch time.
@stefano Exactly which WWAN module does the Chateau use?
-
@stefano Exactly which WWAN module does the Chateau use?
@apicultor this is the chipset of mine (but it's an old device): EG12-EA
-
@apicultor this is the chipset of mine (but it's an old device): EG12-EA
@stefano Oh no, Quectel. Their firmware update process is trash and unreliable (if you can even get the update out of them by begging on their forum) and when their updater says success and leaves your modem bricked (exposing only a QDSS DATA device and nothing else) they tell you to buy a new one.
Go on, ask me how I know.
-
@stefano Oh no, Quectel. Their firmware update process is trash and unreliable (if you can even get the update out of them by begging on their forum) and when their updater says success and leaves your modem bricked (exposing only a QDSS DATA device and nothing else) they tell you to buy a new one.
Go on, ask me how I know.
@apicultor Oh, that's a problem. I've had this for 5 years and upgraded it (it's been serving me at office) and it always worked but...yes, I guess it's not that nice.
-
The client has a terrible, unreliable FTTC connection. So, this morning, I've been testing several devices and 4G carriers to find a reliable alternative when the FTTC is full/down.
The good, old LTE12 Chateau is the best for this task, giving a stable and reliable 220/50 Mbit/sec thanks to carrier aggregation.
The newer but smaller hAP ax lite LTE6 is still giving a good result, around 100/50 - expected, as it's "only" a LTE6. This will probably come to my office, while I'm waiting for the Chateau 5G (LTE20) to arrive - probably not before middle of November.Now, I need to create proper queues and rules to manage the two connections - at the moment, I've implemented only the failover and some simple queues on the FTTC.
Lunch time.
@stefano i have 2 of those hAP ax LTE6 devices and they are surprisingly good. In my case speed isn't much of an issue, but failover configuration and flexibility were. WiFi was a bonus and it works fine. Yeah, I'm a fan. Connecting remote locations through wireguard and I feel confident I can administer these remotely anywhere.
-
@stefano i have 2 of those hAP ax LTE6 devices and they are surprisingly good. In my case speed isn't much of an issue, but failover configuration and flexibility were. WiFi was a bonus and it works fine. Yeah, I'm a fan. Connecting remote locations through wireguard and I feel confident I can administer these remotely anywhere.
@drizzy Exactly. Those devices are reasonably priced and reliable. I love them.
-
@apicultor Oh, that's a problem. I've had this for 5 years and upgraded it (it's been serving me at office) and it always worked but...yes, I guess it's not that nice.
@stefano Upgraded the modem firmware, or the Chateau? The Chateau probably does not ever attempt to push a firmware update to the modem.
-
@stefano Upgraded the modem firmware, or the Chateau? The Chateau probably does not ever attempt to push a firmware update to the modem.
@apicultor both of them