Can ping to LAN but not Web Configurator
-
And is your browser using a proxy.. And not set to bypass on local networks that would explain why it can not get to a local address.. If you have not set a proxy, then you have an infection would be my guess.
Fire up wireshark on the box - what does it show going on the wire..
-
Maybe I just got lost in the reading…
But if you are trying to reach the web gui on 10.0.0.1
and your lan address on pfsense is 192.168.1.1
You will never succeed.
Can you please attach a photo of the browser error you get when you try to access the web gui also?
-
You have tried https yes?
Since you are seeing a pfsense favicon have you ever connected to another pfSense box at that address?
Steve
-
You know - Something very basic has to be wrong because in default setup, pfsense just works.
I suggest a reinstall from scratch and maybe even try another computer as client.
Also, check your cables.
-
I have setup pfsense I don't know how many times going back to very early version 1.x - running devolpment versions, etc. etc. Hardware and VM from everything to virtualbox, to vmware server 1, vmware server 2, esxi version 3.5 through 5.5
Have never seen it not just work out of the box. So here is the thing - is anything else connected to this switch, does the switch have an IP on it or just dumb switch.
Validate the MAC address pfsense has for its lan interface, and the mac address your pinging. On pfsense do a netstat do you see the web gui running?
[2.1.5-RELEASE][root@pfsense.local.lan]/root(7): ps -ax | grep lighty
46888 ?? S 0:17.64 /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf[2.1.5-RELEASE][root@pfsense.local.lan]/root(9): netstat -an | grep .80
tcp6 0 0 *.80 . LISTEN
tcp4 0 0 *.80 . LISTEN[2.1.5-RELEASE][root@pfsense.local.lan]/root(10): ifconfig
vmx3f1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
options=403bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso>ether 00:0c:29:1e:18:ae
inet 192.168.1.253 netmask 0xffffff00 broadcast 192.168.1.255And again - run wireshark on the box your trying to connect to pfsense on.. What does it show? I would really look to your browser being setup to use a proxy, and not set to bypass for local network, or infected. You don't have anything installed on this pfsense install like squid or snort, etc.? Its clean - and your saying its routing internet traffic - but you can not connect to even run the first setup wizard and change the pfsense password, etc.</rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso></up,broadcast,running,simplex,multicast>
-
Interesting idea that maybe something else is interfering…
Unplug the switch. Plug the computer directly into the pfsense LAN with nothing else attached then give it a try.
-
^ for all we know for his switch he is using some soho routers switch ports and it has an IP of 192.168.1.1, which you would think he would get that web gui. But when something doesn't work that you think should be working, it takes 2 seconds to validate your actually talking to the correct something. Have run into duplicate IPs too many times to not validate the mac.
I would think more likely reason is that his browser is just using some proxy..
-
Some devices do not redirect to https when you try to use http and behave like this.
If you had two devices trying to be 192.168.1.1 would you get ping response in both directions? Especially if one of them was the switch.Steve
-
no you could get answer to ping
so from 192.168.1.100 I ping 192.168.1.1 but get mac of say the switch IP.. He answers. When you ping the 100 from pfsense .1 he pings the mac of .100 and .100 send answer to the mac that asked.
-
Hmm, yes layer 2/3 difference. The MAC would show though as you've been saying.
Steve
-
Thanks for all the input guys, really appreciated.
As suggested, I've taken out the switch, now directly connect my notebook to LAN interface (white cable , UE1 on pfsense), WAN (UE0) still the same Red Cable
I followed the instructions as shown to me
I can't confirm the MAC address as the J5 creator doesn't print the MAC on the unit nor the package it came with
I've checked my Proxy setting to make sure
I've installed Wireshark and as soon as I go to the pfsense box (192.168.1.1) I get the RED text on Black shown in Wireshark
-
Oh I forgot to mentioned . Yes I've connected to another pfsense box to that address in the past.
And .. I've also tried connecting using another Desktop PC, same results.
It is a clean install, it doesn't route internet traffic yet, WAN interface is connected but I can't access internet on my notebook.
-
Hmm, weird. Looks like the pfSense box is replying but your laptop is ignoring the replies. Perhaps. :-\
Are you able to browse other external sites? Ping external addresses? In other words is routing working?
I notice your WAN interface has auto-negotiated to 10Mb which is odd but shouldn't be causing this.
Steve
-
I've installed Wireshark and as soon as I go to the pfsense box (192.168.1.1) I get the RED text on Black shown in Wireshark
SYN from you
SYN,ACK from pfSense
ACK from you should be next. It's not there so you aren't getting the webConfigurator. -
So .. just to be sure I'm not doing anything stupid…
I've wipe & Re-Install PFsense again.
I selected option 1
I selected option I
And it is still not working for some strange reason.
The routing isn't working either as I can't access external internet.
-
More USB ethernet…
Trouble shooting these setups is always hard when they are so simple and yet things refuse to work, but I don't like USB ethernet, and I'm sure its working for some people in some installations, but up to this point, its the most likely culprit I've noticed. You don't have even a single built in NIC?
-
I'm thinking whether it's those USB ethernet adapter is causing it. I'll see if I can try another brand and see if it makes any difference.
-
Hard to believe it would work with ICMP but not TCP.
As Derelict said your client is not responding. This appears to be a client side issue. Yet you say you tried a different client? Different browser?Steve
-
You want to check that "Block private networks" is unchecked on your WAN interface. I don't know if the installer does that by default if it detects a private WAN address.
Is that wireshark capture a few messages back taken from the 192.168.1.100 windows client? If so, you need to figure out why it is not sending an ACK in reply to the SYN,ACK sent by pfSense in the connection process before you waste any more time looking at pfSense.
Or, as has been mentioned, USB ethernet interfaces: not a fan. BUT if they're mucking up the works, it should show in the SYN,ACK captured by wireshark.
-
If you look at "Valid interfaces are" the answer is:
Probably not…