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

Routing through non-WAN interface

Scheduled Pinned Locked Moved Routing and Multi WAN
2 Posts 1 Posters 1.2k 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.
  • B
    Blackmag
    last edited by Jan 6, 2012, 6:08 PM Jan 6, 2012, 4:59 PM

    Hi Everybody,

    First of all Happy new year for those who celebrated!

    Now to the topic. I use VM appliance of pfsenese with version: 1.2.3-RELEASE.
    I have 3 interfaces - WAN, LAN and OPT1, addressed respectively in this way:
    em0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
           inet 5.5.7.243 netmask 0xfffffff0 broadcast 5.5.7.255
    em1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
           inet 5.5.6.93 netmask 0xffffffe0 broadcast 5.5.6.95
    em2: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
           inet 192.168.255.3 netmask 0xffffff00 broadcast 192.168.255.255

    The important part of the routing table looks like this:

    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            5.5.7.241          UGS         0    19890    em0
    5.5.6.64/27        link#2             UC          0        0    em1
    5.5.6.92           00:50:56:b7:00:64  UHLW        1      624    em1   1154
    5.5.7.240/28       link#1             UC          0        0    em0
    5.5.7.241          00:25:45:38:79:d7  UHLW        2      844    em0    557
    192.168.0.0/24     192.168.255.1      UGS         0       89    em2
    192.168.10.0/24    192.168.255.2      UGS         0        0    em2
    192.168.255.0/24   link#3             UC          0        0    em2
    192.168.255.1      00:0c:42:2e:c8:6d  UHLW        2        0    em2    515
    192.168.255.2      link#3             UHLW        2        0    em2

    So what is important for me is to reach 192.168.0.0/24 and 192.168.10.0/24 through the OPT1 interface and not through the WAN. That's why I gave static routes. And those networks are reachable from the pfsense machine itself, but NOT through the LAN network, connected behind the LAN (em1) interface.

    On the other hand, all destinations, the LAN network needs to reach through the default route are reached successfully.

    Can somebody help me by telling me how shall I make the requests from the LAN, destined to the 192.168.x.x static routes to work?

    Thanks in advance!

    Regards,
    Ivan</up,broadcast,running,simplex,multicast></up,broadcast,running,simplex,multicast></up,broadcast,running,simplex,multicast>

    1 Reply Last reply Reply Quote 0
    • B
      Blackmag
      last edited by Jan 7, 2012, 4:50 PM

      SOLVED!

      The 'Gateway' field should be filled in the Interfaces->OPT1 configuration section. Then just add WAN and OPT1 interfaces in Load Balancing mode (Services menu). Thus, all incomming packets on the LAN interface also obey the defined static routes.

      Cheers!

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received