This is the observation made by some Freebox subscribers, their IP and the reverse DNS have been modified by Free But why such a change?and why some remote access no longer work?This is what we will try to see in this tutorial.◊ Why this change of IP ◊ Why shared IP ◊ What consequences and what solutions.◊ How to modify the remote access ports taking into account the new parameters.Free fiber optic access, as well as the new Free IPv6 DSLAMs on Freebox connections have points in common.What are these specificities and the consequences on the subscription.A shared IPv4 specificity common to these 2 very different accesses.Fiber optic access and ADSL access.1st subscriber: Port 0 to 16383 -- 2nd subscriber: Port 16384 to 32767 -- 3rd subscriber Port 32768 to 49151 -- 4th subscriber: Port 49152 to 65535Please respect Netiquette and do NOT copy on other websites (except of course, if prior authorization) publications and images from the Busyspider Images & Montage site © www.busyspider.fr Thank you for your understanding.For information: The documents are updated regularly on the original site (texts and images/Tag with the Busyspider logo) Registered on other sites, updating is impossible, which would be harmful to the reliability of the information published.Ps: It is of course always possible to quote a source, a url link to take up information on another website.A new wave of updates is underway (October 2019) on some network and Freebox equipment in IPv6 with the allocation of a new shared access IP address for the Freebox connection concerned.Already initialized on numerous accesses, in particular on new ADSL accesses following migration from NRA-MED, but also on fiber optic accesses, Free is diligently pursuing its deployment in IPv6 on its entire fixed network.For most accesses, the subscriber will see no difference or inconvenience.Some more geeky accesses, we can therefore see on the self-help forums of the participants coming to ask for explanations on this change of IP and its consequences.We will see below, what are the changes and the consequences.What are the visible changes?■ The first observation is the new IP different from the one before, but still in fixed IP.The reverse DNS of the IP was in this form before: xx.xx.xxx.fbx.proxad.net It is now of this type: xx.xx.xxx.subs.proxad.net Or like this: jyr87-1_migr -xx-xxx-xxx-xx.fbx.proxad.net■ The 2nd less visible change is the shared IPFor the new Dslam IPv6 and fiber optic connection (ZTD in PON, ZMD and RIP this will induce new features in particular a new IP will be assigned to the connection. This IP will be shared between 4 users, with for each of them 1/4 ports. On a day-to-day basis, most users will also have no problem. IP shared between 4 Freebox clients with, for each of them, 1/4 of the ports allocated to this connection. But rest assured, each remains independent, and not visible to others.To find out the range of ports that has been assigned to the connection, see this paragraph of the tutorial.■ Telephony temporarily unavailableFreebox telephony may temporarily be unavailable, the error can be found in Freebox OS: Telephony: Telephone service not configured This is not a failure, but related to the change, just wait at most a few hours to find active telephone service .Most of the time it comes back quickly, without doing anything, otherwise a restart of the Freebox could accelerate the return.(No need to ask for an IP-full-stack for this, rebooting, restarting the Freebox if necessary will be beneficial)■ The consequences of this shared IP may require small adjustments in terms of remote accessAnother visible effect, if you have set up remote access on Freebox OS for your HTTPS secure custom domain and for Freebox Compagnon: If the port used for this remote access is no longer within the authorized port range, this remote access won't work anymore, but a solution is easy to implement.It will then be necessary to update - redo the association - with Freebox Compagnon.To modify the ports of the remote access on the Freebox access, see this paragraph of the tutorial.■ MORE access to Free WifiAnother consequence that is a little more disabling for everyone, there is no longer Free Wifi access, .It's a listed bug, Free is well aware, it's in the process of being resolved.No need here to ask for a full-stack IP (with all ports) it will not solve the Free WiFi problem.Free Wifi Secure was restored following a Server update on April 15, 2019, (Secure only.) FreeWifi Secure provides automatic access from your smartphone with a Free Mobile subscription to the neighboring Freebox.See info on Convention Free 2017 Busyspider Web Report■ No longer possible to configure a third-party modemAnother disabling consequence: no longer possible to configure a third-party modem (other than the Freebox) no current modem is compatible with the IPv6 standard implemented by Free on its new equipment.Many testimonials mention it, in particular on the Univers Freebox forum and Fiber Info.The modem will be able to synchronize but will not be able to have Internet.And asking for a Full-Stack IP doesn't change anything, it won't work either!Source of information A paliative solution for experienced users, with corresponding link (Example of setting up a 4th tunnel: my internet access) is offered here on the lafibre.info forum.IPv6 DSLAM Migration■ Freebox bridge mode no longer worksAnother invalidating consequence: If router mode is deactivated, Internet access is no longer possible, Re-activation of router mode from Freebox OS or otherwise from the subscriber area (for a Freebox v5) restores access to the WEB .Asking for an IP-full stack does not solve the problem.Testimonials on the ADUF forum: Testimonial 1 on ADUF Testimonial 2 on ADUF Testimonial 3 on ADUFApril 16, 2019 Free Wifi Secure, restored following Server update on April 16, 2019 (Secure only) Freebox Server update (Revolution/Mini/Delta) 4.0.5 - Improvement: Freewifi Secure support in FTTH mode PON See details on Freebox news Free developer blogAccess Freebox OS http://mafreebox.freebox.fr/ Open the Freebox Status application Internet Status tab There is information on IPv4 and IPv6 with the allocation of the port range for the IPv4 IPv4: xxx xxx xx xx (Ports X to XXXXX)The information is also available on the Free subscriber console.Useful ... for Freebox V5 and Crystal subscribers (who do not have Freebox OS) https://subscribe.free.fr/login/ My Freebox tab / Display my IP address and the characteristics of my line.The IPv6 protocol is now active by default on all Freebox accesses.Those who have slightly more specific uses (Web server hosting for example) can request full-stack IPv4 if necessary.The request is to be made via his subscriber console.MAFreebox section - Advanced Features A new IPV4, with the full range of ports, will be assigned.The installation is almost immediate, you just have to restart the Freebox.Request possible from the Subscriber area Request a full-stack IPv4 If you are wondering what all this is for, it means that you don't have any use for it.It is therefore not useful to make changes, especially since the modification is irreversible (you cannot go back)Asking for a full-stack IP has nothing to do with throughput, it won't improve your throughput to ask for an IP with all ports. This is bad advice sometimes read on forums mutual aid.Do not give in to ease by asking for an IP-full stack, this does not solve all the problems, far from it.The shortage of IPv4 is real, we must not act to the detriment -future- of all.You can read on the Freebox Developers Blog during the April 15, 2019 update, these explanations on the Free network: Freebox News Free Developers Blog April 16, 2019: Freebox Server update (Revolution/Mini/Delta ) 4.0.5IPv6 is delivered today in the form of a tunnel (6RD) above IPv4 (known as native).Due to internal developments in our network, the system will gradually be reversed, and it is now IPv6 that will be native, and IPv4 delivered in the form of a tunnel.For this reason, disabling IPv6 completely on a Freebox amounts to potentially reducing network performance, so we are removing the possibility of disabling it globally.This function was introduced more than 10 years ago at the same time as the Freebox's IPv6 function, in order to avoid interoperability problems with the operating systems of the time.Note that it is always possible to disable IPv6 on the device* itself.As you will have understood, it is no longer possible to deactivate IPV6 from Freebox OS.* On the device, understand your PC.Following Free's decision to activate IPv6 by default on the Freebox network, the need for a firewall was mentioned by many sites and forums.The request was therefore made during the Free Convention in May 2019 and it was with an immediately positive response that this wish was accepted.A firmware update of June 4 version 4.0.6 enabled this functionality.If necessary restart your Freebox.Read details on this Web News of Busyspider Freebox Firmware Update Wishes Convention Free.Setting up an IPv6 firewall To activate this firewall, go to Freebox OS - Freebox settings http://mafreebox.freebox.fr/ ► Freebox settings - IPv6 configuration.Check the box "Enable the IPv6 firewall" select OK - Then apply.The remote access that you had set up on Freebox OS, for example for file sharing or for Freebox Compagnon (remote access to the Freebox) may no longer work, if the original ports are no longer found in the assigned port range.An easy solution exists and will allow you to quickly restore this remote access.Go to Freebox OS version not secure for the moment http://mafreebox.freebox.fr/ ► Parameters of the Freebox - Configuration.Then modify the remote ports, ensuring that they are within the range of authorized ports.Apply, OK.You will be asked for confirmation for the modification.Modification taken into account immediately.The access port for Freebox OS in TLS version (secure) is changed in stride.Don't forget then to modify the HTTPS access link, if you have set up secure access, with the new port.You can now log in to the personalized, secure domain.Example: https://domaineperso.freeboxos.fr:30548/This sometimes transient situation can occur when Free unbundles the zone or when setting up an NRA-MeD (NRA for Increase in Speed) and in this case, Free has not always set up the unbundling at the start, it can intervene later.In the meantime, the Freebox connection is connected in a non-unbundled zone to the Orange DSLAM equipment in the Dispatcher (Telephone exchange)FreePON ... To participate FreePON: Geographic tracking of deployments with native IPv6 architecture ... To learn moreSincerely... Contact me if necessary on the Busyspider Web Twitter accountPlease respect Netiquette and do NOT copy on other websites (except of course, if prior authorization) publications and images from the Busyspider Images & Montage site © www.busyspider.fr Thank you for your understanding.For information: The documents are updated regularly on the original site (texts and images/Tag with the Busyspider logo) Registered on other sites, updating is impossible, which would be harmful to the reliability of the information published.Ps: It is of course always possible to cite a source, a url link, to use information on another website.LEGAL MENTIONS Help topics created by © Busyspider Legal framework of the [Intellectual property of the works] No copy/paste - even partial is authorized, including the © Images © Busyspider of the tutorials.To refer to a subject, news, tutorial of the site, insert only the corresponding url link, thank you.ABOUT ABOUT the SITE Follow NEWS and current events Site MAP Menu haut HOMENO EMAIL SUPPORT Register on a support forum for your questions.Free users' forum CONFIDENTIALITY-COOKIES MANAGEMENT The statistics of this site require the use of cookies in order to improve individual assistance.The data is in no way used for any other purpose, nor transmitted to anyone.See according to your browser, the options to modify, if you do not wish to authorize their use.independent site -- no ads