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

    Just moved from the UK to China - problems

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    78 Posts 11 Posters 10.8k 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
      belt9
      last edited by

      If it's just Mac filtering then can set pfSense to spoof the tplink.

      1 Reply Last reply Reply Quote 0
      • W
        Waqar.UK
        last edited by

        @belt9:

        This has been super entertaining!

        How certain are you that this WAN cable you are connecting to has a live WAN connection?

        Turn the wifi adapter on your laptop completely off, then plug the ethernet cable you think is WAN into you laptop or desktop.

        Can you access the internet?

        If not, restart the computer and try again.

        If you still can't access the internet, see if you can ping something ubiquitous.

        Try```
        ping www.baidu.com

        
        If that doesn't work, then the cable you think is WAN, is actually not WAN at all.
        

        I have tried that, by directly connecting the Ethernet cable coming from the wall to my pfsense box, no WAN connection.

        1 Reply Last reply Reply Quote 0
        • W
          Waqar.UK
          last edited by

          @Grimson:

          @marjohn56:

          Ideally, you would need to log into the old TP-Link and see how the WAN connection is set-up, it may be a static IP for all you know on the WAN side.

          Could also be a MAC filter on the other side, trying to prevent the use of different hardware. So it could help to use the WAN MAC of the TP-Link for the WAN interface in pfSense.

          I think so too. So how do I by pass this?

          1 Reply Last reply Reply Quote 0
          • W
            Waqar.UK
            last edited by

            @marjohn56:

            @Waqar.UK:

            @marjohn56:

            Ok, you should now be able to browse into pfsense. Connect the wan port after you have browsed to the control panel.

            I have connected my WAN cable (same one that goes into the old tp link router which allows me internet access), but all I get is a orange flashing led with no green led.

            That could mean that all you have is 100Mbps connection or even 10Mbps ( yuk ).

            I think I am now understanding that the WAN cable as it comes in is currently connected to the old TP-Link router, for which you have been given the SSID and password.

            OK, let's see how close I am to the truth, connect the WAN cable to pfSense, go to the pfSense control panel and what does it say about the interfaces, they should both be up ( if your laptop is connected to the LAN port that is! ). Does the WAN show it is connected at all ( Speed wise )?

            Ideally, you would need to log into the old TP-Link and see how the WAN connection is set-up, it may be a static IP for all you know on the WAN side.

            I have no WAN connection if I look at Interface drop down in web gui.

            1 Reply Last reply Reply Quote 0
            • W
              Waqar.UK
              last edited by

              @marjohn56:

              @Waqar.UK:

              @marjohn56:

              Ok, you should now be able to browse into pfsense. Connect the wan port after you have browsed to the control panel.

              I have connected my WAN cable (same one that goes into the old tp link router which allows me internet access), but all I get is a orange flashing led with no green led.

              That could mean that all you have is 100Mbps connection or even 10Mbps ( yuk ).

              I think I am now understanding that the WAN cable as it comes in is currently connected to the old TP-Link router, for which you have been given the SSID and password.

              OK, let's see how close I am to the truth, connect the WAN cable to pfSense, go to the pfSense control panel and what does it say about the interfaces, they should both be up ( if your laptop is connected to the LAN port that is! ). Does the WAN show it is connected at all ( Speed wise )?

              Ideally, you would need to log into the old TP-Link and see how the WAN connection is set-up, it may be a static IP for all you know on the WAN side.

              Sadly, I do not  have access to the old TP-Link router, Only have SSID and WPA2- AES password.

              1 Reply Last reply Reply Quote 0
              • B
                belt9
                last edited by

                well if it is MAC filtering and you no longer have access to the NIC it's assigned to then I would think your best bet would be to find the network manager and request that your NIC's MAC be added to the list.

                1 Reply Last reply Reply Quote 0
                • W
                  Waqar.UK
                  last edited by

                  Sadly it looks like that. Attached is a picture of what is connected to the TP -Link wireless router.
                  Yellow Ethernet is connected to TP -link
                  Grey Ethernet comes in from wall.
                  I do not know what that blue thing is.

                  IMG_20171010_094121.jpg
                  IMG_20171010_094121.jpg_thumb

                  1 Reply Last reply Reply Quote 0
                  • ?
                    Guest
                    last edited by

                    That is a modem by the look of it. What model is it?

                    There are ways  to crack this nut. For instance I would start by sniffing the packets coming from the TP-Link to the modem using wireshark, but if you don't know how to use that then you are lost.

                    1 Reply Last reply Reply Quote 0
                    • D
                      DaHai8
                      last edited by

                      The Blue thing is Fiber.
                      That Huawei box is a fiber modem/router. Most likely a EchoLife model of some kind.
                      Some simlar models:
                      https://www.alibaba.com/product-detail/huawei-fiber-optic-router_60667383784.html?s=p

                      If it is like other Chinese Fiber routers, it will be serving up 192.168.1.x local IP addresses, and handles all the PPPOE login credentials to your ISP (China Telecom/China Unicom)

                      Your issue may be that you've assigned the 192.168.1.x subnet to your pfSense LAN and the Huawei box is trying to assign that address to your WAN connection.
                      Try setting another subnet to LAN1 and see if that allows you WAN to get assigned from the Huawei box.

                      The model might be listed underneath and that might help finding the specs on that and a user manual - which could help further in troubleshooting this.

                      But more than likely, you'll be double-nat'd, which sucks, but it should still ultimately work.

                      1 Reply Last reply Reply Quote 0
                      • ?
                        Guest
                        last edited by

                        @LianYu4:

                        The Blue thing is Fiber.
                        That Huawei box is a fiber modem/router. Most likely a PowerLink model of some kind.
                        Some simlar models:
                        https://www.alibaba.com/product-detail/huawei-fiber-optic-router_60667383784.html?s=p

                        If it is like other Chinese Fiber routers, it will be serving up 192.168.1.x local IP addresses, and handles all the PPPOE login credentials to your ISP (China Telecom/China Unicom)

                        And if that is the case, getting to the login credentials is probably very unlikely. :)

                        Good advice you have given and a double NAT is probably the only solution.

                        1 Reply Last reply Reply Quote 0
                        • W
                          Waqar.UK
                          last edited by

                          I looked at the model:  echo hg8120f  made by huwei.

                          1 Reply Last reply Reply Quote 0
                          • ?
                            Guest
                            last edited by

                            Just had a quick look at the web site, authentication is carried out inside that fibre gateway. You can always try taking the cable that goes to the TP-Link from the fibre gateway and plugging that into the WAN port of the pfSense box. You should at least get a solid ethernet connection LED indicator.

                            Try that and see what you get.

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

                              Yeah, ditching the craptastic TP-Link would be a good start.

                              1 Reply Last reply Reply Quote 0
                              • W
                                Waqar.UK
                                last edited by

                                @marjohn56:

                                Just had a quick look at the web site, authentication is carried out inside that fibre gateway. You can always try taking the cable that goes to the TP-Link from the fibre gateway and plugging that into the WAN port of the pfSense box. You should at least get a solid ethernet connection LED indicator.

                                Try that and see what you get.

                                I have tried that, no luck. Just in case the Ethernet cable could be faulty (I checked before leaving the UK), I tried at least three other cables. No WAN lights (green and orange). I only get  orange.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  DaHai8
                                  last edited by

                                  Did you try setting your LAN to a different subnet?
                                  The Huawei router is probably using 192.168.1.x

                                  1 Reply Last reply Reply Quote 0
                                  • W
                                    Waqar.UK
                                    last edited by

                                    @LianYu4:

                                    Did you try setting your LAN to a different subnet?
                                    The Huawei router is probably using 192.168.1.x

                                    How do I do that please?

                                    1 Reply Last reply Reply Quote 0
                                    • ?
                                      Guest
                                      last edited by

                                      :o

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        belt9
                                        last edited by

                                        @Waqar.UK:

                                        @LianYu4:

                                        Did you try setting your LAN to a different subnet?
                                        The Huawei router is probably using 192.168.1.x

                                        How do I do that please?

                                        It's in the interface settings.

                                        Change "192.168.1.1" to "192.168.22.1" You can replace 22 with any number between 2 and 254.

                                        1 Reply Last reply Reply Quote 0
                                        • W
                                          Waqar.UK
                                          last edited by

                                          Sorry for a very late reply. I have been so busy as my life has turned upside down.

                                          My estate agent who is my first point of contact came to see if I could directly connect my ancient wireless TP link router to my laptop. She successfully did by using a Ethernet cable from the ancient wireless TP link router one of the Ethernet ports to my laptop.

                                          If I plug this into one of the Intel based Ethernet ports, I can still ping as described below even though the led above stays orange and never turns green and orange.

                                          So now I have a working WAN connection that I can use. :) I have  attached pictures of my WAN and LAN IP's

                                          OK, I have attached new pictures of my setup. I can ping various websites such as www.sky.com, www.krellonline.com, www.yahoo.com, www.ymail.com & www.bbc.co.uk. Strange thing is that my WAN light stays orange, never green and orange. The yellow Ethernet is from my  cable modem

                                          I have a  LAN IP as proven in one of my attached pictures which has both green and orange led lights. My problem is that I cannot reach 192.168.1.1 to finalise my pfsense setup. I even tried to temporary disable my internet security software. Still no LAN can be seen.

                                          I forgot to add, the black Ethernet is from back of the ancient TP link wireless router into my pfsense box. White is my LAN cable that goes into the Ethernet port of my Dell xps.

                                          My final setp should  be: back of ancient TP link router -> WAN on my pfsense box -> LAN on my pfsense box to my wireless AP a old but stable Asus RTN 66U (with the latest firmware that is still being supported by Asus)

                                          IMG_20180310_18314cHDR.jpg
                                          IMG_20180310_18314cHDR.jpg_thumb
                                          IMG_20180310_174539_HDR.jpg
                                          IMG_20180310_174539_HDR.jpg_thumb
                                          IMG_20180310_174901_HDR.jpg
                                          IMG_20180310_174901_HDR.jpg_thumb
                                          IMG_20180310_175004_HDR.jpg
                                          IMG_20180310_175004_HDR.jpg_thumb
                                          IMG_20180310_175518_HDR.jpg
                                          IMG_20180310_175518_HDR.jpg_thumb
                                          IMG_20180310_175824_HDR.jpg
                                          IMG_20180310_175824_HDR.jpg_thumb
                                          IMG_20180310_181136_HDR.jpg
                                          IMG_20180310_181136_HDR.jpg_thumb
                                          IMG_20180310_182042_HDR.jpg
                                          IMG_20180310_182042_HDR.jpg_thumb

                                          1 Reply Last reply Reply Quote 0
                                          • ?
                                            A Former User
                                            last edited by

                                            Your pictures clearly show your WAN and LAN fighting over the same subnet of addresses.
                                            On the console you will see option 2 "Set interface IP address" pick that one and change your LAN (igb1) to another private IP range.
                                            Try 10.0.0.0/24 or 172.16.0.0/24 anything but what you are using now.
                                            Your firewall will be at 10.0.0.1 or 172.16.0.1 depending on your choice.
                                            " I have been so busy as my life has turned upside down. " Yup, think your machine knows the feeling. o_0

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