Wireless / Mobile > Wireless Users Chat > OMGfast.... Looking for review

reply to GeekInfoNow

Re: OMGfast.... Looking for review

This is with a hardwired connection. They want you to use their router that they set up for you. I have my network setup on my e3000 and i dont want to reconfigure anything. So i was trying to hook up their modem to my e3000. I got no internet once i did that, Then i remembered the guy gave the activation people over the phone the mac address from "their" router. So all i did was go into my settings and put that in and it worked.... Then when I wanted to go back to comcast I just unhooked their stuff and unchecked clone mac.

They didnt make it out today with the new modem but they are supposed to tomorrow between 5 and 7pm. We'll see.

Sorry for the delay. I'm GliTcH. I haven't experienced any service outages since that first week. I'm not sure if they have "flipped" to WiMax since then either as I don't run speed tests daily like I used to but I can say I've been downloading ISO files of Linux distro's and such and I've seen this thing hit 60mbps consistently. You probably do have a faulty modem, if you have a strong signal you should get good speeds. I heard if your further out or the signal is weak it'll definitely harm your speeds. Are you getting 3.2mbps upload consistently? That'd be the wimax portion.

They will let you use your own router and return theirs, you just have to stay on top of them about it. In order to use your E3000 you have to clone the mac address of the E1200. They marry their modem to the mac address of the E1200, using mac cloning you can get around it. If you don't use mac cloning you'll get a public IP but won't be online. They do tend to discourage the use of your own router but you can do it, they're the ones who told me about cloning the Mac Address, and they said I could send the router back for a small monthly discount, not sure how much yet. You could program the E1200 as a repeater or Access Point, etc. I understand why they're pushing the E1200 as part of the setup though. When I first hooked my omgfast to my own router, a Buffalo HP-G54 router running DD-WRT, I was only getting about 30mbps down and 3.2mbps up. Turns out the backplane of the router was about 30mbps, that's all it could "nat", probably CPU limitation. They've tested their setup on the E1200 and it has over a 60mbps backplane, so I could see them discouraging people from using their own routers, what if you hooked their setup to a cheap $20 or $30 router that can only handle 20 or 30mbps internet connections, and then you call yelling at them about speed? The E1200 is a $40 router and can handle it. But I since hooked it to my WNDR4000, a $120 router, and it handles it just fine.

I'm really amazed they got you installed in 2 hours! That's amazing. It just seemed time consuming to bring all the equipment out, hook up the dish, the LNB, run the wire, mount everything, etc. did they preassemble the dish and mounts and everything? I always thought they really should do that, would be much faster to install if the whole assembly was already done and all they had to do was mount it to your house and aim it.

I'll upload some photo's shortly for you others.

Yes, photos please!

Also, could you do a couple traceroutes? For example to softlayer.com, dimenoc.com and singlehop.com? Those sites are respectively in Dallas, Florida (I forget there..probably Tampa) and Chicago so you can get a good idea of how Clearband passes their traffic and how much latency is on the last mile.

reply to glitchsys0

Outdoors 1

Outside 1

Close Up 1

Close Up 2

$ traceroute softlayer.com
traceroute to softlayer.com (66.228.118.53), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 4.582 ms 1.163 ms 1.195 ms
2 199.193.105.1 (199.193.105.1) 66.397 ms 64.524 ms 60.098 ms
3 192.168.100.9 (192.168.100.9) 86.536 ms 63.773 ms 85.500 ms
4 74.120.47.233 (74.120.47.233) 20.396 ms 52.436 ms 69.701 ms
5 208.67.164.150 (208.67.164.150) 42.961 ms 59.061 ms 79.866 ms
6 208.67.164.157 (208.67.164.157) 79.920 ms 32.894 ms 39.819 ms
7 198.32.124.221 (198.32.124.221) 36.001 ms 57.727 ms 79.971 ms
8 * * ae1.bbr01.sr02.hou02.networklayer.com (173.192.18.162) 86.414 ms
9 ae3.bbr01.eq01.dal03.networklayer.com (173.192.18.218) 77.616 ms 82.096 ms 79.856 ms
10 ae0.dar02.sr01.dal01.networklayer.com (173.192.18.253) 77.717 ms 97.126 ms
ae0.dar01.sr01.dal01.networklayer.com (173.192.18.211) 126.502 ms
11 po1.slr01.sr01.dal01.networklayer.com (66.228.118.138) 90.188 ms 77.508 ms
po2.slr01.sr01.dal01.networklayer.com (66.228.118.142) 81.718 ms
12 * * *

