B-Box, DMZ Issue, NAT or Misconfiguration?
Deadlift
Posted messages
5
Status
Member
-
phil2k Posted messages 10841 Registration date Status Contributor Last intervention -
phil2k Posted messages 10841 Registration date Status Contributor Last intervention -
Hello everyone,
I'm posting my message here hoping you understand my problem.
I'll explain, this procedure is done from my server locally.
So I comment, I open my webpage. I connect to my webpage at 127.0.0.1 (Local address) no issues + Ping (No issues).
Now, I access 192.168.1.183 from my browser, no issues + ping)
Up to this point, no issues. Now I enter my public address in the browser, 31.XX.XXX.XXX. Nothing happens (it used to work perfectly well for over a year!...) But I can ping my own public address (31.XX.XXX.XXX) WTF?..
Well, I'm on B-BOX version 2.0. (I didn't pay attention to the version, it changed by itself.)
Basically, I've reset my box several times. Hardware + Software... Firewall disabled... Anyway, nothing...
Any suggestions? I'm lost...
I'm posting my message here hoping you understand my problem.
I'll explain, this procedure is done from my server locally.
So I comment, I open my webpage. I connect to my webpage at 127.0.0.1 (Local address) no issues + Ping (No issues).
Now, I access 192.168.1.183 from my browser, no issues + ping)
Up to this point, no issues. Now I enter my public address in the browser, 31.XX.XXX.XXX. Nothing happens (it used to work perfectly well for over a year!...) But I can ping my own public address (31.XX.XXX.XXX) WTF?..
Well, I'm on B-BOX version 2.0. (I didn't pay attention to the version, it changed by itself.)
Basically, I've reset my box several times. Hardware + Software... Firewall disabled... Anyway, nothing...
Any suggestions? I'm lost...
2 answers
-
Hello
Now I'm using my public address on the browser, 31.XX.XXX.XXX. Nothing is happening
It's normal, you cannot access your server with the public address...
(it worked very well for over a year now!...)
That's the most surprising part. It shouldn't be...
Try this:
http://validator.w3.org/
--
"To fix something that doesn't work or makes too much noise, all you need to do is hit it with something that works better or makes more noise" The Shadoks-
Hello, thank you for your response. But I have a BBOX Pro sensation. And coincidentally, for exactly 3 days I have this issue, and I found this online;
https://www.bbox-mag.fr/box/firmware/780-deploiement-du-firmware-9-2-38-pour-bbox-sensation-xdsl-et-ftth-sagem-3965b-modem-routeur/
A firmware update 3 days ago! Isn't that great?... It's impossible to downgrade the version. In short, I can't do anything, my systems won't work anymore (I'm not saying more).
The DMZ service doesn't work anymore, as well as NAT. Thank you Bouygues Telecom. I just have to contact them.
Thank you for your response, and if we can access the server with the public address locally to see its site for example. The magic of the DMZ service.
Have a nice day. -
-
-
-
-
-
Hello,
A little comment:
It's normal, you can't access your server with the public address...
This is called NAT Hairpinning, which is very commonly used, and some routers have it built-in (especially with the "DMZ" feature).
--
Using a registry "compactor" on top of a registry "cleaner" would be equivalent to rinsing your throat with a swig of Jack Daniels after swallowing a pint of snake oil....