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

    Routing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 3 Posters 1.0k 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.
    • G Offline
      goldengate
      last edited by

      Hi! I have a little problem, and need some advice, this is my network:

      WAN DHCP
          |
          |
      pfSense – netA 192.168.90.10/24 -- SWITCH -- Clients and one server in 192.168.90.X/24
          |
          |
      netB 192.168.3.7/24
          |
          |
      Switch -- Clients 192.168.3.X/24 Default GW for clients 192.168.3.10
          |
          |
      Linux Server 192.168.3.10
          |
          |
      WAN - DHCP

      And I need to route some my clients in 192.168.3.X to one server in 192.168.90.50

      In the Linux server I did this:  route add -net 192.168.90.0 netmask 255.255.255.0 gw 192.168.3.7

      And when I do a traceroute

      C:\Users\saruman>tracert 192.168.90.15

      Traza a 192.168.90.15 sobre caminos de 30 saltos como máximo.

      1    <1 ms    <1 ms    <1 ms  MORIA [192.168.3.10]
        2    <1 ms    <1 ms    <1 ms  192.168.3.7
        3    1 ms    <1 ms    <1 ms  192.168.90.50

      I need to make the same command in the pfsense side, but I'm lost!

      Best regards,

      Frank

      1 Reply Last reply Reply Quote 0
      • KOMK Offline
        KOM
        last edited by

        https://doc.pfsense.org/index.php/Static_Routes

        1 Reply Last reply Reply Quote 0
        • H Offline
          heper
          last edited by

          I need to make the same command in the pfsense side, but I'm lost!

          Best regards,

          why would you need to do the same on the pfsense side? pfsense already has a route to the 192.168.3.X/24 subnet, because it has an interface on it.

          1 Reply Last reply Reply Quote 0
          • G Offline
            goldengate
            last edited by

            Thanks KOM, but I did my homework and read that article from PFSenseDocs…  :P

            Heper, its because this:

            PING 192.168.3.10 (192.168.3.10) from 192.168.90.10: 56 data bytes

            --- 192.168.3.10 ping statistics ---
            3 packets transmitted, 0 packets received, 100.0% packet loss

            This is from the pfsense box  ;) as you can see, I can't reach the Linux box, I'm doing this setting the ping command from the source address 192.168.90.10  I think that I'm missing something but I'm not seeing it! :(

            Thanks you two for your comments!

            Frank

            1 Reply Last reply Reply Quote 0
            • H Offline
              heper
              last edited by

              firewall rules perhaps? do you allow from the .90.x ==> 3.x ?

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