$ traceroute dimenoc.com
traceroute to dimenoc.com (72.29.64.136), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 1.724 ms 1.060 ms 1.035 ms
2 199.193.105.1 (199.193.105.1) 65.490 ms 39.191 ms 54.715 ms
3 192.168.100.9 (192.168.100.9) 30.416 ms 40.578 ms 38.611 ms
4 74.120.47.233 (74.120.47.233) 21.063 ms 38.071 ms 23.212 ms
5 208.67.164.150 (208.67.164.150) 38.596 ms 34.117 ms 40.819 ms
6 208.67.164.157 (208.67.164.157) 39.504 ms 51.641 ms 20.211 ms
7 port-channel201.car1.miami1.level3.net (4.71.210.133) 21.772 ms 40.705 ms 39.895 ms
8 ae-32-52.ebr2.miami1.level3.net (4.69.138.123) 39.881 ms 28.862 ms 44.698 ms
9 ae-3-5.bar2.orlando1.level3.net (4.69.148.210) 34.590 ms 28.437 ms 39.767 ms
10 ae-0-11.bar1.orlando1.level3.net (4.69.137.145) 39.390 ms 31.386 ms 39.619 ms
11 hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 40.698 ms 45.205 ms 30.229 ms
12 72-29-79-119.static.dimenoc.com (72.29.79.119) 45.805 ms 38.694 ms 41.474 ms
13 * * *
14 * * *

$ traceroute singlehop
traceroute to singlehop.bocario.clearband.com (76.163.66.2), 64 hops max, 52 byte packets
openpeaks-macbook-pro:~ deon$ traceroute singlehop.com
traceroute to singlehop.com (184.154.60.210), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 1.965 ms 1.050 ms 1.174 ms
2 199.193.105.1 (199.193.105.1) 67.124 ms 49.420 ms 81.445 ms
3 192.168.100.9 (192.168.100.9) 74.345 ms 39.395 ms 39.404 ms
4 74.120.47.233 (74.120.47.233) 23.841 ms 36.343 ms 38.798 ms
5 208.67.164.150 (208.67.164.150) 22.025 ms 31.750 ms 27.496 ms
6 208.67.164.157 (208.67.164.157) 23.911 ms 35.009 ms 24.197 ms
7 be-10-902-pe01.nota.fl.ibone.comcast.net (66.208.228.113) 35.964 ms 62.017 ms 79.666 ms
8 pos-1-9-0-0-cr01.miami.fl.ibone.comcast.net (68.86.88.105) 83.586 ms 45.690 ms 80.453 ms
9 pos-0-8-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.86.197) 94.538 ms 78.288 ms 75.323 ms
10 pos-2-9-0-0-cr01.chicago.il.ibone.comcast.net (68.86.85.169) 103.839 ms 77.253 ms 86.719 ms
11 pos-1-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.42) 84.362 ms 182.839 ms 105.828 ms
12 be-12-pe03.350ecermak.il.ibone.comcast.net (68.86.84.190) 77.858 ms 77.255 ms 80.268 ms
13 173.167.57.126 (173.167.57.126) 94.925 ms 103.595 ms 97.681 ms
14 ae1-50g.cr2.ord1.us.nlayer.net (69.31.111.137) 100.069 ms
ae1-40g.cr1.ord1.us.nlayer.net (69.31.111.133) 103.764 ms
ae1-50g.cr2.ord1.us.nlayer.net (69.31.111.137) 115.895 ms
15 ae1-20g.ar1.ord6.us.nlayer.net (69.31.110.250) 127.117 ms
ae2-20g.ar1.ord6.us.nlayer.net (69.31.110.254) 130.523 ms
ae1-20g.ar1.ord6.us.nlayer.net (69.31.110.250) 118.983 ms
16 as32475.ae6.ar1.ord6.us.nlayer.net (69.31.110.202) 113.179 ms
as32475.ae7.ar1.ord6.us.nlayer.net (69.31.111.30) 112.088 ms
as32475.ae6.ar1.ord6.us.nlayer.net (69.31.110.202) 78.213 ms
17 * * *

