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

    Access to the modem web page

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 8 Posters 8.7k 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
      last edited by johnpoz

      So some devices when you put in bridge mode no longer listen on management IP.. So that might be the reason you can not access it..

      192.168.8.1 is not your typical view my info on this IP sort of IP.. if that was the old lan IP you had before you put it bridge mode - its highly likely that IP is just gone and you should prob need to use something like the industry standard of 192.168.100.1

      So your device is this Huawei E5186?

      From looking at that hack to get bridge mode..

      Note you must plug in the ethernet cable into the 4th LAN port labeled LAN/WAN, then plug the other end into your router servicing your LAN.
      

      So if you want to get to 192.168.8.1 I would think you need to be connected to one of the other ports since it seems to put that 4th port into bridge mode... So plug a box into one of the other ports to access its 192.168.8.1

      Do you have another interface on pfsense - you could connect one of the other ports to this interface, or vlan to access it.. That is the way I read that hack of a bridge mode for this device.

      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.7.2, 24.11

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Yes, looks like you might need an extra connection there. But test it from pfSense as I outlined, that is in the same subnet so is able to connect (if you don't need an extra connection).

        Usually with this type of setup you need to NAT the traffic as most "modems" have no facility for adding a route of gateway on the LAN side. They can only talk back to devices in the subnet.

        Steve

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

          Comcast business gateways are like this... 1 Port of the switch on them can be put in bridge mode, and the other ports are natted..

          Your not going to be able to hit the LAN ip from the bridged interface.. Your going to need to connect to one of the non bridged ports.

          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.7.2, 24.11

          1 Reply Last reply Reply Quote 0
          • mrvargaM
            mrvarga
            last edited by mrvarga

            I connect another lan cable to pfsense router lan3 port to the model lan1 port. Set the interface to dhcp but this is the result:
            0_1542317982836_9bcface7-c832-4e30-b8df-ac90f3ba4a1e-image.png
            If I set the iterface to static ip 192.168.8.100/24 and I try to ping the router:
            0_1542320214224_ccbb9106-4964-449c-b03a-fa4c95e6a34d-image.png

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              If you have to access the modem (honestly, how often does one really have to do this?) connect a laptop.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              mrvargaM 1 Reply Last reply Reply Quote 0
              • mrvargaM
                mrvarga @Derelict
                last edited by

                @derelict yes this is right, but is just for learn new things.
                I think the error is in the modem ip address, the right is 192.168.1.1 and not the 192.168.8.1.
                When I arrive home I will try...

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

                  From what I researched the default IP is the 8, but sure that could of been changed... My point was that once you put it in bridge mode that lan IP of what is actually a gateway and not a "modem" is not going to be available on the bridged interface.. So you will have to access if via one of its other switch ports.

                  This is completely different than say a "cable" modem that bridges your connection to the router behind (pfsense) and then also listens on 192.168.100.1 address on the same L2..

                  I concur with Derelict there is really little reason to just not connect a box to one of the "natted" switch ports on that gateway device if you need to access it... But its also possible to to connect and interface to pfsense..

                  The question comes down to the details of that device - which I have no actual experience with other than that thread you listed and I breezed through. But what I do have experience with is other "cable" gateways where you can put 1 port of the switch in bridge mode and device connected will get a public IP.. and other devices on other ports will get a natted ip - but in such cases dhcp is still running and connecting a device set for dhcp should get an address.

                  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.7.2, 24.11

                  1 Reply Last reply Reply Quote 0
                  • mrvargaM
                    mrvarga
                    last edited by mrvarga

                    Can be my setting wrong, because somtimes (once every two days I lost the wan connection and the wan IP is 0.0.0.0) so I don't have internet and and have to manualy reboot the modem...
                    The modem is Huawei E5186 put in bridge mode by this guide (https://forums.whirlpool.net.au/archive/2670005), and the WAN interface setting si:
                    0_1543155915302_37a37d0d-dc0c-4694-8e52-597cdf7ef85b-image.png
                    And this is the result:
                    0_1543156043557_b2172a24-630e-455d-aa23-7481b7a73e41-image.png
                    I have also a lot of this log....
                    0_1543156562531_2902a840-1e28-4ca9-a889-1b0e31fdd565-image.png

                    BabizB 1 Reply Last reply Reply Quote 0
                    • BabizB
                      Babiz @mrvarga
                      last edited by

                      @mrvarga Hi!

                      Here is my current working layout of pfSense, I can login to modem web ui
                      at 192.168.254.1 when it is propely configured with pppoe 8/35 link , dhcp server and bridge mode!
                      Because I add another MODEM interface side by side to PPPoe interface.

                      pfSense do all work and no need to make additional hybrid nat rule with this simple layout.
                      I also setup ipsec vpn and for reach remote device for mamaging watching remote stuffs, I do on remote site some hybrid nat and vips to re routing traffic on my local subnet. yes it's really amazing 🚪
                      alt text
                      alt text

                      Cheers.

                      mrvargaM 1 Reply Last reply Reply Quote 0
                      • mrvargaM
                        mrvarga @Babiz
                        last edited by

                        @babiz 😱

                        1 Reply Last reply Reply Quote 1
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          If you're seeing an odd IP on the WAN you should check the dhcp logs to see if it's actually being handed to you. You migyht need to reject DHCP leases from the 'modem' itself. Though 0.0.0.0 is not normally something you would see in that situation.

                          https://www.netgate.com/docs/pfsense/book/interfaces/ipv4-wan-types.html#dhcp

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • D
                            discy @johnpoz
                            last edited by discy

                            PC on lan at 192.168.9.100, just put 192.168.100.1 in the browser and bing bang zoom... No vips, not odd nats, no disable reply-to.. No floating rules.

                            Same for me. Nothing to be done. 192.168.100.1 Ziggo/UPC/Vodafone "Connect-box" in bridge.

                            Just had to add a rule on top of LAN from LAN-NET to the modem on WAN_DHCP gateway because other rules mess it up.

                            dc49e387-0f0a-45cd-a096-cc006736ef30-image.png

                            1 Reply Last reply Reply Quote 0
                            • M
                              MarioNava
                              last edited by MarioNava

                              Hello there.
                              I had the same problem, accessing my router behind PfSense.
                              Internal lan is 192.168.0.x Pfsense on 192.168.0.254
                              Router is 192.168.1.254
                              There was no way to access it. Then i checked my network card IPs.
                              I had 2 assigned. 192.168.0.22 and 192.168.1.22
                              Removed 192.168.1.22 amd then BANG! router interface is reachable.
                              Is really THAT simple as other people wrote. NO need to mess up anything.
                              Hope this helps someone.
                              Have a nice day,

                              Mario

                              1 Reply Last reply Reply Quote 1
                              • T tman222 referenced this topic on
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.