Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Subnet public rutat print-run IP public

    Scheduled Pinned Locked Moved Romanian
    16 Posts 3 Posters 7.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      vasilenicusor
      last edited by

      Hmm, la Pfsense nu ar trebui XXX.YYY.173.25 in loc de XXX.YYY.173.24 , .24 fiind ip-ul de retea ?

      1 Reply Last reply Reply Quote 0
      • C
        catalin
        last edited by

        ba da , greseala de redactare :)

        luam ca exemplu clasa 86.122.173.24/29

        IP Address: 86.122.173.24
        Netmask: 255.255.255.248
        Wildcard Mask: 0.0.0.7
        CIDR Notation: /29
        Network Address: 86.122.173.24
        Usable Host Range: 86.122.173.25 - 86.122.173.30
        Broadcast Address: 86.122.173.31
        Binary Netmask: 11111111.11111111.11111111.11111000
        Total number of hosts: 8
        Number of usable hosts: 6
        IP Class: A (0.0.0.0 - 127.255.255.255)

        Adevarul se afla dincolo de noi …

        1 Reply Last reply Reply Quote 0
        • V
          vasilenicusor
          last edited by

          Am reusit, totul merge ok, dar in internet tot pe ip-ul principal imi ies hosturile dupa pfsense, ar trebui sa ies pe ip-ul din subnet. Ma poti ajuta cu o configurare?

          1 Reply Last reply Reply Quote 0
          • C
            catalin
            last edited by

            trebe setata ruta de XXX.XXX.173.24/29 in pfsense pe wan

            Adevarul se afla dincolo de noi …

            1 Reply Last reply Reply Quote 0
            • V
              vasilenicusor
              last edited by

              iarta-ma dar astazi e prima ora cand iau contact cu pfsense. am citit prin manual dar nu ma prind unde sa o pun :(

              1 Reply Last reply Reply Quote 0
              • C
                catalin
                last edited by

                nu am un pfsense la indemana sa iti arat , ai teamviewer  ?

                Adevarul se afla dincolo de noi …

                1 Reply Last reply Reply Quote 0
                • V
                  vasilenicusor
                  last edited by

                  ai PM . Merci

                  1 Reply Last reply Reply Quote 0
                  • A
                    AMizil
                    last edited by

                    Salutari

                    Pana la urma cum a iesit? Puneti si voi un print screen de la Routing si interfaces?

                    Adrian

                    1 Reply Last reply Reply Quote 0
                    • V
                      vasilenicusor
                      last edited by

                      momentan nimic. inca nu am reusit sa-l fac sa pot iesi pe net cu ipu-rile respective, tot ip-ul principal e folosit - se comporta ca un router obisnuit ce face NAT. Momentan nu pot pune printscreen-uri ca nu am acces direct la server , iar remote nu mai pot face , maine poate reusesc sa ajung. Intre timp am contactat si RDS-ul si …. cica ma cauta maine :))) interesant

                      1 Reply Last reply Reply Quote 0
                      • C
                        catalin
                        last edited by

                        am nevoie de un traceroute catre 8.8.8.8 de pe o masina din spatele routerului cu ip extern

                        Adevarul se afla dincolo de noi …

                        1 Reply Last reply Reply Quote 0
                        • V
                          vasilenicusor
                          last edited by

                          Salut,

                          Asta e cu NATUL activat (vezi Reguli_autogenerate.png)

                          C:>tracert 8.8.8.8

                          Tracing route to google-public-dns-a.google.com [8.8.8.8]
                          over a maximum of 30 hops:

                          1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [81.196.173.25]
                            2    2 ms    2 ms    1 ms  dr00.sibiu.rdsnet.ro [213.154.106.228]
                            3    7 ms    6 ms    7 ms  qr17.rdsnet.ro [213.154.124.44]
                            4    6 ms    8 ms    5 ms  qr07.rdsnet.ro [213.154.124.158]
                            5    6 ms    6 ms    6 ms  213-154-124-65.rdsnet.ro [213.154.124.65]
                            6    10 ms    11 ms    10 ms  xr01.budapesta.rdsnet.ro [213.154.128.1]
                            7    11 ms    9 ms    9 ms  213-154-130-234.rdsnet.ro [213.154.130.234]
                            8    10 ms    9 ms    10 ms  209.85.250.79
                            9    9 ms    9 ms    9 ms  google-public-dns-a.google.com [8.8.8.8]

                          Trace complete.

                          Aici e traceroutu cu regulile custom (vezi Reguli_custom.png)

                          C:>tracert 8.8.8.8

                          Tracing route to google-public-dns-a.google.com [8.8.8.8]
                          over a maximum of 30 hops:

                          1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [81.196.173.25]
                            2    1 ms    1 ms    <1 ms  dr00.sibiu.rdsnet.ro [213.154.106.228]
                            3    7 ms    6 ms    7 ms  qr17.rdsnet.ro [213.154.124.44]
                            4    6 ms    6 ms    6 ms  qr07.rdsnet.ro [213.154.124.158]
                            5    *        *        *    Request timed out.
                            6    *        *        *    Request timed out.
                            7    *        *        *    Request timed out.
                            8    *        *        *    Request timed out.
                            9    *        *    ^C

                          Reguli_autogenerate.PNG
                          Reguli_autogenerate.PNG_thumb
                          Reguli_custom.PNG
                          Reguli_custom.PNG_thumb

                          1 Reply Last reply Reply Quote 0
                          • V
                            vasilenicusor
                            last edited by

                            Sa rezolvat prin setarea Gateway-ului la LAN in pfSense IP-ul principal si NAT activat cu regulile implicite

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.