Just moved from the UK to China - problems
-
What is the ip address given for the LAN?
-
@marjohn56:
What is the ip address given for the LAN?
LAN IP is: https://192.168.1.1
LAN (up green arrow) 1000baseT <full-duplex> 192.168.1.1 both green and yellow LEDs yare lit.
My Internet Ethernet is plugged into the ancient tp link router, when I un plug it and put it into my Ethernet port that I have designated as a WAN igb0 only the yellow LED lights up.</full-duplex>
-
ZOMG. At the interfaces autodetection, get ALL cables unplugged. Let it probe for WAN. Plug in the cable to what you think is your WAN. Does it get an IP lease? If not, plug in the cable in what you think is your LAN.
-
Progress…
Now, goto your laptop and set a STATIC ip address on the lan of 192.168.1.50. Mask 255.255
255.0. Gateway should he .1 but it's not important at this point. Now open a cms prompt and if Windows then ping 192.168.1.1 -t and connect a cat cable between the laptop and qotom, if you see a response you vs found the lan, if not.move to the next port until you find a response. Once you have a response you can then browse to offense and set the rest up. -
I am getting:
Microsoft Windows [Version 6.1.7601]
Copyright
2009 Microsoft Corporation. All rights reserved.C:\Windows\system32>ping 192.168.1.1 -t
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64again and again
-
ZOMG. At the interfaces autodetection, get ALL cables unplugged. Let it probe for WAN. Plug in the cable to what you think is your WAN. Does it get an IP lease? If not, plug in the cable in what you think is your LAN.
I have tried that, only the LAN is recognised, the WAN only flashes orange.
-
Ok, you should now be able to browse into pfsense. Connect the wan port after you have browsed to the control panel.
-
Assuming you can now browse to the control panel AND you have connected the WAN cable, you will the need check your wan settings are correct and your lan dhcp server settings are correct before restoring your laptop lan setting to DHCP.
-
@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.
-
@marjohn56:
Assuming you can now browse to the control panel AND you have connected the WAN cable, you will the need check your wan settings are correct and your lan dhcp server settings are correct before restoring your laptop lan setting to DHCP.
How do I, do that please? As the internet was set up by the estate agent who only gave me the ssid and password to connect wirelessly.
Attached is a screen grab of my WAN settings.
 -
What are you connecting the WAN port to?
Dok, is this you having a laugh? :o
-
@marjohn56:
What are you connecting the WAN port to?
Dok, is this you having a laugh? :o
I am connecting my Ethernet coming into my flat to my pfsense box WAN.
-
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.comIf that doesn't work, then the cable you think is WAN, is actually not WAN at all. -
-
This is perfect. I'm wondering if he had the interwebs turned on when he moved?
Would his new location be a part of the issue? Doesn't China proxy everything, to protect its citizens, or is that just DPRK?
On a lighter note, I too have a Qotom box, however my nics register as re0 and re1.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.comIf that doesn't work, then the cable you think is WAN, is actually not WAN at all. -
How certain are you that this WAN cable you are connecting to has a live WAN connection?
If that doesn't work, then the cable you think is WAN, is actually not WAN at all.The guy is just NOT reading.
I still think it's you on a wind-up.
-
This is perfect. I'm wondering if he had the interwebs turned on when he moved?
Would his new location be a part of the issue? Doesn't China proxy everything, to protect its citizens, or is that just DPRK?
On a lighter note, I too have a Qotom box, however my nics register as re0 and re1.I think it all has to go through the Great Firewall of China. Quite surprised he's managed to get this far, but no mention of the party please, otherwise he'll be Peking Ducked.
-
@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.
-
@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.
-
If it's just Mac filtering then can set pfSense to spoof the tplink.
