Question: I have an ID (number format) that has trailing decimals in the source data. I need to retain the rounded number (see example attached) and have the trailing decimals removed from the data. The decimals are causing upload issues/error into a system that I use.

I have tried formatting to number and removing decimal places, =INT, =ROUND, etc and I can get the cell view to reflect what I want but when I click on the cell, the formula bar still appears to retain the trailing decimals. How do I remove these? Thanks in advance!

[![Example](https://i.stack.imgur.com/n3kOe.jpg)](https://i.stack.imgur.com/n3kOe.jpg)

Answer: 
All of IP addresses 1 - 7 may well exist only between your laptop and the 4G modem. As the whole path is wired, there's no way to set up a MITM in between; unless there's another way to access your firewall. The 4G modem requires connection to a service provider, and it will only connect to the provider who provided the SIM Card, so a MITM in between the modem and the service provider is also extremely unlikely.

Tunnels in this context have nothing to do with caching, they're just a way to route traffic in a specific way. To quote [Wikipedia](https://en.wikipedia.org/wiki/IP_tunnel):

> 
> An IP tunnel is an Internet Protocol (IP) network communications channel between two networks. It is used to transport another network protocol by encapsulation of its packets.
> 
> 
> 

Usually tunnels are used because it simplifies the routing one way or another. In this context something may be internally configured to use a tunnel, for example the Ethernet-over-USB interface that connects the modem to the firewall. Can't say much more than that without knowing more of the setup; the hardware and the configuration.

Connection refused has nothing to do with port 80, only the fact that your client isn't authorized to connect to that tunnel.
Your carrier is free to use any rfc1918 (ie private soace) in their network for parts you dont need to be able to reach - indeed doing this can save real IP space. You have not pointed out where your world routable or CGN IP is defined, and doing this could be useful in you understanding how tnings fit together.

Also be aware that the reported IP addresses in a traceroute are for guidance purposes only It is entirely possible there are things messing with the ICMP (or equivalent) packet TTLs causing duplicates masking real IP addresses - but you would need to communicate with your ISP if those are a concern.

HTTPS is cachable - although the word cachable is vague. Relatedly large content providers often will deploy equipment to ISPs to distribute and cache content. Typically the content provider will provide equipment to do caching including appropriate certificates so https does not fail, and work with the ISP to ensure traffic is appropriately routed to the caching bix in the ISP network.