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

    Interfaces LANs WS2012 + PfSense (Problema Resolvido)

    Scheduled Pinned Locked Moved Portuguese
    11 Posts 3 Posters 1.1k 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.
    • M
      mfelipeap
      last edited by

      Hello,

      I have Windows Server 2012 with AD with three LAN interfaces (192.168.1.1; 192.168.2.1; 192.168.3.1) integrated with PfSense (192.168.1.2). How do I configure 192.168.2.1 and 192.168.3.1 Interfaces for pfsense to view as LANs and they communicate?

      In ISA Server just put all the interfaces on the internal network, like I do in pfsense?

      1 Reply Last reply Reply Quote 0
      • P
        pskinfra
        last edited by

        @mfelipeap:

        Hello,

        I have Windows Server 2012 with AD with three LAN interfaces (192.168.1.1; 192.168.2.1; 192.168.3.1) integrated with PfSense (192.168.1.2). How do I configure 192.168.2.1 and 192.168.3.1 Interfaces for pfsense to view as LANs and they communicate?

        In ISA Server just put all the interfaces on the internal network, like I do in pfsense?

        Hi, mfelipeap.

        Just create interface on your pfsense, later configure IP host on network.  You need think in Model OS! Hugs  :)

        --
        E-mail: tleite@bsd.com.br
        Whatsapp: (021) 9 6403-5250

        1 Reply Last reply Reply Quote 0
        • M
          mfelipeap
          last edited by

          servidor dhcp, dns é WS2012!

          1 Reply Last reply Reply Quote 0
          • P
            pskinfra
            last edited by

            @mfelipeap:

            servidor dhcp, dns é WS2012!

            Para o PFSense servir o DHCP, ele terá que ser o gateway dos seus hosts!

            Link: https://forum.pfsense.org/index.php?topic=8930.0

            --
            E-mail: tleite@bsd.com.br
            Whatsapp: (021) 9 6403-5250

            1 Reply Last reply Reply Quote 0
            • M
              mfelipeap
              last edited by

              topologia não funcionaria nas interfaces x.x.3.1 e x.x.2.1? O que falta é distribuir internet com as condições de regras do pfsense. As interface não encontra o pfsenese.

              1 Reply Last reply Reply Quote 0
              • M
                mfelipeap
                last edited by

                https://www.dropbox.com/s/sku4a4mnyzc01jb/topologia_rede.jpg?dl=0

                1 Reply Last reply Reply Quote 0
                • P
                  pskinfra
                  last edited by

                  mfelipeap, explique melhor o que você quer fazer!

                  Se você quiser que o PFSense faça o DHCP das outras 2 redes, ele terá que ser o GW. Nesse caso, você terá que adicionar mais interfaces ( vlan ou lan ).

                  Abraços

                  --
                  E-mail: tleite@bsd.com.br
                  Whatsapp: (021) 9 6403-5250

                  1 Reply Last reply Reply Quote 0
                  • M
                    mfelipeap
                    last edited by

                    I have 3 Windows Server 2012 interfaces (DNS Server, DHCP and Active Directory):
                    LAN1 (active DHCP)
                    ip: 192.168.200.1
                    mask: 255.255.255.0
                    GW_Defatul 192.168.200.2
                    DNS P: 192.168.200.1

                    LAN2 (active DHCP)
                    ip: 192.168.201.1
                    mask: 255.255.255.0
                    GW_P:
                    DNS P: 192.168.201.1

                    LAN3 (active DHCP)
                    ip: 192.168.202.1
                    mask: 255.255.255.0
                    GW_P:
                    DNS P: 192.168.202.1

                    Pfsense
                    WAN: dhcp modem router

                    LAN: Static
                    ip: 192.168.200.2
                    mask: 255.255.255.0

                    The PfSense communication with LAN1 WS2012 is perfect, everything works! With the LAN2 and LAN3 interfaces do not. I believe in route problems.

                    Can you help me with details? Thank you…

                    1 Reply Last reply Reply Quote 0
                    • empbillyE
                      empbilly
                      last edited by

                      Porque estão postando em inglês no fórum "português" se os dois escrevem em português?  :o

                      mfelipeap,

                      Se tu quer comunicação entre a lan2, lan3 e o pfsense, ou tu faz como o pskinfra informou ou tu configura 2 rotas estaticas pra essas interfaces, pois o pfsense precisa conhecer essas redes, caso ele não conheça.

                      https://eliasmoraispereira.wordpress.com/

                      1 Reply Last reply Reply Quote 0
                      • M
                        mfelipeap
                        last edited by

                        estou criando a rota system > router

                        192.168.201.0/24 GW 192.168.200.2
                        192.168.202.0/24 GW 192.168.200.2

                        1 Reply Last reply Reply Quote 0
                        • M
                          mfelipeap
                          last edited by

                          Senhores,

                          Resolvi o problema… Eu não estava entendo porque o roteamento estático no pfsense não funcionava.

                          Seguinte estava tudo certo inclusive roteador do servidor AD, o problema é que uma chave de registro de roteamento estava negando o funcionamento do roteamento.

                          As rotas estáticas mencionadas que coloquei acabaram passando após alteração!

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