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

    Difference between Interface subnet and 192.168.2.0/24

    Firewalling
    5
    44
    11.4k
    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.
    • D
      doktornotor Banned
      last edited by

      Wasn't my question. Let me ask again:

      If you check the "Topology" checkbox, do both work (i.e., OPT3 subnet being the same as /24)?

      1 Reply Last reply Reply Quote 0
      • panzP
        panz
        last edited by

        @doktornotor:

        Wasn't my question. Let me ask again:

        If you check the "Topology" checkbox, do both work (i.e., OPT3 subnet being the same as /24)?

        There's only 1 (roadwarrior) client and it has 192.168.2.6 address.

        pfSense 2.3.2-RELEASE-p1 (amd64)
        motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          The question still remains the same. See the OpenVPN docs on net30 for the reason I'm asking.

          1 Reply Last reply Reply Quote 0
          • panzP
            panz
            last edited by

            Yes, now checking that, the first rule works… so... why?

            pfSense 2.3.2-RELEASE-p1 (amd64)
            motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              Well, because /30 is not /24  :P

              net30 – Use a point-to-point topology, by allocating one /30 subnet per client.
              subnet -- Use a subnet rather than a point-to-point topology by configuring the tun interface with a local IP address and subnet mask

              Documentation. Also comparing the ifconfig output for both modes should be pretty much enlightening.

              1 Reply Last reply Reply Quote 0
              • K
                kejianshi
                last edited by

                OK - So, your pfsense is a client to a vpn service and then your pfsense is also running an openvpn server to which your laptop/computer is a client while inside your own LAN?  Do I have this wrong?

                1 Reply Last reply Reply Quote 0
                • P
                  phil.davis
                  last edited by

                  Look in /tmp/rules.debug - down the end you will see the user rules generated from the Firewall Rules tabs. You will be able to see exactly what rules it generates for OPT3. I suspect it gets a different idea about OPT3 Subnet depending if it is set to topology or not. One way may treat it as a /30 and the other as the full tunnel network range.

                  As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                  If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                  1 Reply Last reply Reply Quote 0
                  • panzP
                    panz
                    last edited by

                    Oh, yes, I understand that. But my question was: why does OPT subnet and 192.168.2.0/24 was not the same?

                    I understand this IF topology is net30, so is a peer-to-peer like connection.

                    But the previous scheme was ALL /24. Why this doesn't work?

                    pfSense 2.3.2-RELEASE-p1 (amd64)
                    motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      @panz:

                      Oh, yes, I understand that. But my question was: why does OPT subnet and 192.168.2.0/24 was not the same?

                      Please, type ifconfig to console. For both modes. Compare the OPT3/ovpns? output.

                      1 Reply Last reply Reply Quote 0
                      • panzP
                        panz
                        last edited by

                        @kejianshi:

                        OK - So, your pfsense is a client to a vpn service and then your pfsense is also running an openvpn server to which your laptop/computer is a client while inside your own LAN?  Do I have this wrong?

                        laptop/computer is a client while I'm out (for eg. at a Strabucks coffee).

                        pfSense 2.3.2-RELEASE-p1 (amd64)
                        motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                        1 Reply Last reply Reply Quote 0
                        • K
                          kejianshi
                          last edited by

                          OK - I see.

                          When you VPN into your pfsense from your laptop when you are out does all that traffic then go out over the VPN pfsense is client too?

                          1 Reply Last reply Reply Quote 0
                          • panzP
                            panz
                            last edited by

                            @kejianshi:

                            OK - I see.

                            When you VPN into your pfsense from your laptop when you are out does all that traffic then go out over the VPN pfsense is client too?

                            Yes.

                            pfSense 2.3.2-RELEASE-p1 (amd64)
                            motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                            1 Reply Last reply Reply Quote 0
                            • K
                              kejianshi
                              last edited by

                              haha - I see where this is going…  Good one.

                              I take it AirVPN doesn't have a bandwidth usage cap?

                              1 Reply Last reply Reply Quote 0
                              • panzP
                                panz
                                last edited by

                                @doktornotor:

                                @panz:

                                Oh, yes, I understand that. But my question was: why does OPT subnet and 192.168.2.0/24 was not the same?

                                Please, type ifconfig to console. For both modes. Compare the OPT3/ovpns? output.

                                with net30

                                ovpns2: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                                options=80000 <linkstate>inet6 fe80::a00:27ff:fe7f:875d%ovpns2 prefixlen 64 scopeid 0x8
                                inet 192.168.2.1 –> 192.168.2.1 netmask 0xffffff00

                                without inet30

                                ovpns2: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                                options=80000 <linkstate>inet6 fe80::a00:27ff:fe7f:875d%ovpns2 prefixlen 64 scopeid 0x8
                                inet 192.168.2.1 --> 192.168.2.2 netmask 0xffffffff
                                nd6 options=3 <performnud,accept_rtadv>Opened by PID 15822</performnud,accept_rtadv></linkstate></up,pointopoint,running,multicast></linkstate></up,pointopoint,running,multicast>

                                pfSense 2.3.2-RELEASE-p1 (amd64)
                                motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                                1 Reply Last reply Reply Quote 0
                                • panzP
                                  panz
                                  last edited by

                                  @kejianshi:

                                  haha - I see where this is going…  Good one.

                                  I take it AirVPN doesn't have a bandwidth usage cap?

                                  no limitations as I know

                                  pfSense 2.3.2-RELEASE-p1 (amd64)
                                  motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    Yeah. So, see:

                                    netmask 0xffffffff = /32 (really just the OVPN IP itself, does not include any client, 192.168.2.6 certainly out)
                                    netmask 0xffffff00 = /24 (the configured subnet)

                                    1 Reply Last reply Reply Quote 0
                                    • panzP
                                      panz
                                      last edited by

                                      @doktornotor:

                                      Yeah. So, see:

                                      netmask 0xffffffff = /32 (really just the OVPN IP itself, does not include any client, 192.168.2.6 certainly out)
                                      netmask 0xffffff00 = /24 (the configured subnet)

                                      why  inet 192.168.2.1 –> 192.168.2.1

                                      pfSense 2.3.2-RELEASE-p1 (amd64)
                                      motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        doktornotor Banned
                                        last edited by

                                        @panz:

                                        why  inet 192.168.2.1 –> 192.168.2.1

                                        What's your problem with that, again? The question has been answered already. The tunnel endpoints are the same there.

                                        1 Reply Last reply Reply Quote 0
                                        • K
                                          kejianshi
                                          last edited by

                                          So, anyway - I've not been running pfsense this way before.  I've only done this with a DD-WRT as client to Pfsense/Openvpn and then DD-WRT has its clients…  Similar.

                                          No one has said yet, but I'm guessing the OPT3 got created auto-magically when you created the OpenVPN client in pfsense?  If so, I'm clear now.

                                          How well is this working for you?

                                          1 Reply Last reply Reply Quote 0
                                          • panzP
                                            panz
                                            last edited by

                                            @kejianshi:

                                            So, anyway - I've not been running pfsense this way before.  I've only done this with a DD-WRT as client to Pfsense/Openvpn and then DD-WRT has its clients…  Similar.

                                            No one has said yet, but I'm guessing the OPT3 got created auto-magically when you created the OpenVPN client in pfsense?  If so, I'm clear now.

                                            How well is this working for you?

                                            Absolutely not, I created the OPT3 to add a roadwarrior after all VPN testing from LAN –> to AirVPN were successful.

                                            pfSense 2.3.2-RELEASE-p1 (amd64)
                                            motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

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