Jump to content

dkyeager

Honored Premier Sponsor
  • Content Count

    8,293
  • Joined

  • Last visited

  • Days Won

    205

Everything posted by dkyeager

  1. If Sprint were to use 100Mhz 5g channels, that alone could make b41 uploads 2.5 to 5 times faster. 5 to 10 times faster if all B41 was 5G using 100Mhz and a less than 94Mhz channel where allowed for carrier aggregation. Rumors are also out there that 5G B41 may be allowed to use 400Mhz channels in the future. These would also make CA with other bands much more feasible. The other possibility which has been discussed before is 5G evidently has the ability to restart the frame cycle if more upload is needed. This is all theoretical at this point. Facebook Live, Facetime, and Skype come to mind as apps that could use lots of upload. Instagram would be another.
  2. ---------- Forwarded message --------- From: <fusiontables-noreply@google.com> Date: Wed, Sep 11, 2019, 2:36 AM Subject: Download your Google Fusion Tables data and migrate your maps Last year, we announced plans to shut down Google Fusion Tables, an experimental project to help visualize large datasets, especially on a map. With three months to go until shutdown on December 3, 2019, we wanted to share progress on new tools to make it easier for you to download your data and migrate your maps. Download your data with Google Takeout If you created many tables over the years, we’ve made it easy to download all your data in one step with a new dedicated Fusion Tables option in Google Takeout. You can save the rows, metadata and geometries of any base tables that you own, and export this data in the following formats: JSON, CSV and KML. Migrate your maps with a new open source tool We’ve seen a lot of great maps created with Fusion Tables, including data journalism projects that shouldn’t have to disappear along with Fusion Tables. That’s why we've partnered with Ubilabs to create a new open source tool built to preserve maps generated with Fusion Tables. To get started, go to the Fusion Tables Archive Tool and select the tables you want to export. You will need to give the tool access to your Google Drive and Fusion Tables so that it can read your tables and write archives. Here’s how it works: The data for each table is saved to its own “archive”. The data will be saved in a Google Sheet; for datasets beyond the size limits of Sheets, you'll get a CSV. This archive is stored in a top level folder called “ft-archive” in your Drive. A Google Maps visualization is automatically created with the archived data. This map preserves many of the original Fusion Tables styling configurations. Any changes you make to the Sheet or CSV will appear in the map visualization. A listing of all archived tables is stored in a Sheet. This handy Sheet is called "ft-archive-index" and lives within the “ft-archive” folder. The index Sheet summarizes each run of the archive tool and preserves the visualization URLs with encoded styles. Each time you run the archive tool, you will get additional archives based on the current data in your tables along with corresponding new rows in the archive directory. You can preview a map visualization in the archive tool, and when you’re ready to share, generate a code snippet to embed your map. If you want to embed the map on your site, you must get an API key. If you're a journalist or nonprofit, you may be eligible for free or reduced cost usage. Finally, certain features of Fusion Tables, notably geocoding, will not be supported by this tool—see this FAQ for more limitations and known issues. As mentioned, we’ve open sourced the export and visualization code. The export code will stop working on December 3, when Fusion Tables shuts down. The visualizer will continue to be available for at least a year after this date. There are guides on how to deploy and host your own version of the tool in the GitHub repo. These and other tools—including BigQuery, Cloud SQL and Maps Platform—provide newer, more specialized alternatives to Fusion Tables, from data storage to mapping. We encourage you to explore these alternatives as you transition off Fusion Tables. Sincerely, The Google Fusion Tables Team © 2019 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 You have received this mandatory service announcement to update you about important changes to Google Fusion Tables or your account.
  3. 5g properly implemented should fi x b41 upload issues. Multiband CA would also help.
  4. Anyone going through this merger process (new T-Mobile, Dish, etc) will use it as an opportunity to raise more money. Much harder to get money for organic growth. Some of Dish's delay this summer was because they were arranging financing iirc. Another possibility in construction slowdown is the shortage of equipment (except Samsung). In Sprint's case they have overbuilt compared to what they have brought online. Not certain about other carriers in this case.
  5. With CDMA SCP has site hints which allows four choices. I urge you to go beyond disabling the offset and directly support the new sequential GCI sectors as an option, but instead of calling them b41 #2 etc, call them #B etc. I would also display the sector (A, B, Γ) for its educational and practical value. If this could be set as the default for some Sprint markets that would be even better.
  6. I don't think it is fair to any carrier to judge them on their performance via roaming or a MVNO. Not all bands are used. Priority may be different. Phone may not be optimized for their bands. Service may be deliberately throttled by roaming agreement. Info could be routed through Kansas City.
  7. We are now in a sixty day public comment period on the Department of Justice's plans for the T-Mobile Sprint merger. I believe this started on August 12 with publication in the federal register: https://www.federalregister.gov/documents/2019/08/12/2019-17153/united-states-et-al-v-deutsche-telekom-ag-et-al-proposed-final-judgment-and-competitive-impact Comments evidently must be in written form and mailed to: Scott Scheele, Chief, Telecommunications and Broadband Section, Antitrust Division, Department of Justice, 450 Fifth Street NW, Suite 7000, Washington, DC 20530 (telephone: 202-514-5621)
  8. One of the main uses of a DMZ is to isolate questionable hardware from all other devices on your network, many of which almost never receive security updates. That way an IOT device can only see itself. Of course restricting a device to only what it needs from where it needs it is even better, but requires more vigilance than most people have. I see this type of DMZ use as a much better alternative to putting the Airave first for cases of where the Airave won't function without network adjustments.
  9. In what way does using a DMZ for an Airave threaten the rest of the network?
  10. I was wondering if you tested scenarios where the communication link was broken. That is where Sprint may attempt to reestablish a ipsec tunnel.
  11. Looks like the same usual port requirements to me, which has required adjustments for some routers. https://www.sprint.com/content/dam/sprint/us/en/support/airave/Airave4UserGuide.pdf page 9: 4. Connect one end of the Ethernet cable to an available LAN port on your broadband connection modem,or to a LAN port on your network. If on network: Open UDP ports 53, 67, 500 and 4500 bi-directionally. Contact your IT administrator for assistance. Great that it works for you without adjustments, which likely applies for many others, but if it does not work, putting it on the DMZ may be the easiest way for others to fix it. Besides, often IOT devices are untrustworthy as they are typically spying on other parts of the network or open unknown holes and other security risks, thus using a DMZ for such devices is a best practice.
  12. Depends on the router. if it has DMZ then that is often the easiest method.
  13. On my Sprint hunter phones I am using Tello. $7 per month for 1GB and 100 minutes of calls with unlimited text. You could also do pay as you go for much less, but then you must make a call and use some data every 90 days.
  14. All the Dish site plans I have seen through permits indicate protection sites. Typically just one antenna and RRH.
  15. Sorry dude, I picked up Shentel near Maysville KY. Once I reached Ripley OH just across the river heading north, it was Sprint Cincy Market. Now I did blow it on my Western KY question. My internal compass must have been off. I was thinking the eastern portion.
  16. Thanks for this post. I would never have looked for a small cell that close to the gtound.
  17. Please expand on the Qqualmin value. Many of us often have the same issue. Thanks
  18. The following other factors must be considered: any leases of Dish 600MHz spectrum, Dish may choose not to own 800MHz in the area, T-Mobile has a two year extended option on 4MHz of 800MHz, 2.5 in the area will go up for auction soon for the first time in many decades, mmWave could help in denser areas.
  19. Parts of Northern MN, Northern MI, Ohio are among the many places with no Verizon coverage. Some of those areas are served by AT&T (likely an informal "understanding" between the duo IMO). Starting to see T-Mobile in a few of those places. All bow down before the Verizon God. In other forums I might be burned at the stake. No carrier is perfect, even if you pay top $$$. Verizon is the slowest at my house inside the Columbus beltway. Hard to beat Sprint on roaming. I those places where I did not get T-Mobile, US Cellular, AT&T, Verizon CDMA, or some regional carrier I would sometimes pick up Canadian roaming. Rarely without some form of service. I was at a funeral yesterday in eastern Ohio without service or Wi-Fi. People adjusted. Some women have told me they avoid routes without cell service when we were comparing coverage notes for other remote Ohio places at a state wide conference. Verizon is the safe choice for many.
  20. Interesting that they plan on using carrier grade 5G for their WISP. Puts them very much in line with T-Mobiles plans/precludes them.
  21. I have always wondered about the wisdom of a 120Mhz unit when so many place have 194Mhz. They should have left the 8T8R up in those places IMO. The trouble with 5G NR is it is basically extended carrier aggregation. I want to see full B41 5G with lots of bandwidth (ideally 100Mhz) so the upload issue goes away before you even get to the notion of being able to tweak the timing to get more upload. That would also leave more room for carrier aggregation with other bands.
  22. Where Sprint improves, the duo will quickly put money in and hammer them down. I see this happen often enough to say it happens within 6 months. Sprint has not even publicized at that point. The Duo watch speed test results.
  23. This does not match my experience. Many Sprint small cells in Ohio have two carriers (no CA). We have gotten 70Mbps off of relay fed, faster off of fiber fed. Now many are in the 30-40Mbs range.
×
×
  • Create New...