LAN NIC not installing?
-
Yes, I have setup the Wi-Fi router as per your post https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense
I changed the gateway IP from 192.168.1.180 to 192.168.1.155 in the Wi-Fi router.
The Wi-Fi router had 192.168.1.180 as part of the Wi-Fi router network setup which worked before pfSense.
I changed the Wi-Fi router's gateway IP to 192.168.1.155 as the Wi-Fi router now connects and goes to the pfSense LAN interface with IP 192.168.1.155.The modem is issuing IPs with its DHCP server on.
The client machines ping each other via the Wi-Fi router fine until I try the pfSense setup.
Most client machines have static IPs for easier management.Still not working, so maybe the Wi-Fi router needs the IP checked. I still need to reboot the modem too.
-
Can the modem operate by itself or does it always require the wifi router (or some other router like pfSense) behind it?
Seems strange that it would be handing out IPs just fine to other devices and not pfSense. :-\ Try rebooting it.I think the wifi router is just confusing things here. Try just connecting your switch to the pfSense LAN and your client to the switch. Add the wifi router back once you have successfully connected to the webgui.
All this would be explained by the WAN and LAN interfaces being mixed up. I realise you have said you checked that but are really sure. ;)
Steve
-
So, I'm not quite clear.
On the Wi-Fi router, I have the settings:
Local IP Address: 192.168.1.180
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.155Is the gateway correct?
-
Yes, if those are the WAN settings.
However if that's true then it makes no sense that the gateway was previously set to 192.168.1.180.
Also if you have it behind pfSense you should not have anything connected to the wifi routers WAN port so the gateway shouldn't matter. You connect the pfSense LAN interface (perhaps via your switch) to one of the the wifi routers LAN ports. That way the wifi router is no longer doing any routing that could be potentially causing a problem. It's acting purely as a wifi access point and a switch.You still haven't managed to connect to the pfSense webgui? It should not be this difficult! ;)
Steve
-
Thanks, okay, so the Wi-Fi router connections were right according to the forum threads.
Still no connection and no Web-GUI.I am now having the optical drive go weird and keeps booting the CD.
I even changed the BIOS to boot from HDD and not optical drive, but still boots and reinstalls from DVD.Now the install goes through the quick setup and then freezes with error:
Writing configuration…Perhaps I should have the modem LAN connected to the pfSense WAN, but I thought it should still install?
I'm thinking of downloading the pfSense OS again in case I downloaded a buggy OS? The USB install won't work either, which makes for an inconvenience burning onto DVD again.
-
Yes you should still be able to install with nothing connected to WAN. It will take longer to boot with no WAN connection, sometime a lot longer.
Are you installing to a HD? Failure to write the configuation is not good. Is the HD known to be good?
Why did you still have the DVD in the drive? Just remove it after install.Steve
-
Okay, so I bought a new motherboard, CPU, NIC and optical drive.
Install ok and WAN and LAN IPs are found and I can ping pfSense's LAN from another computer.
However, I still can't eject the DVD, so each reboot reinstalls the system?
I suspect this is a problem with pfSense and this is the 2nd motherboard and optical drive with the same issue.
Any ideas how to fix this?
Yes, I have manually removed the DVD and reset the BIOS to boot from the storage drive, however the boot just looks for the optical drive to boot from?My network was unable to ping outside the WAN, so this probably means I need to configure pfSense's WebGUI now. Looking for a good link for a configuration.
-
Ok, the DVD thing is weird. Usually the drive ejects when the system restarts after the install.
Are you actually installing or just booting the live DVD? If you're just running live it won't write to the HD adn won't eject the disk.Steve
-
I was installing with the pfSense default options which was booting off the LiveDVD.
I have not pressed the option 'I' to install to the storage disk, however the install gets stuck at 36% each time?I've just downloaded the pfSense OS again in iso.gz format.
I will try decompressing, burning and installing off a new DVD. -
Okay, new DVD download pfSense-LiveCD-2.1-RELEASE-i386-20130911-1815.iso installs to storage disk and same freezing error:
Executing Commands
/usr/local/bin/cpdup -vvv -I -o /usr /mnt/usr
[- 36%] -
Well, pfSense finally installed completely, without any changes after the install kept sitting at 36%.
Working out how to configure pfSense via GUI as only LAN access and no WAN access yet.
Suddenly, pfSense's monitor went black and unable to ping pfSense, but can ping LAN still.
Tried reboot but same issue?.
Checking if hardware is fried:
CPU fan ok.
Keyboard ?
LAN NIC ok.
Mouse ?
Optical drive ok.
PSU fan ok.
SSD ?
VGA monitor ?
WAN NIC ? -
Getting stuck at 36% is unfortunately quite common in specific hardware. Some people have reported it will eventually install if you just wait otherwise there are work-arounds. See mine and JimPs comments in this thread:
https://forum.pfsense.org/index.php/topic,71941.0.htmlThe monitor suddenly going black sounds like some sort of hardware failure. There is no facility to disable the screen in pfSense. In fact some people have deliberately tried to do that but never really succeeded.
Does it still show anything at boot?Steve
-
Thanks for the link.
Finally installed pfSense to storage disk.Re no monitor, it's totally dead on boot nothing.
I think the 2 x 2GB DDR3 RAM might be blown as I've tested all the other hardware up to this point.No spare DDR3 RAM to test so might have to buy some tomorrow.
Is there a minimum re RAM. Seems coincidental that all this hardware I'm going through is breaking upon the pfSense install?
-
Well, was going to pull apart piece by piece the computer to find the problem…tried one lucky boot and it worked.
Seems a rest of 5 hours helped the boot work.So, now back in pfSense GUI and can ping LAN, but not WAN.
I setup pfSense Setup Wizard, but not sure and something not right with settings?
-
Ok well now you're getting somewhere. :)
You'll probably have to consider the hardware suspect until you find the fault. If you could still ping the LAN interface after the video went black I would first suspect the video hardware, either the monitor or the graphics card.Ok so you can't ping the WAN interface. Do you mean the WAN IP itself or the router on the WAN side?
Is the pfSense WAN interface receiving an IP from the WAN router via dhcp?Steve
-
Yes, maybe the video card, but can't confirm yet.
I've run some traceroute tests and LAN doesn't seem to go past the Wi-Fi router.
Should go to the Switch > Wi-Fi router (192.168.1.180) > pfSense LAN (192.168.1.155) > pfSense WAN (DHCP currently 192.168.0.2) > cable modem LAN (192.168.0.50) > cable modem WAN (WAN IP) > Internet.$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.1.180 (192.168.1.180) 0.241 ms 0.344 ms 0.418 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 192.168.0.4 (192.168.0.4) 1114.118 ms !H 1114.127 ms !H 1114.123 ms !H$ traceroute www.google.com
www.google.com: Name or service not known
Cannot handle "host" cmdline arg `www.google.com' on position 1 (argc 1)$ traceroute google.com
google.com: Name or service not known
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1) -
Can you ping from a client that is not on WIFI?
The WIFI should be wired to one port on the switch and the Switch connected to pfSense LAN.
Is your WIFI in Router mode or just an Access Point?
-
Yep, those things.
We have been over so much now that I'm confused as to where we are. :-
Perhaps you could detail exactly what you have connected and what IP details you're using, dhcp etc.What is 192.168.0.4?
The fact that the first hop is 192.168.1.180, your wifi router, is bad. Your clients should be sending traffic directly to pfSense not via the wifi router.
Steve
-
Well I can ping everything on the LAN that is wired. The WiFi is down.
I reconnected the Wi-Fi router (192.168.1.180) to the Switch and the Switch to the pfSense LAN (192.168.1.155).
The WiFi router is in AP mode.
I noticed the WiFi router's WAN Connection Type is Automatic Configuration - DHCP. Maybe this WiFi WAN should be set to a static IP of 192.168.1.155 (pfSense's LAN IP)?
I rebooted the WiFi router and the WiFi WAN IP is 192.168.0.4.WiFi router details:
Network Setup DHCP disabled. (Maybe this is the LAN settings). -
The WiFi router is in AP mode.
I noticed the WiFi router's WAN Connection Type is Automatic Configuration - DHCP. Maybe this WiFi WAN should be set to a static IP of 192.168.1.155 (pfSense's LAN IP)?
I rebooted the WiFi router and the WiFi WAN IP is 192.168.0.4.WiFi router details:
Network Setup DHCP disabled. (Maybe this is the LAN settings).Glad that the Router is in AP mode and you have it wired to the switch.
In the WIFI setup, You can ignore the WAN setup as you put it into AP Mode.
–------------
The Cable Modem connects to the pfSense WAN interface (If its DHCP it will give the address to pfSense you dont need to worry about it)
The LAN interface you must set this to a different address than the WAN. So for example use 192.168.1.1, mask 255.255.255.0 (/24 Subnet)
So now you must ensure that all devices on your network share the same 192.168.1.X addressing. (/24 Subnet)
Connect a cable from pfSense LAN and connect it to one of the ports on the Switch
–------------
Now connect a network cable from the switch to one of the LAN ports of the WIFI (Set to AP Mode). DO NOT CONNECT anything to the WAN port of the WIFI unit.
Set the WIFI LAN address to 192.168.1.2, 255.255.255.0.
–------------
Setup DHCP on pfsense and Disable DHCP on the WIFI.
