Issue accessing Web GUI on specific IP

[bronaldo]

Hi, I've run into an odd issue.
I tried to access the pfsense web access today and had the page time out. I could ping the IP fine, and internet, captive portal and all was well. When changing the interface IP to another IP[192.168.1.2/192.168.1.3, the web access works fine but it specifically will not work on 192.168.1.1. I could probably just change the interface IP and reboot everyone but I currently have people working on the machines.

I was playing around with virtual IP's before, trying to make a WAN IP 192.168.0.1 accessable to my LAN although I deleted the changes I made and the web access was working the whole time. The problem started a few hours later.

Any ideas?
Thanks.

[wallabybob]

@bronaldo:

the web access works fine but it specifically will not work on 192.168.1.1.

Perhaps you have multiple systems with IP address 192.168.1.1.
Perhaps you are attempting the wrong type of access (e.g. http:// instead of https:// or vice versa).

The browser report on the access attempt would be more informative than the executive summary "will not work".

[bronaldo]

Sorry, here is some more information.
Chrome gives me this error when trying to access 192.168.1.1: Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out. I have tried both http and https

If I change the interface IP to another address, it works fine on that IP. There is no ping response to 192.168.1.1 when I do this. Nmap doesn't see anything either. Is there any other information I could provide? I might try loading a previous backup of the virtual machine and see if that resolves the issue.

[doktornotor]

Flush the states or reboot.

[bronaldo]

Rebooting does not resolve the issue. :(

[wallabybob]

@bronaldo:

Rebooting does not resolve the issue. :(

Just to clarify the context: You rebooted with IP address of pfSense LAN interface set to 192.168.1.1? Attempted web access to 192.168.1.1 timed out? Ping to 192.168.1.1 timed out?

Diagnostic questions:
What is the IP address, netmask and default gateway of the system from which you attempted these accesses? What is shown for a traceroute [Unix/Linux] or tracert [Windows command prompt] to 192.168.1.1? If the accessing system is on the same IP subnet as 192.168.1.1 What is the output of command```
arp -a

What is the output of pfSense shell command```
ps ax | grep http
```(Perhaps the web server is not running after startup and restarts correctly when you change IP address.)

[bronaldo]

Yes, rebooted with 192.168.1.1 and web access times out. I can ping 192.168.1.1 fine though, and get 100% response. The same scenario is across all PC's i've tried through. The PC i'm currently using is 192.168.1.112.

Tracing route to brozone.home [192.168.1.1]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms  brozone.home [192.168.1.1]

The mac address is also correct [cadmus is what virtualbox identifies as]

Starting Nmap 6.01 ( http://nmap.org ) at 2013-06-28 00:06 Pacific Daylight Time
Nmap scan report for brozone.home (192.168.1.1)
Host is up (0.00051s latency).
Not shown: 96 filtered ports

PORT     STATE SERVICE
53/tcp   open  domain
80/tcp   open  http
3128/tcp open  squid-http
8000/tcp open  http-alt
MAC Address: 08:00:27:19:90:88 (Cadmus Computer Systems)
Nmap done: 1 IP address (1 host up) scanned in 1.93 seconds

I am quite baffled at what it may be.

[bronaldo]

since I'm under a tight deadline, and it is out of business hours here and I have a relatively small amount of machines here, I have refreshed all the PC's and they are all using the new gateway, 192.168.1.2.

This is a hotfix that has worked for me, hopefully I this will not be an issue anymore, but it is an odd one at least.