Here we go again. Same machine and same issue. Local domain 10.*.*.* is on the local modem on all modems. That is the facts. I didn't get lucky with a 10. domain. I used to have 192 years ago and saw it pop up on something. Old Sun. Now recycled. Set top boxes have local connection to the router so local web and phone connections can tell what food, what song, what the baby or temp sensor, watch or what-not is providing. Please stop fighting us and open up 10.

Timing out is a lame excuse. This tower is hardwire to the same Linksys router that my B2 is attached using one of the 50 'local' internet attachments. My Cell phone is connected to the router as well as is the TV, set top box, etc. You are blocking a Raspberry Pi computer within the B2. You can not expect every IOT device to have a registered domain. Internal ones on the routers use numbers. My phone attaches to the guest account. But that is part of the list of 50 this router has to hand out. I know places that the router needs rebooting to flush the local connections (most or all had left (cell phones in the pockets of a large meeting)). Then the next meeting can have internet connection. That is the life of a router. Finite numbers to dole out. 10.xx.xx.xx is the router in this Building. In the house there are two more.

If this is a hardware issue then you need to contact the hardware manufacturer support.

It is your software. Was last time and is this time. Every other fix of Firefox you kill my IOT machine 10.xxx.xxx.xxx is a local modem less than a foot from me and you TIME OUT getting to it. The CAT 6 cable from my tower to the router is short. No time to get to 10.xxx Since the IOT comes from the antenna of that router. It is your software that kills the access. You just installed a new version on us and you killed what I was using. The web page is part of my specific home page. One in Germany and the other in the Pi machine feet away. Your DNS table disallows it on lookup. My Raspberry Pi playing hundreds of my CD's isn't a VILE dangerous black web site. It is in my home and is valid. Look at the previous posts. Same old story.

Martin357 said

It is your software.

AFAIK, Mozilla hasn't released an official build of Firefox for the RaspberryPi. From what I have read the RaspberryPi version of Firefox is a Debian-build that uses the Firefox source code which is open source and anyone can build their own version from the source code.

That may be why no one here has answered this thread in 4 months. Perhaps the best place to ask about that is a Linux support fora. http://ubuntuforums.org/

You don't understand. Read all of these. The Brennan B2 is a CD box that that software has the java and website that when asked it presents the display of all of my CD's and the contents on my browser on my Tower. The Tower is running System 7 Ultimate. The FireFox is this tool and runs on this local tower. When I enter HOME (press the icon) or start a new tool my home pages are my Solar array and another tab has my B2 website. That website is in the other room, the domain is in the router a few inches away. I never said Mozilla made a Raspberry Pi version - the web page is located at http://10.224.219.149/# which is on the third deep from the 50meg internet provided. That is, Modem, router1, router2 and this router 3 in this estate. The IOT box with the simple software is listed at that on my Router. My router has 10.224.219.100 to 219.149. The B2 takes the last available from the router pool. Other pull from the front of the pool. NOW follow this : B2 www.brennan.co.uk Yes a UK site. Sold on Amazon. look at pictures and see the box. Your DNS table is likely the issue if not in your see since timeout and the funny animal is impossible between this computer and the router to the set top box that fetches that number every time it boots. It is your implementation of this protective code.

Sorry, your explanation is very confusing.

Martin357 said

... The Tower is running System 7 Ultimate. The FireFox is this tool and runs on this local tower. ...

Are you saying that the Tower is running Windows 7 Ultimate and Firefox 65 does not connect to the peripheral devices on your Local Area Network (LAN) that have Class A unicast IP Addresses that start with 10.x.x.x?

Martin357 said

It is your software. ... It is your software...

You seem to be under the impression that this is either a ticketing system in contact with Mozilla people or that the people who have responded on this forum thread work for Mozilla.

The is a community support forum and this section is for things in relation to the desktop Firefox web browser.

YOUR DNS look up table blacklists 10.* sites. 10.* sites are INTERNAL to a location and you can't ping/spray/etc the site because it is out of your area. I worked just fine until I got this new version of Firefox downloaded and installed. - Not my idea.

You are in league with MS on killing black listed sites. Sites within and deep within a house are not black sites. It is your DNS look up table that you run and see and then timeout. Timing out is IMPOSSIBLE it is nano seconds away. Now look at all of this list.

As of this morning, I can still access http://10.10.*.*/ sites on an internal business network in Firefox 65.0.2, both by IP address and by hostname. There is not a built-in block on that range of addresses.

Please re-read our discussion in your earlier thread here:

Why are you blocking our Music players that use number addresses

The screenshot you posted in the last reply shows a notch on the Control Center 'i' icon indicating you made changes to some settings.

• /questions/1205115?page=3#answer-1090455

Do you remember what permission changes were made in that old Firefox version?

I was editing and looking at my music when you downloaded this browser. You had a flag up and when I looked at it it stated to exit and restart to install new. The link on my desktop was the installer, not the old (last version) version. Every since MS has been killing sites this has been an issue with the DNS service and other catching software. I have had it Fixed twice. This isn't the first rodeo for me. I have been using FF, Mozilla, Netscape etc. Since I downloaded it from Cern. The software developed in Batavia Ill. So this basic form of software has been on my Sun 3 , Sun 4 and many PC's since. I'm 72 and have had a PC on my desk since 75 with letter quality printer. I started and still have my teletype 33 but had a 32 first. I don't believe you have a 10.10 site unless it is on a router inside. I can't since this was installed. You are purging to much on install. This has been my home page for several years. look on the whole thread. I've downloaded a new web design from England and rebooted the B2 and this still won't work. Now I'll have to Reboot this computer and hope it still functions with the software I have. One never knows what MS has up their sleeves. Someone purged the DNS table that we look at. Not on purpose but made to. Or there is a function within that gives" Problem loading page" on the tab and TIME OUT in the middle splash with the zilla upset to the timeout in the lower left. I can easily get out but this is inside this room. The laptop is on the wireless and works this tower is on wire and works the B2 is wireless and connects to the router inches away but this version of FF will not get to the router. It will on all other sites in Germany and Amazon. Brennan in the UK is ok. But to a 10.xx on a persons not a developer that builds a version not installs the version. That is the issue - our systems and processes are different. I can ping 10.224.219.149 send 4 packets, get 4 packets. And is yours a PC and installed from the web ? or development build ? I am a retired Sr. Scientist and have worked with SINET in it's early years. Martin

I fixed it by Rebooting my modem after getting a new browser. That is lame. I know old information on it maybe but there is something else inside the code that is wrong. If I have to reboot the router , computer, and the IOT box and start all over on all three when I get an upgrade from prior version of FF to this 65 version there is a fundamental code issue. IT departments don't like to reboot and neither do customers rebooting everything in the room because you updated. Is it that anything on 64.*.* is considered trash and not trusted or owned ? And I purge it ? What did I purge when I rebooted the modem ? Think of that.