Can ping to LAN but not Web Configurator
-
Would you mind showing us the output of ipconfig /all or, if you are using linux, ifconfig ? Also, would you mind showing the IP and cidr of the PFSense interface? That would help a lot.. it sort of sounds like dhcp is handing out the incorrect subnet or something similar.. also, are you trying to connect to the web interface using a dns name, or the ip address directly? (I know a lot of these questions sound pointlessly simple, but they would help rule out a few things..)
Also, have you tried setting the IP address of your laptop statically and connecting to the pfsense machine? Also, have you enabled SSH and tried connecting through ssh? If you did connect through SSH (or even could connect to ssh using telnet as a test.. ex: telnet 192.168.1.1 22) it would definitely show that you've only having issues with the web interface and not ip/tcp communication..
Something to mention.. I've run into this issue once before actually. I ended up backing up the configs, setting it to factory defaults, loading just the firewall, nat, and alias configs and then set up wan/lan all over again… Just doing a factory reset and restoring the whole thing didn't fix the problem. To this day I've no idea what the issue could have been, as I am 1000% positive that the basic settings like IP/subnet were identical before and after. It really was beyond frustrating and annoying since I spent 5+ hours on it before I got to the point of re installing. That box is now running like a champ for a 120 user company in the transportation industry, serving out vpn connections and all. :) So don't let this discourage you...
-
I had this once on a fresh install. I re-assigned interface in the console, tried to re-start the web interface in the console without success. Then I simply did a fresh install and the problem was solved…
-
"LAN interface IP is 10.0.0.1"
Why are you changing the lan IP during the install process? When did you change it to that.. Did you restart the web from console. I would suggest fresh install.. Let it come up on default which would be 192.168.0.1 I believe - and then try and get to the web gui. Once you finish the setup then try changing the IP of your lan interface on pfsense to your 10 address you want.
-
I agree. There have been issues with changing the LAN subnet during initial install, though I've never seen that personally. The symptoms seem to indicate the webserver is not listening/responding on the correct address/port for whatever reason. It may be possible to diagnose that but it's probably easier to re-install to the standard values and then change it later as John suggests.
Steve
-
Hi Guys
Terribly sorry for not getting back sooner, I've been away.
I've taken some photos of my setup
As you can see
WAN is set to UE0 interface with IP 192.168.16.204
LAN is set to UE1 interface with Default IP 192.168.1.1
The RED cable is WAN connection
The BLUE cable is LAN connection, it connects to a switch. My notebook connects to the same switch.
The notebook gets IP from PFSense DHCP with the range from 192.168.1.100 - 192.168.1.150
I can select option 7 from PFSense console to ping my Laptop.
As you can see on my notebook screen .. I can also ping the PFSense box, but when I tried the Web Config page 192.168.1.1, I get the error message, if you look closely to the browser tab, you can actually see the PFSense logo.
Any idea what might have caused this? The notebook firewall has been switched off to make things easier.
Thanks in advance
-
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…
-
Yeah. More likely some software firewall or antivirus or ? on the windows pc.
-
You will notice that the connection just kind of dies.. Not only do you see retrans from pfsense you call see retrans from .100 to .1
It is not answering dns queries either..
Juts for be complete - how you would verify the mac your pinging is to look in your arp table on the .100 box
So
C:>arp -a
Interface: 192.168.1.100 –- 0xc
Internet Address Physical Address Type
169.254.7.80 00-26-24-08-8a-ed dynamic
169.254.82.185 00-1c-c3-09-05-7a dynamic
192.168.1.3 00-0c-29-c8-f2-dc dynamic
192.168.1.7 00-0c-29-dd-02-ba dynamic
192.168.1.8 00-0c-29-55-4f-95 dynamic
192.168.1.40 00-1f-29-54-17-14 dynamic
192.168.1.97 00-26-24-08-8a-ed dynamic
192.168.1.98 00-1c-c3-09-05-7a dynamic
192.168.1.99 00-06-dc-43-ad-78 dynamic
192.168.1.253 00-0c-29-1e-18-ae static
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
239.255.255.250 01-00-5e-7f-ff-fa staticYou notice from my workstation that is the mac I saw on my ifconfig..
Your sniff is odd.. You see 3 different connections to 80.. And yes you see the syn-ack back, but you never send ack? And actually start the conversation.. And then you just see a bunch of retrans
You see retrans from pfsense sending his syn-ack because he never got back the ack.. And you see .100 sending back his syn because seems he thinks he never got the syn-ack.
Need to figure out why your client .100 did not send back ACK to the syn-ack he was clearly sent and seen by wireshark for the 3 different connections you tried to create to http (80)
Do you have another client you can try?
-
MACs will also be in your wireshark captures.
-
yeah in there it looks right
to where he is sending the request for 80
-
Are these captures taken on .1 or .100?
It makes a difference because if from .1 we know the SYN-ACK was sent, but not that it was actually received. If from .100 we know it was sent and received.
-
Have to assume it is taken on .100
Since he states
"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"I doubt he installed wireshark on the pfsense box ;)
-
Hi Guys
I want to isolate the problem, so I grab an old desktop, put an extra NIC in it and install PFSense.
Notebook, Cables, is the same, only difference here is the pfsense box.
Once installation finished
Everything works as it should, I can go to Web Configurator, i can access external internet.
So …
For some strange reason.. pfsense doesn't like those USB to NIC adapters, even though you can ping it.
So disappointed as I really want to use those Intel NUC for pfsense.
Thanks so much for the help, really appreciated. :)
-
Hey - I like your pfsense you made with the old computer. Thats not bad actually.
I bet it can handle whatever you need to throw at it also.Low power and small is nice, but that one might be pretty trouble free also assuming you can blow out the fans every 6 months or so.
Not sure whats up with the USB NICs - It crossed my mind that they may not be getting enough power from the usb port?
Not sure? -
The USB NICs certainly look like the issue then. Weird that you can ping just fine though.
Not sure why we haven't suggested this before but try disabling any hardware offloading options. Looking back at your ifconfig output the nics both claim to support checksum offloading. If that's not working I guess it would explain it.Steve
-
How do I disable hardware offloading?
I'll willing to give it a try :)
-
System: Advanced: Networking
-
Not helpful when you can't access the webgui. ;)
You could maybe edit the config file. There's probably a way to do this from the developer shell, but I'm not sure what it might be.
You can probably do it temporarily from the command line. Something like:ifconfig ue1 -txcsum -rxcsumI imagine that will get reverted when the config is reloaded though.
Steve
-
Duh. Catch 22.
Those CLI changes might not stick but if they work the GUI should be accessible and the permanent changes saved.
-
Not helpful when you can't access the webgui. ;)
You could maybe edit the config file. There's probably a way to do this from the developer shell, but I'm not sure what it might be.
You can probably do it temporarily from the command line. Something like:ifconfig ue1 -txcsum -rxcsumI imagine that will get reverted when the config is reloaded though.
Steve
I happened to be doing the exact same config (Love the Intel NUC!!!). I was also using two USB NICs, and had the exact same issue. Disabling checksum offloading as show above fixed it!!!!
Thank you!
