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

    Access Modem GUI Behind Firewall

    Scheduled Pinned Locked Moved NAT
    firewall rulesnat rulesinterfacegui accessmodem
    107 Posts 5 Posters 10.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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @Globaltrader312
      last edited by johnpoz

      @Globaltrader312 Why would your outbound nat rule be on wan2.. Your interface is the vigor interface.. this is the physical interface that you put the 5.x address on that connects to the vigor device.

      Your nat should be natting to that interface..

      And for your sniff, set a host to 192.168.5.1 - the destination address your waning to talk too.. You don't need to see any other noise..

      You create the interface per the instructions, since your pppoe. You put an IP on it, you nat to this IP..

      Here is what I would do - pull out everything you have randomly clicked on to try and get this to work.. Follow the instructions. Create an interface. Put the IP on it, change to hybrid nat and setup an outbound nat for going to this 5.1 address to be natted to the interface IP you created.

      These is the 2 steps defined in the instructions.

      Where your setup differs is you have multiple wan interfaces, and your policy routing. So you need a rule on the interface where your traffic is going to come into pfsense that wants to talk to the vigor device. This rule needs to be above where you policy route out some specific gateway, be it a load balancer, a failover group or whatever.

      Make sure there are no rules in floating that would interfere with your traffic. Also this 192.168.5 your wanting to talk to - this can not overlap with your lan network, nor any other local network you have attached to pfsense.

      Now sniff on the vigor interface, with a host filter IP of 192.168.5.1 (your IP your wanting to talk to from this interface).. Do you see traffic going out, natted to the 192.168.5.x address you put on the pfsense interface you created.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      G 1 Reply Last reply Reply Quote 0
      • G
        Globaltrader312 @johnpoz
        last edited by

        @johnpoz said in Access Modem GUI Behind Firewall:

        Your nat should be natting to that interface..

        And for your sniff, set a host to 192.168.5.1 - the destination address your waning to talk too.. You don't need to see any other noise..

        You create the interface per the instructions, since your pppoe. You put an IP on it, you nat to this IP..

        Here is what I would do - pull out everything you have randomly clicked on to try and get this to work.. Follow the instructions. Create an interface. Put the IP on it, change to hybrid nat and setup an outbound nat for going to this 5.1 address to be natted to the interface IP you created.

        These is the 2 steps defined in the instructions.

        Where your setup differs is you have multiple wan interfaces, and your policy routing. So you need a rule on the interface where your traffic is going to come into pfsense that wants to talk to the vigor device. This rule needs to be above where you policy route out some specific gateway, be it a load balancer, a failover group or whatever.

        Make sure there are no rules in floating that would interfere with your traffic. Also this 192.168.5 your wanting to talk to - this can not overlap with your lan network, nor any other local network you have attached to pfsense.

        Now sniff on the vigor interface, with a host filter IP of 192.168.5.1 (your IP your wanting to talk to from this interface).. Do you see traffic going out, natted to the 192.168.5.x address you put on the pfsense interface you created.

        I have done the following

        I created an INterface again with the name VIGOR then gave the interface the IP address with 192.168.5.3 then I created the Outbount NAT Rule as in the instructions as in the screenshot unfortunately it only lets me enter 192.168.5.0/24 for Destination it always changes this after saving.

        for Translation address I entered 192.168.5.3 which is the one from the Vigor interface.

        As far as the rules about the Policy Based rules are concerned, I am currently stuck there, so I only have the two any to any rules and of course the gateway is specified there, the Failover GW where all 3 WANs are included as tier 1 2 3.

        if I have understood it correctly, an extra rule has to be created there again, right ? only which one

        Bildschirmfoto 2024-06-24 um 16.41.59.png Bildschirmfoto 2024-06-24 um 16.42.10.png

        johnpozJ 1 Reply Last reply Reply Quote 0
        • johnpozJ
          johnpoz LAYER 8 Global Moderator @Globaltrader312
          last edited by johnpoz

          @Globaltrader312 Why are you showing rules on wan2 - this has zero to do with anything.

          Maybe this is all a translation issue?

          Maybe you should ask for help in your native language section, because we seem to not be able to communicate??

          As to changing your destination in an outbound nat - if you set the mask to /24 then yeah it prob changes the last octet to .0 - if you want to set the specific IP then the mask would be /32

          edit: an an any any rule on a wan, is never going to be a good idea.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

          1 Reply Last reply Reply Quote 0
          • patient0P
            patient0 @Globaltrader312
            last edited by

            @Globaltrader312 Btw: The NAT Outbound rule is on the VIGOR interface, as per docu.

            G 1 Reply Last reply Reply Quote 0
            • G
              Gblenn @patient0
              last edited by

              @Globaltrader312 said in Access Modem GUI Behind Firewall:

              @johnpoz
              then i misunderstood that i thought that would be the solution
              i added the interface vigor to bge 0 and gave this interface the ip 192.168.5.3 and with this and the outbound nat rule it does not work.

              i thought if i did exactly that it would work.

              with my other interface where i use DHCP to get the fixed IP from the ISP i can access the modem without extra rules but not with the SVDSL MOdem.

              yes i need vlan tag 7 therefor the interface is 1,7
              pppoe runs on bge1 / ppoe1 and the interface vigor too

              @patient0 How do you access the UI of the modem for WAN1 where you seem to have a public IP (DHCP)?

              Have you tried creating a static route for 192.168.5.1 /32, using the VIGOR interface as the Gateway in the setup?

              G 1 Reply Last reply Reply Quote 0
              • G
                Globaltrader312 @Gblenn
                last edited by

                @Gblenn

                I have a static public IP on WAN 1 which I have been assigned by my cable provider in the business tariff via DHCP via my cable modem.
                Bildschirmfoto 2024-06-24 um 18.42.04.png
                is a dual stack IPV4 and IPV6

                the modem IP of the technicolor TC4400 is 192.168.100.1 is connected to WAN 1 BGE0 when I open it it works without extra rules or anything else.

                See screenshot

                G johnpozJ 2 Replies Last reply Reply Quote 0
                • G
                  Gblenn @Globaltrader312
                  last edited by

                  @Globaltrader312 Ok so pfsense simply routes that request out the WAN1 then. I assumed it would never try to route an unknown private IP out the WAN... ??

                  I wonder though, the VIGOR interface isn't part of your load balancing or failover setup is it?? It's not a gateway at all actually... So then the only way for pfsense to actually route any traffic that way would be to specifically tell it.

                  Set up a static route, under System / Routing / Static Routes... create one with :

                  Destination network : 192.168.5.1 / 32
                  Gateway : VIGOR interface

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator @Globaltrader312
                    last edited by johnpoz

                    @Globaltrader312 yeah sometimes you don't need an IP or nat. My old modem use to answer with no need for a different interface IP on the 192.168.100 network.. It would intercept the traffic sent out the wan because it was to 192.168.100.1 and send the answer back to the source IP which was just my public IP.

                    But even if that was the case, natting to an IP that is on the network you want to talk to isn't going to break anything.. But you seemed confused on where you want to set it and what rules you need..

                    if your vigor interface bge1 is connected to the vigor device, and this device has an IP of 192.168.5.1 and you put an IP of 192.168.5.x on your bge1 interface.. Pfsense knows how to get there.. You need to nat it because its quite possible if your source is say 192.168.1.x the vigor devices isn't going to send the answer back to your 192.168.5.2 IP.

                    You don't seem able or willing to follow simple instructions or provide info asked for.. Why in the world would you create an any any rule on your wan2 for trying to talk to something connected to bge1 interface?? Just at a complete loss..

                    This takes all of 2 seconds to validate you your setup.. Sniff on bge1 - does pfsense send the traffic out this interface? Does it nat to your 192.168.5.x address. If it is not - then you got something wrong in what you setup in pfsense.. Its just that simple..

                    This is step one - because if your not sending traffic out your bge1 interface - how do you expect to talk to an IP on the other end of the wire you have connected to bge1?

                    Set up a static route, under System / Routing / Static Routes... create one with :

                    You do not need a route.. If pfsense has an interface connected to network X.. Why would it send traffic out any other gateway be it default or not when it has an interface attached to that network?

                    Unless you had a specific route, to this 192.168.5.X address it would always pick the interface it has in network 192.168.5.x

                    Viewing the routing table in pfsense could be helpful info.. But there is zero reason to create a route, unless he has created a route with a better route for 192.168.5 out some other interface.

                    Here is my routes - why would it send traffic out the default for any of the networks its directly attached too?

                    routes.jpg

                    See the route for 192.168.100.0/24 - that is the network its attached to via the VIP I created on mine, etc..

                    If he is sending the traffic out some other interface because of policy routing then no its never going to work.. But create a route isn't going to fix his policy routing rule that would be sending traffic out the wrong gateway... He just needs a rule above his policy route that allows the traffic and uses pfsense normal routing..

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    G G 2 Replies Last reply Reply Quote 0
                    • G
                      Globaltrader312 @johnpoz
                      last edited by Globaltrader312

                      @johnpoz

                      sorry the answers always come a little late

                      so I have deleted the static route again.

                      then i checked the routing tbale once see screen shot interface and IP are visible.

                      I created these any to any in the firewall for the lan rules for IPV4 and IPv6 according to the instructions for the failover setup erv, otherwise I created them separately.

                      I have selected the failover gateway in the dropdown under advanced in the lan rules I think the firewall will send everything over it can it be because of that ? see screen shot....

                      I would like to do your steps I'm just stuck at the point where I write I should create a rule about the Policy Based rules which exactly only the outbound nat I have or another ?

                      I will do the sniff and then send the info. Bildschirmfoto 2024-06-24 um 19.59.15.png Bildschirmfoto 2024-06-24 um 20.33.38.pngBildschirmfoto 2024-06-24 um 20.36.15.png Bildschirmfoto 2024-06-24 um 20.43.47.png no traffic comes through when I check with packet capture on interface Vigor BGE 1

                      1 Reply Last reply Reply Quote 0
                      • G
                        Gblenn @johnpoz
                        last edited by Gblenn

                        @johnpoz said in Access Modem GUI Behind Firewall:

                        Set up a static route, under System / Routing / Static Routes... create one with :

                        You do not need a route.. If pfsense has an interface connected to network X.. Why would it send traffic out any other gateway be it default or not when it has an interface attached to that network?

                        Unless you had a specific route, to this 192.168.5.X address it would always pick the interface it has in network 192.168.5.x

                        Viewing the routing table in pfsense could be helpful info.. But there is zero reason to create a route, unless he has created a route with a better route for 192.168.5 out some other interface.

                        If he is sending the traffic out some other interface because of policy routing then no its never going to work.. But create a route isn't going to fix his policy routing rule that would be sending traffic out the wrong gateway... He just needs a rule above his policy route that allows the traffic and uses pfsense normal routing..

                        Bildschirmfoto 2024-06-24 um 19.59.15.png

                        No you are of course absolutely right, his routing table clearly shows 192.168.5.0/24 as well, and I find it strange that it wouldn't "just work". Very confusing all of it though... and if there is some policy rule as well, I missed that...

                        A question though... will pfsense process send a request to an unknown IP via the WAN, even if it belongs to an RFC 1918 range? I guess I was thinking it would just drop it?

                        johnpozJ 1 Reply Last reply Reply Quote 1
                        • johnpozJ
                          johnpoz LAYER 8 Global Moderator @Gblenn
                          last edited by

                          @Gblenn said in Access Modem GUI Behind Firewall:

                          and I find it strange that it wouldn't "just work".

                          because as you can see by his lan rules - he is policy routing.. Which has been brought up multiple times already.. He needs a rule to allows the normal routing to work..

                          policyroute.jpg

                          Here

                          https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html#bypassing-policy-routing

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                          G 1 Reply Last reply Reply Quote 1
                          • G
                            Globaltrader312 @johnpoz
                            last edited by

                            @johnpoz I apologise for asking this question.

                            I have looked at the instructions, unfortunately I do not understand one point in the instructions it says to create an alias for RFC1918 and in the picture it can also be seen that RFC1918 was set as destination.

                            but when i want to create a new rule, the destination RF1918 is displayed as invalid IP so i don't quite understand how i can set this i can only set an IP subnet e.g. 192.168.0.0/16

                            johnpozJ 1 Reply Last reply Reply Quote 0
                            • johnpozJ
                              johnpoz LAYER 8 Global Moderator @Globaltrader312
                              last edited by

                              @Globaltrader312 Huh.. You don't need to create such an alias you could just put in 192.168.0.0/16 cidr in the rule.. Or just your 192.168.5.1/32 or 192.168.5.0/24

                              But creating an alias for all rfc1918 space would be done in the alias section

                              alias.jpg

                              Here would be an example of using it in rule - this isn't a rule like you need but just an example of using the alias in a firewall rule

                              rule.jpg

                              An intelligent man is sometimes forced to be drunk to spend time with his fools
                              If you get confused: Listen to the Music Play
                              Please don't Chat/PM me for help, unless mod related
                              SG-4860 24.11 | Lab VMs 2.8, 24.11

                              G 1 Reply Last reply Reply Quote 1
                              • G
                                Globaltrader312 @johnpoz
                                last edited by

                                @johnpoz

                                I have now created the rule via the Policy Based Rules and traffic is also flowing see screen shot and packet capture

                                but the GUI of the Vigor is still not accessible.

                                can it be that I still have to enter the changed ports from vigor in the firewall 8080 and 444 which I changed because of an advice from another user a few posts before.Bildschirmfoto 2024-06-24 um 23.39.53.png Bildschirmfoto 2024-06-24 um 23.41.10.png

                                johnpozJ 1 Reply Last reply Reply Quote 0
                                • johnpozJ
                                  johnpoz LAYER 8 Global Moderator @Globaltrader312
                                  last edited by johnpoz

                                  @Globaltrader312 well if your device is not listening on port 80 any more, and you try and talk to port 80 which is what your sniff shows - then yeah its not going to answer. Either change its port back to 80, or talk to it on port whatever you changed it too

                                  http://192.168.5.1:port

                                  But your sniff shows 192.168.5.0 -- that is not really a valid IP address using a /24 mask.. I thought you set your pfsense interface to be .2 and or .3 why would it be using .0??

                                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                                  If you get confused: Listen to the Music Play
                                  Please don't Chat/PM me for help, unless mod related
                                  SG-4860 24.11 | Lab VMs 2.8, 24.11

                                  G 1 Reply Last reply Reply Quote 1
                                  • G
                                    Globaltrader312 @johnpoz
                                    last edited by

                                    @johnpoz

                                    so i have now set the ports back to 80 and 443 it still does not work unfortunately

                                    the 192.168.5.0/24 is because when I set Vigor to /32 under interfcaes no packets get through.

                                    if i set it to /24 then packets go through at 192.168.5 but it says 192.168.5.0 / 24.Bildschirmfoto 2024-06-25 um 14.16.53.png

                                    johnpozJ 1 Reply Last reply Reply Quote 0
                                    • johnpozJ
                                      johnpoz LAYER 8 Global Moderator @Globaltrader312
                                      last edited by

                                      @Globaltrader312 no idea what your talking about?

                                      Your address there is 192.168.5.3, why would pfsense change the address it sends from to .0??? That doesn't happen

                                      The mask of /24 means this

                                      The Wire or network is .0, the host address on this /24 network is .1 to .254, the broadcast address is .255

                                      What you show there is correct, the interface address would be .3, there is no scenario that I can think of where pfsense would jsut on its own change that to .0 as its source address when natting to that interface.

                                      Please post your outbound nat rule..

                                      Why do you show .3 and .4?

                                      address.jpg

                                      Did you create a vip or something? And your natting to the vip address? VIP is not something you need to create.. VIP was my attempt at showing you how it can be done when your actual interface has a actual public IP like mine does... You are using PPPoE so you don't need to create a vip

                                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                                      If you get confused: Listen to the Music Play
                                      Please don't Chat/PM me for help, unless mod related
                                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                                      G 1 Reply Last reply Reply Quote 1
                                      • G
                                        Globaltrader312 @johnpoz
                                        last edited by

                                        @johnpoz Bildschirmfoto 2024-06-25 um 16.59.58.png

                                        johnpozJ 1 Reply Last reply Reply Quote 0
                                        • johnpozJ
                                          johnpoz LAYER 8 Global Moderator @Globaltrader312
                                          last edited by johnpoz

                                          @Globaltrader312 just show your outbound nat tab.. Not the specific details of 1 of them - for a we know this one isn't even being used because you have some other one above it.

                                          Example here is mine

                                          nat.jpg

                                          But this isn't right

                                          network.jpg

                                          Click the dropdown and pick the Vigor address, which would be 192.168.5.3 from your screenshot

                                          dropdownjpg.jpg

                                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                                          If you get confused: Listen to the Music Play
                                          Please don't Chat/PM me for help, unless mod related
                                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                                          G 1 Reply Last reply Reply Quote 1
                                          • G
                                            Globaltrader312 @johnpoz
                                            last edited by Globaltrader312

                                            @johnpoz Bildschirmfoto 2024-06-25 um 17.21.57.png

                                            thank you guys for your help it works after i entered the alias rfc1918 as soure and selected 192.168.5.0/24 as destination and Vigor aadress as translation address.Bildschirmfoto 2024-06-25 um 17.21.48.png

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