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

    Changed my pfsense for a 2.1.4 from 2.0.3 now routing not working

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 650 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.
    • W
      wookiefw
      last edited by

      I was wondering if anyone can point me in the right direction..

      I installed a new box to replace my old 2.0.3 box.  the old one was working fine this new one is not..  here is what is going on

      I have a /30  111.111.111.86/30  on WAN

      I have a block assigned to me  222.222.222.0/26  and LAN  as 222.222.222.1/26

      I have a private network 10.1.1.0/24 on OPT1  and OPT1 is 10.1.1.1/24

      I can forwars my bock ips to  the OPT1 net fine.. but I cannot reach the LAN network hosts… also LAN network cannot ping outside its own net and cannot ping the 222.222.222.1 host.  they are connected properly and I can ping each host internally just fine form other 222.222.222.0 hosts

      What I did so far..

      I disabled autmatic outbound nat

      I went to disable nat relefection but in 2.1.4 its a check to ENABLE.. so left it unchecked.

      I create any any any rule on LAN, WAN and OPT1 to test

      I can ping world from 10.1.1.1
      I can ping 222.222.222.1  from 10.1.1.1 or internet
      I can forward  222.222.222.44 (forexample) to 10.1.1.44 and it works

      I am new to 2.1.4 so not sure what I missed

      routes are

      default 111.111.111.85 UGS 0 3661428 1500 fxp0
      10.1.1.0/24 link#4 U 0 3233402 1500 em1
      10.1.1.1 link#4 UHS 0 1 16384 lo0
      111.111.111.84/30 link#1 U 0 440880 1500 fxp0
      111.111.111.86 link#1 UHS 0 0 16384 lo0
      222.222.222.0/26 link#3 U 0 492982 1500 em0
      222.222.222.1 link#3 UHS 0 6 16384 lo0
      127.0.0.1 link#7 UH 0 82 16384 lo0

      interaces

      WAN interface (fxp0)
      Status up
      MAC address 00:02:b3:9e:ff:47
      IPv4 address 111.111.111.86
      Subnet mask IPv4 255.255.255.252
      Gateway IPv4 GW_WAN 111.111.111.85
      IPv6 Link Local fe80::202:b3ff:fe9e:ff47%fxp0
      ISP DNS servers 127.0.0.1
      208.67.222.222
      208.67.220.220
      Media 100baseTX <full-duplex>In/out packets 4195155/4099778 (2.11 GB/3.12 GB)
      In/out packets (pass) 4195155/4099778 (2.11 GB/3.12 GB)
      In/out packets (block) 22749/11 (2.52 MB/748 bytes)
      In/out errors 0/0
      Collisions 0

      LAN interface (em0)
      Status up
      MAC address 00:30:48:8c:57:cc
      IPv4 address 222.222.222.1
      Subnet mask IPv4 255.255.255.192
      IPv6 Link Local fe80::230:48ff:fe8c:57cc%em0
      Media 100baseTX <full-duplex>In/out packets 226514/490528 (191.48 MB/218.79 MB)
      In/out packets (pass) 226514/490528 (191.48 MB/218.79 MB)
      In/out packets (block) 2/67568 (80 bytes/6.19 MB)
      In/out errors 0/0
      Collisions 0

      OPT1 interface (em1)
      Status up
      MAC address 00:30:48:8c:57:cd
      IPv4 address 10.1.1.1
      Subnet mask IPv4 255.255.255.0
      IPv6 Link Local fe80::230:48ff:fe8c:57cd%em1
      Media 100baseTX <full-duplex>In/out packets 3281622/3234331 (2.89 GB/1.88 GB)
      In/out packets (pass) 3281622/3234331 (2.89 GB/1.88 GB)
      In/out packets (block) 126/0 (10 KB/0 bytes)
      In/out errors 0/0
      Collisions 0</full-duplex></full-duplex></full-duplex>

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