$ traceroute 4.2.2.1
traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 3.301 ms 1.828 ms 1.000 ms
2 199.193.105.1 (199.193.105.1) 53.697 ms 38.865 ms 39.947 ms
3 192.168.100.9 (192.168.100.9) 31.648 ms 35.555 ms 37.905 ms
4 74.120.47.233 (74.120.47.233) 22.146 ms 41.315 ms 37.424 ms
5 208.67.164.150 (208.67.164.150) 36.348 ms 39.912 ms 39.655 ms
6 208.67.164.157 (208.67.164.157) 40.255 ms 46.916 ms 35.663 ms
7 port-channel201.car1.miami1.level3.net (4.71.210.133) 20.156 ms 34.777 ms 24.158 ms
8 ae-32-52.ebr2.miami1.level3.net (4.69.138.123) 38.709 ms 24.894 ms 31.887 ms
9 ae-2-2.ebr2.atlanta2.level3.net (4.69.140.142) 38.153 ms 69.606 ms 39.631 ms
10 ae-21-52.car1.atlanta1.level3.net (4.69.150.67) 49.763 ms 37.134 ms 41.980 ms
11 a.resolvers.level3.net (4.2.2.1) 44.225 ms 39.212 ms 39.760 ms

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 3.197 ms 1.165 ms 1.042 ms
2 199.193.105.1 (199.193.105.1) 48.083 ms 78.494 ms 145.587 ms
3 192.168.100.9 (192.168.100.9) 21.669 ms 29.405 ms 29.701 ms
4 74.120.47.233 (74.120.47.233) 20.103 ms 29.358 ms 29.967 ms
5 208.67.164.150 (208.67.164.150) 21.839 ms 28.985 ms 41.076 ms
6 208.67.164.157 (208.67.164.157) 37.688 ms 42.779 ms 36.672 ms
7 core1-1-0-0.mia.net.google.com (198.32.124.133) 39.918 ms 58.424 ms 81.664 ms
8 209.85.253.118 (209.85.253.118) 55.941 ms 21.777 ms 39.795 ms
9 209.85.254.252 (209.85.254.252) 56.243 ms
216.239.48.192 (216.239.48.192) 79.561 ms
209.85.254.252 (209.85.254.252) 67.575 ms
10 209.85.248.31 (209.85.248.31) 39.269 ms
209.85.248.29 (209.85.248.29) 75.481 ms 68.070 ms
11 209.85.253.133 (209.85.253.133) 39.437 ms 68.041 ms 89.312 ms
12 google-public-dns-a.google.com (8.8.8.8) 134.301 ms 53.735 ms 60.219 ms


What's annoying is the first 6 hops are 'static'. I know hop 1 is my own router, but hops 2-6 is their network, that does seem a bit excessive to get me to their 'border'. 208.67.164.157, hop 6, is owned by FPL FiberNet. I'm guessing it's OMGFast's upstream provider.

reply to glitchsys0
Boy I'm not impressed with that installation at all. One good real CAT 1 or better hurricane and that will be ripped from the side of the eve and do all kinds of damage to the home could let wind and water in. Do they even have it grounded with anything to a real ground rod or cold water pipe? I would hate to have their installation be the path for lightning to take out other electronic items in the house.