MDE
Expert Member
- Joined
- May 18, 2009
- Messages
- 2,247
Sounds like the new age TelkomWhat a load of BS from Octotel, cant believe they even said that.
Sounds like the new age TelkomWhat a load of BS from Octotel, cant believe they even said that.
If this is implemented, will this be for only users whom experience the drops, or would this be applied to all on Octotel? Reason I ask is that I have a few services which a log back to my house when I'm away and cgnat obviously won't allow access once implemented.PPPoE is a very stateful protocol.
If 3 LCP echo messages are missed within 90 seconds then, the NAS and/or the CPE will consider the connection as dead. Which is correct.
I'm tempted to deploy straight forward DHCP on our Octotel VLANS (which will have internet access, but behind CGNAT).
That way some of our more advanced users can setup a DHCP and a PPPoE connection and monitor pings via the Octotel DHCP connection if they are capable. Or just choose to use DHCP, or PPPoE.
It would basically require two routers plugged into the ONT, or some further cleverness, or a specific choice between protocols.
I'm pretty sure that the pings over PPPoE and DHCP will show the same amount of outages with PPPoE possibly showing a longer outage due to the time to re-establish a connection (purely due to Octotel flakiness).
But outage-time-line wise, I feel we'll see the same....
Octotel have been blaming this on our NAS's and because we're using PPPoE. Yet the same NAS'es offer services to at least 20 other FNO's on the same pool of NAS'es without issues.
Clarification:
NAS = the PPPoE server you see from your Octotel ONT, which is the server that CISP uses to terminate your PPPoE session.
FNO = Fibre Network Operator
So perhaps it's time to just got pure IP over Ethernet and prove them wrong.
An IPoE (IP over Ethernet/DHCP) disconnection will just result in packet loss obviously, so it might be less "sensitive" to the end user. But the packet loss would still be an issue, and the disconnect would still exist, just not on a PPPoE level. So not a "hard disconnect", but for the period that Octotel's network is dead, you would still have 100% packet loss.
Basically allow Octotel users to connect using DHCP (behind CGNAT) or PPPoE.
Votes to implement ? Volunteers ?
If this is implemented, will this be for only users whom experience the drops, or would this be applied to all on Octotel? Reason I ask is that I have a few services which a log back to my house when I'm away and cgnat obviously won't allow access once implemented.PPPoE is a very stateful protocol.
If 3 LCP echo messages are missed within 90 seconds then, the NAS and/or the CPE will consider the connection as dead. Which is correct.
I'm tempted to deploy straight forward DHCP on our Octotel VLANS (which will have internet access, but behind CGNAT).
That way some of our more advanced users can setup a DHCP and a PPPoE connection and monitor pings via the Octotel DHCP connection if they are capable. Or just choose to use DHCP, or PPPoE.
It would basically require two routers plugged into the ONT, or some further cleverness, or a specific choice between protocols.
I'm pretty sure that the pings over PPPoE and DHCP will show the same amount of outages with PPPoE possibly showing a longer outage due to the time to re-establish a connection (purely due to Octotel flakiness).
But outage-time-line wise, I feel we'll see the same....
Octotel have been blaming this on our NAS's and because we're using PPPoE. Yet the same NAS'es offer services to at least 20 other FNO's on the same pool of NAS'es without issues.
Clarification:
NAS = the PPPoE server you see from your Octotel ONT, which is the server that CISP uses to terminate your PPPoE session.
FNO = Fibre Network Operator
So perhaps it's time to just got pure IP over Ethernet and prove them wrong.
An IPoE (IP over Ethernet/DHCP) disconnection will just result in packet loss obviously, so it might be less "sensitive" to the end user. But the packet loss would still be an issue, and the disconnect would still exist, just not on a PPPoE level. So not a "hard disconnect", but for the period that Octotel's network is dead, you would still have 100% packet loss.
Basically allow Octotel users to connect using DHCP (behind CGNAT) or PPPoE.
Votes to implement ? Volunteers ?
PPPoE is a very stateful protocol.
If 3 LCP echo messages are missed within 90 seconds then, the NAS and/or the CPE will consider the connection as dead. Which is correct.
I'm tempted to deploy straight forward DHCP on our Octotel VLANS (which will have internet access, but behind CGNAT).
That way some of our more advanced users can setup a DHCP and a PPPoE connection and monitor pings via the Octotel DHCP connection if they are capable. Or just choose to use DHCP, or PPPoE.
It would basically require two routers plugged into the ONT, or some further cleverness, or a specific choice between protocols.
I'm pretty sure that the pings over PPPoE and DHCP will show the same amount of outages with PPPoE possibly showing a longer outage due to the time to re-establish a connection (purely due to Octotel flakiness).
But outage-time-line wise, I feel we'll see the same....
Octotel have been blaming this on our NAS's and because we're using PPPoE. Yet the same NAS'es offer services to at least 20 other FNO's on the same pool of NAS'es without issues.
Clarification:
NAS = the PPPoE server you see from your Octotel ONT, which is the server that CISP uses to terminate your PPPoE session.
FNO = Fibre Network Operator
So perhaps it's time to just got pure IP over Ethernet and prove them wrong.
An IPoE (IP over Ethernet/DHCP) disconnection will just result in packet loss obviously, so it might be less "sensitive" to the end user. But the packet loss would still be an issue, and the disconnect would still exist, just not on a PPPoE level. So not a "hard disconnect", but for the period that Octotel's network is dead, you would still have 100% packet loss.
Basically allow Octotel users to connect using DHCP (behind CGNAT) or PPPoE.
Votes to implement ? Volunteers ?
Man, everyday I lurk here and see more and more shyte from Octotell it makes me more thankful Openserve rolled around here. I have not had a single hitch since moving after waiting years for Octo to fix my bursting packet loss.
All I can say is, if you're on Octotel and get chance to move to Openserve DO IT WITHOUT HESITATION. You will not regret it.
Good luck to everyone on Octotel.
Hmmm, I am pretty sure I had that with Afrihost on Octotel. You can check that?So perhaps it's time to just got pure IP over Ethernet and prove them wrong.
Basically allow Octotel users to connect using DHCP (behind CGNAT) or PPPoE.
Votes to implement ? Volunteers ?
Man, everyday I lurk here and see more and more shyte from Octotell it makes me more thankful Openserve rolled around here. I have not had a single hitch since moving after waiting years for Octo to fix my bursting packet loss.
All I can say is, if you're on Octotel and get chance to move to Openserve DO IT WITHOUT HESITATION. You will not regret it.
Good luck to everyone on Octotel.
At one point they blamed our RADIUS server, and asked for a test account on a different RADIUS server. Which has also got absolutely nothing to do with the issue.What a load of BS from Octotel, cant believe they even said that.
Yes, with DHCP you won't experience a "disconnect" as such, but you likely have 100% packet loss for a while.Hmmm, I am pretty sure I had that with Afrihost on Octotel. You can check that?
I dont recall getting disconnects with Afrihost, but I cant recall if I ever got a lot of dead periods either. It would be too short to notice. I do recall times playing Fortnite where the connection would just be dead for a few seconds, and would have just interpret that as packet loss. Everything is starting to make a bit more sense to me. Thanks for the info!
Yes, and me! Like said, I can handle the downtime (although it is not fun to get out of bed to reconnect), the IP change is more annoying which seems like it should be solved with that?
PS: Anything on 1gbps pricing for Octotel yet to match Afrihost (or close)?
Well the IP will likely not change, unless the DHCP lease times out, but initially we will do this with CGNAT, so you won't have a real public IP.Hmmm, I am pretty sure I had that with Afrihost on Octotel. You can check that?
I dont recall getting disconnects with Afrihost, but I cant recall if I ever got a lot of dead periods either. It would be too short to notice. I do recall times playing Fortnite where the connection would just be dead for a few seconds, and would have just interpret that as packet loss. Everything is starting to make a bit more sense to me. Thanks for the info!
Yes, and me! Like said, I can handle the downtime (although it is not fun to get out of bed to reconnect), the IP change is more annoying which seems like it should be solved with that?
PS: Anything on 1gbps pricing for Octotel yet to match Afrihost (or close)?
I see many ISPs set their DHCP at 120 hours? Does that help?Well the IP will likely not change, unless the DHCP lease times out, but initially we will do this with CGNAT, so you won't have a real public IP.
Yes, Afrihost uses DHCP everywhere.
I am in city bowl, we don't have drops in connection but we sure do have pathetic speeds...On octotel, if you can get a wireshark on the WAN port via your PC or router check what you see. Look at the broadcast packets and record the MACs. It will confirm the vendor.
In the City bowl they seem to have changed from Arista to Edgecore and its more reliable,
ISP/FNO or between them have the traffic policy wrong.I am in city bowl, we don't have drops in connection but we sure do have pathetic speeds...
RSAWEB & Octotel is a hell combo lol both incompetent as much as the other.ISP/FNO or between them have the traffic policy wrong.![]()
Who did you murder in your previous life to deserve them?RSAWEB & Octotel is a hell combo lol both incompetent as much as the other.
Left this running for a bit of time FNO: Frogfoot with ~ 0.18% dropsAnyone perhaps on Octotel with a Mikrotik? Try to run a ping over MAC to the PPPoE server. Should also help to show line issues.
View attachment 1143900

That looks good.