Testing from inside my router, no web interface
-
New install. I've searched, read, and watched videos for two day before posting the following question. I didn't want to post, but searching for an answer is not working for me.
I didn't want to take my current home network down while I played around with pfSense so I connected the Wan side to a switch, and the lan side to my MacBook. I was hoping to get to the web interface and start learning the software. So far I can't access the web interface from my MacBook. My home nrtwork should assign an address of 10.0.1.50-99, from my pfSense box it shows anaddress of 192.168.100.27/24 on the Wan side and 192.168.1.1/24 on the Lan side. I set my MacBook to 192.168.1.2, but I'm not able to connect to the web interface.
Hardware wise I'm using a Dell Dimension C521 (AMD64), integrated nic for Wan, and Intel pro 1000 for lan nic. I'm surprised of the Wan ip address, but I feel I should be able to establish a web connection to the pfSense box even if I can't reach the internet. All nic's have been autodetected.
current network:
Comcast -> zoom cable modem -> apple airport extreme (dhcp) -> switch (basement) -> switch (office) -> Wan side pfSense -> lan side pfsense -> MacBookAny thoughts? I believe once I can establish a connection, I'll be able to work through the configuration.
-
How is pfSense receiving an IP address in a completely different subnet? Do you have a rogue DHCP server on your network?
Still, as you say, it shouldn't stop you accessing the webgui on LAN. Have you set a gateway and DNS server on the macbook? How are you trying to access the webgui? Can you ping the LAN interface?Is there some reason you didn't use DHCP on the LAN interface?
-
I've been having issues with my Airport Extreme and DHCP addressing, that's why I'm looking at pfSense to take over that role. I do have two Airport extremes in my network, the 2nd is bridged for access point only. I removed the 2nd Airport extreme to eliminate the possibility of it assigning an address.
I disabled the internal NIC on my Dell Dimension C521 and I'm trying two Intel pro 1000 NIC's. I now have the Wan side plugged in after my Airport Extreme, and the cable is routed between two switches, one in basement by router, and one in my office.
After rebooting and detecting NIC's the WAN side shows no IP address, and the LAN side show 192.168.1.1/24. Tme MAcBook connected to the lan side via DHCP is not showing a connection since the ip address is 169.254.140.87. The Dell used to have win/xp on it, maybe I'll run a live version of Unbuntu to verify NIC's and internet access.
The MacBook when pinging 192.168.1.1 timeouts.
My plan is when I have pfSense working it to replace the remaining Airport extreme with a couple of wireless access points that support dd-wrt.
-
I verified the cable to my MacBook by plugging into my switch. Next I'll check the pfSense box, but since it ran xin/xp for years, I hope it is fine. Maybe it's the new nic's.
-
I'm having some type of hardware issue. All nic's are not getting a proper address from my Airport express DHCP. I should get a 10.0.1.x address and I'm getting a 192.168.100.xx address. I loaded Unbutu live on y Dell and these are my results. Not sure if this hardware can be saved.
-
I loaded win7. I got both Intel Gigabit CT desktop adapter's to work after a driver update. The card states support under FreeBsd version 9. I'll download current Intel drivers unto a flash drive. I've never installed drivers while running pfSense, but that is what google is for. The process continues!
-
Those cards should work fine with pfSense 2.1. You could try a 2.1.1 snapshot which have newer drivers but it shouldn't make any difference.
Loading new drivers in pfSense is not straight forward. ;)Steve
-
I moved pfSense to an intel based box, and everything in pfSense worked fine.
I still have a problem with my Apple Airport Extremes, but tonight I'll do a factory reset. I hope to use one extreme as an access point.