Just moved from the UK to China - problems
-
on the screenshot you posted, clock WAN then post a screenshot of what your settings are there.
Since trying to re - recognise my wan port, I cannot get to a web interface anymore.
-
HDMI ??
What ports (NICS ?) ?
This guy https://forum.pfsense.org/index.php?topic=137702.0 also struggles with the same device …How are you sure that what you think the LAN is, is really the LAN port.
And WAN ?
The rest will be OPT1 and OPT2.Remember, we have only your words - nothing to test, no images.
-
HDMI ??
What ports (NICS ?) ?
This guy https://forum.pfsense.org/index.php?topic=137702.0 also struggles with the same device …How are you sure that what you think the LAN is, is really the LAN port.
And WAN ?
The rest will be OPT1 and OPT2.Remember, we have only your words - nothing to test, no images.
I am using the HDMI port on the qotom to output to HD TV.
I have installed pfsense on this machine while back home, it worked perfectly. I remembered which was LAN and the other was WAN. Yes, others will be OPT1 and OPT2. -
What pfSense version are you running? When was the last snapshot update carried out?
-
I have installed pfsense on this machine while back home, it worked perfectly. I remembered which was LAN and the other was WAN. Yes, others will be OPT1 and OPT2.
So, it works.
You shut it down - put it in a box, put it out of the box, hooked it up and … interfaces are lost.
Without no more info : that's not a software issue. More a hardware (power ?) issue.
LAN would be up right away. WAN would be different, because more "ISP" related.If the situation exists that because WAN is down, LAN is also down then your setup was broken to begin with.
What about resetting it ? Use the console access - assign a LAN - FIND the LAN port (it will give you an IP etc - you can access the GUI on it) and then setup your WAN, etc.
-
@marjohn56:
What pfSense version are you running? When was the last snapshot update carried out?
Latest stable version.
-
I have installed pfsense on this machine while back home, it worked perfectly. I remembered which was LAN and the other was WAN. Yes, others will be OPT1 and OPT2.
So, it works.
You shut it down - put it in a box, put it out of the box, hooked it up and … interfaces are lost.
Without no more info : that's not a software issue. More a hardware (power ?) issue.
LAN would be up right away. WAN would be different, because more "ISP" related.If the situation exists that because WAN is down, LAN is also down then your setup was broken to begin with.
What about resetting it ? Use the console access - assign a LAN - FIND the LAN port (it will give you an IP etc - you can access the GUI on it) and then setup your WAN, etc.
I will try again to get a LAN IP.
I will use choose a for auto detection.
How do I setup a WAN within the GUI? -
Oh Dear….
Basics, first things first. In the shell set the Interfaces correctly, until those are correct you are never going to get anywhere. Once you have a valid LAN connection/configuration, then you can use the web interface to set it the rest up.
-
@marjohn56:
Oh Dear….
Basics, first things first. In the shell set the Interfaces correctly, until those are correct you are never going to get anywhere. Once you have a valid LAN connection/configuration, then you can use the web interface to set it the rest up.
Hello marjohn56,
sorry to be a pain, I am trying to follow your instructions, now I cannot even see the console via HDMI. The cable works between my laptop and TV.
-
@marjohn56:
Oh Dear….
Basics, first things first. In the shell set the Interfaces correctly, until those are correct you are never going to get anywhere. Once you have a valid LAN connection/configuration, then you can use the web interface to set it the rest up.
Hello marjohn56,
sorry to be a pain, I am trying to follow your instructions, now I cannot even see the console via HDMI. The cable works between my laptop and TV.
O.K. Power off the Qotom, unplug it!
Next remove the HDMI cable from the laptop and plug it into the Qotom, power on the Qotom - watch the screen…..
Do you see anything?
If the answer is yes, then tell us what you see. If the answer is no, then the Qotom is borked.
-
@marjohn56:
@marjohn56:
Oh Dear….
Basics, first things first. In the shell set the Interfaces correctly, until those are correct you are never going to get anywhere. Once you have a valid LAN connection/configuration, then you can use the web interface to set it the rest up.
Hello marjohn56,
sorry to be a pain, I am trying to follow your instructions, now I cannot even see the console via HDMI. The cable works between my laptop and TV.
O.K. Power off the Qotom, unplug it!
Next remove the HDMI cable from the laptop and plug it into the Qotom, power on the Qotom - watch the screen…..
Do you see anything?
If the answer is yes, then tell us what you see. If the answer is no, then the Qotom is borked.
Yes, I see console now, after leaving it off for a few minutes:
WAN (wan) -> igb0 ->
LAN (lan) -> igb1 -> -
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.
