NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Sylvester2999's avatar
Nov 15, 2017
Solved

R7800 configuration Freebox & Nas syno sur 2 reseaux

Bonjour                                                                                         ,

 

 

Est-il possible d’acceder à un Nas Synology sur 2 reseaux ?

Le reseau 192.168.0.x pour serveur multimedia à la Freebox

Le reseau 192.168.1.x pour serveur de fichier pour les différents terminaux wifi ou filaire

 

Le Nas Synology n’a qu’un adaptateur réseau.

Extention prévue : un 2eme Nas & un disque externe reseau

Le reseau actuel fonctionne correctement.

 

Ma configuration :

Freebox V6

mode routeur (pour garder la fonctionnalité serveur multimedia),

DHCP ON

Adresse IP statique du Routeur R7800 : 192.168.0.2

passerelle : 192.168.0.254

reliée au

Routeur R7800,

mode routeur

adresse IP statique : 192.168.0.2

Adresse IP de la passerelle : 192.168.0.254

 

Paramétrage TCP/IP du LAN

Adresse IP : 192.168.1.1

Masque 255.255.255.0

DHCP ON

Plage 192.168.1.2 à 192.168.1.254

Avec réservation d’adresse

 

Relié au

Switch DLINK DGS-1216T (manageable)

 

Terminaux reliés En filaire au Switch :

3 PC W10

Imprimante

Consoles jeux,

Photo

Serveur domotique

+……….

 

Terminaux reliés En WIFI sur R7800 :

Tablettes

Mobiles,

Répéteur wifi

ChromeCast

App Photo

+………….

 

Merci pour vos réponses

Cordialement

  • antinode's avatar
    antinode
    Nov 16, 2017

    > Je n'ai rien modifié dans la configuration de R7800

       That is expected.  The R7800 does not need any new information.
    Any message to a foreign subnet gets sent out through its WAN port.

    > Je n'ai RIEN ajouté dans les redirections de la Freebox

       Ah, yes.  If the connection is made by a client on the R7800 LAN,
    then NAT (on the R7800) may do everything you need.  The Freebox will
    see a connection coming from the R7800 WAN interface (192.168.0.2).  It
    will reply to that, and NAT on the R7800 will pass the reply to the real
    client on the R7800 LAN.

       If the connection is to be made by a client on the Freebox LAN,
    _then_ the Freebox will need a static route to the R7800 LAN. 
    (Otherwise it would send the message to your ISP.)

       So, in one direction (R7800 -> Freebox), NAT solves the problem.  In
    the other direction (Freebox -> R7800), the route is required.  Sorry

    for the (my) confusion.

6 Replies

  •    If Google reads your French correctly, and if I understand your
    network, then ...

       The Synology NAS is on the 192.168.0.x (Freebox LAN) subnet.  Let's
    say the NAS is at 192.168.0.N.

       The R7800 LAN is the 192.168.1.x subnet.

       Let's say that there's a client on the R7800 LAN, at address
    192.168.1.C.  This client wants to send a message to the NAS (at
    192.168.0.N).  The client sees that the NAS is on a different subnet
    (192.168.0.x, not 192.168.1.x), so it sends the message to its default
    gateway, the R7800.  The R7800 also sees that the NAS (192.168.0.N) is
    on a different subnet, so it passes the message to its default gateway,
    the Freebox.  The Freebox knows that 192.168.0.N is on its LAN, so it
    delivers the message to the NAS.

       Now, the NAS will have a reply for the client (at 192.168.1.C, on the
    R7800 LAN), which is not on its own subnet, so it sends the reply to its
    default gateway, the Freebox.  The Freebox must pass the reply to the
    R7800, but how does it know that?  Normally, it sends foreign messages
    to your ISP.  You can tell the Freebox to pass such a message to the
    R7800 by defining a static route (on the Freebox):

          Destination: 192.168.1.0   \ (the R7800 subnet...)
          Subnet: 255.255.255.0     /
          Gateway: 192.168.0.2        (the R7800 WAN address)
          Metric: <anything>

       Then, each router knows how to find the subnet of the other router,
    and clients on either subnet can get messages to and from clients on the
    other subnet.

    • Sylvester2999's avatar
      Sylvester2999
      Aspirant

      Merci  Antinode pour la réponse,

      (Goggle, traduction moi aussi,

      je pense avoir compris !!!!)

      Je vérifie et teste dans la journée

      et je répond (dans la soirée)

       

    • Sylvester2999's avatar
      Sylvester2999
      Aspirant
      I do not know if goggle to properly translated?
      I have an incorrect translation return

      Thanks Antinode for the answer,
      (Goggles, translation me too,
      I think I have understood!!!!)
      I check and test in the day
      And I answer (in the evening)
       
       
       
    • Sylvester2999's avatar
      Sylvester2999
      Aspirant

      Essai :

       

      J’ai branché le NAS directement sur la freebox

      IP : 192.168.0.10

       

      Je n’ai rien modifié dans la configuration de R7800

      Je n’ai RIEN ajouté dans les redirections de la Freebox

       

      • Sur la TV avec le FreePlayer, le NAS apparait bien comme serveur multimedia : Ce qui est normal.

       

      • Sur 1 PC en Windows 10

      Dans l’Explorateur windows ,  saisie : \\192.168.0.10 et je peux acceder à n’importe quel dossier du NAS !!!

       

      Dans EDGE,  saisie : IP+port du NAS et affichage correct

       

      Je n’ai rien trouvé dans ROUTERLOGIN.NET du R7800 qui m’indique ce qu’il a vu passer ?

       A votre avis, a partir des demandes par l’explorateur windows 10, quel est le chemin ?

       

      Sinon, mon problème est résolu

       

      Test:

       

      I plugged the NAS directly on the Freebox

      IP: 192.168.0.10

       

      I have not changed anything in the configuration of R7800

      I have not added anything in the redirections of the Freebox

       

      -On TV with the FreePlayer, the NAS appears as a multimedia server: which is normal..

       

      -On 1 PC in Windows 10

      In Windows Explorer, enter: \ 192.168.0.10 and I can access any folder of the NAS!!!

       

      In EDGE, typing: IP + NAS port and correct display

       

      I found nothing in ROUTERLOGIN.NET of the R7800 that tells me what he saw passing?

       

      In your opinion, from the requests by Windows Explorer 10, what is the path?

       

      Otherwise my problem is solved

       

      • antinode's avatar
        antinode
        Guru

        > Je n'ai rien modifié dans la configuration de R7800

           That is expected.  The R7800 does not need any new information.
        Any message to a foreign subnet gets sent out through its WAN port.

        > Je n'ai RIEN ajouté dans les redirections de la Freebox

           Ah, yes.  If the connection is made by a client on the R7800 LAN,
        then NAT (on the R7800) may do everything you need.  The Freebox will
        see a connection coming from the R7800 WAN interface (192.168.0.2).  It
        will reply to that, and NAT on the R7800 will pass the reply to the real
        client on the R7800 LAN.

           If the connection is to be made by a client on the Freebox LAN,
        _then_ the Freebox will need a static route to the R7800 LAN. 
        (Otherwise it would send the message to your ISP.)

           So, in one direction (R7800 -> Freebox), NAT solves the problem.  In
        the other direction (Freebox -> R7800), the route is required.  Sorry

        for the (my) confusion.