Moderator: 3ne2nr Mods
teems1 wrote:originalbling wrote:Anyone knows how this is being provisioned on modems and can it compromise your network in any way?
What does paying the electrical bill have to do with it?
It's the same thing Comcast did with their Xfinity WiFi years ago.
This isn't something new which FLOW is doing. They're simply enabling an out of the box module which supposedly has been tested in other countries.
Lol.. Good looking out G..maj. tom wrote:don't worry, the internet is archived
http://webcache.googleusercontent.com/s ... /flow-wifi
http://archive.is/ipwwJ
Yeah speeds Good, but data cap too low.dean_spleen09 wrote:https://discoverflow.co/trinidad/flow-wifi
Get 200MB of data every 24 hours
Flow Wi-Fi offers speeds of up to 10Mbps download and up to 3Mbps upload
you can do better than this flow
maj. tom wrote:Well I hope you emailed your concerns and suggested corrections to Flow and Cable&Wireless then "chupacabra."
I think it is more effective to post here, bet they read here more often.
Maybe they will hire you and forget about the CCIE engineers that they're paying on their global scale networking company. I know you can teach them quite a few things about IP routing efficiency.
There is no global ip routing specialists guru group that needs years of training, you shouldn't talk rubbish, perhaps aspiring young people on this forum want to go into CCNA. The routing tables isn't all that complex and I wrote you already that it does work on the 'next hob' association principle.
N.B. the internet backbone and the Tiers networking levels, and why that particular IP route is chosen by FLOW was covered a few pages back when ED asked more or less the same question. The exact question. Or maybe it was his Digicel ping thread I think?
The fastest route is not always the direct route, your data could take a world trip on a high bandwidth fibre cable and still reach before taking the shortest physical route due to whatever reason, that is what MPLS is used for, instead of normal layer 2 routingchupacabra wrote:maj. tom wrote:Well I hope you emailed your concerns and suggested corrections to Flow and Cable&Wireless then "chupacabra."
I think it is more effective to post here, bet they read here more often.
Maybe they will hire you and forget about the CCIE engineers that they're paying on their global scale networking company. I know you can teach them quite a few things about IP routing efficiency.
There is no global ip routing specialists guru group that needs years of training, you shouldn't talk rubbish, perhaps aspiring young people on this forum want to go into CCNA. The routing tables isn't all that complex and I wrote you already that it does work on the 'next hob' association principle.
N.B. the internet backbone and the Tiers networking levels, and why that particular IP route is chosen by FLOW was covered a few pages back when ED asked more or less the same question. The exact question. Or maybe it was his Digicel ping thread I think?
I searched and see no reference to tracert in ED's posts, if you really get it you would realise that FLOW doesn't decide a route, routes are not defined form the sender, routes are defined by the routers on the way. So it is just quite common that some routers have bad tables, its called 'human error' therefor it is best that this gets fixed a.s.a.p since all FLOW traffic going to a US 'GODADDY' server is now first going to London and Switserland, I know that for you that means nothing and you personally don't care if it goes to HongKong, but any normal thinking person doesn't want its traffic to go that way.
bossmann wrote:You do know that flow is owned by C&W? Which is a London based company. They are most likely routing traffic through their servers Also what are the 7 TCP layers?
What DNS do you use btw?chupacabra wrote:Here a list of ping times if anyone else needs a new hoster. ( This using FLOW connection )
https://www.top10bestwebsitehosting.com/
Anyone using Bluehost or Hostinger? love to hear if you use them especially for a Wordpress site, looks like Hostinger is great place for traffic from TnT.
Or is Google or mr. Bezos going into hosting for small business?
If anyone figured out their pricing like to hear it too.
(btw I did most pings commands like 4 times and only used the best 4)
Also these are only ping times from their domain name servers (bluehost.com,hostgator.com etc) NOT from the real hosting servers, since godaddy has way better reply from there, still I think it does gives an indication. what to expect from TnT traffic.
Bluehost.com
35.153.7.161
PING 35.153.7.161 (35.153.7.161): 56 data bytes
64 bytes from 35.153.7.161: icmp_seq=0 ttl=46 time=95.442 ms
64 bytes from 35.153.7.161: icmp_seq=1 ttl=46 time=94.707 ms
64 bytes from 35.153.7.161: icmp_seq=2 ttl=46 time=91.123 ms
64 bytes from 35.153.7.161: icmp_seq=3 ttl=46 time=92.754 ms
Hostgator
PING 18.220.249.233 (18.220.249.233): 56 data bytes
64 bytes from 18.220.249.233: icmp_seq=0 ttl=39 time=111.495 ms
64 bytes from 18.220.249.233: icmp_seq=1 ttl=39 time=108.331 ms
64 bytes from 18.220.249.233: icmp_seq=2 ttl=39 time=106.778 ms
64 bytes from 18.220.249.233: icmp_seq=3 ttl=39 time=102.170 ms
Hostinger
PING 104.20.160.69 (104.20.160.69): 56 data bytes
64 bytes from 104.20.160.69: icmp_seq=0 ttl=56 time=69.189 ms
64 bytes from 104.20.160.69: icmp_seq=1 ttl=56 time=73.296 ms
64 bytes from 104.20.160.69: icmp_seq=2 ttl=56 time=71.571 ms
64 bytes from 104.20.160.69: icmp_seq=3 ttl=56 time=70.982 ms
Godaddy.com
PING 208.109.192.70 (208.109.192.70): 56 data bytes
64 bytes from 208.109.192.70: icmp_seq=0 ttl=45 time=152.481 ms
64 bytes from 208.109.192.70: icmp_seq=1 ttl=45 time=148.536 ms
64 bytes from 208.109.192.70: icmp_seq=2 ttl=45 time=150.281 ms
A2Hosting
PING 104.218.15.162 (104.218.15.162): 56 data bytes
64 bytes from 104.218.15.162: icmp_seq=0 ttl=50 time=108.685 ms
64 bytes from 104.218.15.162: icmp_seq=1 ttl=50 time=107.757 ms
64 bytes from 104.218.15.162: icmp_seq=2 ttl=50 time=112.581 ms
Web.com
PING 216.21.227.87 (216.21.227.87): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Return to “Ole talk and more Ole talk”
Users browsing this forum: nick5434 and 74 guests