LAN NIC not installing?
-
Hi, I'm working on my first install.
I have 2 NIC's in the computer, which will be used as a firewall perimeter.I installed off the DVD, and connected the WAN when prompted and this worked.
I then connected the LAN when prompted and this doesn't work?I'm not clear on the cabling so some help might fix the issue.
I have a cable modem connected to a router.
I unplugged the modem Ethernet cable from the router's WAN and connected to the computer's 1st NIC.
I then added a new Ethernet cable into the 2nd computer NIC and plugged into the router's WAN. (this is supposed to be for the pfSense LAN NIC if I'm correct). -
Some NICs do not work well with the autodetect script for whatever reason. It's only there in case you have multiple identical NICs and need some way of identifying them. Since you know which one is LAN (the only one left!) just enter it manually. The available interface names are listed just above that prompt.
Adding the router on the LAN side on pfSense may cause some problems. Are you doing that because it provides wifi?
https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense
pfSense will use the 192.168.1.* subnet for it's LAN and there's a good chance your router might be using that also. If that's the case it will break routing so you'll need to change one of them.Steve
-
Thanks for the reply.
So, I reinstalled and saw the Interface name.
Only re0 is shown, for the MOBO NIC.
The PCI NIC isn't found, but when I plug an Ethernet cable into the PCI NIC, the green LED shows activity.
So I entered the WAN name of re1 and I have no name to enter for the LAN.Also, I'm not clear on the cabling yet. I simply use the cable modem to the computer WAN so traffic will flow through the computer and then connected a LAN from the computer to the router, so my network devices receive Internet.
Yes, the router is Wi-Fi aswell which is needed for some Wi-Fi devices.Well, I think I need to find out why pfSense isn't finding the 2nd NIC, then research the cabling again, unless someone has some ideas?
-
I changed the ASUS NIC which was faulty with a working NIC.
The new NIC is found by pfSense installer.
I enter the WAN address re0 which works.
I enter the LAN address re1 and receive the error:I now get the results: re0 00:1f:1f:32:eb:60 (up) re1 6c:f0:49:1f:68:30 (down) RealTek 8169SC/8110SC Single-chip Gigabit Ethernet
I can assign the WAN address re0, when I assign the LAN address re1, pfSense installer gives the error: uhub_reattach_port: giving up port reset - device vanished
Enter the Optional 1 interface name or 'a' for auto-detection (or nothing if finished): uhub_reattach_port: giving up port reset - device vanished -
Okay, so I tried a PS2 keyboard connection and error: uhub_reattach_port: giving up port reset - device vanished continues.
I can still enter the WAN address: re0.
I can still enter the LAN address: re1.pfSense installer then says:
Enter the Optional 1 interface name or 'a' for auto-detection (or nothing if finished): uhub_reattach_port: giving up port reset - device vanished.I can't remove any USB hubs as the keyboard and mouse is USB.
I tried with a PS2 keyboard and mouse, but the computer doesn't read it.I can't access the BIOS?
-
Okay, so managed to enter WAN and LAN address of re0 and re1 respectively.
Still receive error: uhub_reattach_port: giving up port reset - device vanished
I would like to use the GUI by accessing pfSense's IP address from another computer in the LAN.
How do I set pfSense's IP address? -
Ok, so entered in WAN and LAN IP address, subnet and default gateway, but no success.
What do I do?My basic topology is:
Cable modem: 192.168.0.50
Ethernet to pfSense's WAN IP 192.168.1.2, Subnet 255.255.255.0/24, Default gateway 192.168.0.50.
pfSense's LAN to router, LAN IP 192.168.1.1, Subnet 255.255.255.0/24, Default gateway 192.168.1.180.
Router: IP 192.168.1.180.
Ethernet cables to LAN network. -
The WAN interface should be set to DHCP since it's receiving an address from the cable modem.
The LAN interface should not have a gateway set. The pfSense box itself does not have gateway on LAN, it acts as a gateway for other devices.Steve
-
Ethernet to pfSense's WAN IP 192.168.1.2, Subnet 255.255.255.0/24, Default gateway 192.168.0.50.
That cannot work - 192.168.1.2/24 is not in the same subnet as 192.168.0.50
pfSense's LAN to router, LAN IP 192.168.1.1, Subnet 255.255.255.0/24, Default gateway 192.168.1.180
As Stephen said, you do not put a gateway on the pfSense LAN - pfSense is supposed to be routing the internet traffic out the WAN - to the WAN gateway.
pfSense WAN and LAN must be different subnets. So you have to decide which to keep as 192.168.1.0/24 and which to make a different subnet.Router: IP 192.168.1.180
I am guessing that your old router is also a WiFi device. It probably has a WAN port, some LAN ports and WiFi antenna/s. You do not use it as a router any more. Just use it as an ordinary WiFi device by:
- Disable DHCP on it (you want your LAN clients to get DHCP from pfSense)
- Set its IP address to be something in the pfSense LAN subnet (so you can manage it)
- Connect a cable from one of its LAN ports to pfSense LAN. (This will put it on the pfSense LAN subnet as an ordinary device providing WiFi)
-
Thanks for the reply.
So, it seems pfSense's WAN DHCP won't receive an IP address from the modem?I have plugged the modem's LAN cable to pfSense's WAN port.
I selected pfSense's option 2) Set interface(s) IP address, and selected DHCP for WAN.pfSense shows:
WAN (wan) -> re0 ->
LAN (lan) -> re1 -> v4: 192.168.1.155/24I can't ping the LAN from my network either which I through would work?
I tried pfSense's LAN into the router's WAN and LAN port and same result.
Here are my current settings:
Cable COAX > Modem WAN > Modem LAN > pfSense WAN > pfSense LAN > router LAN1 (tried router WAN but doesn't work) > router LAN2 > network.
Modem:
WAN IP: xxx.xxx.xxx.xx
WAN Subnet Mask: 255.255.240.0.
WAN Default Gateway: 124.191.160.1.LAN IP: 192.168.0.50.
Subnet Mask: 255.255.255.0.
DHCP Server: Yes.
Starting IP Address: 192.168.0.2.
Ending IP Address: 192.168.0.254.pfSense:
WAN set to DHCP.
WAN subnet must be different to LAN subnet.
Subnet unknown and needs to be for modem.
Web GUI: http://dhcp/LAN IP address: 192.168.1.155.
Subnet: 255.255.255.0/24.
Default gateway: none.
Web GUI: http://192.168.1.155/Router:
Disable DHCP server.
IP address: 192.168.1.180.
Subnet: 255.255.255.0/24.
Update Gateway from 192.168.1.180 to 192.168.1.155 (pfSense LAN is now gateway).Any ideas?
-
LAN IP: 192.168.0.50.
Subnet Mask: 255.255.255.0.
DHCP Server: Yes.
Starting IP Address: 192.168.0.2.
Ending IP Address: 192.168.0.254.Where is the above set? On the modem? The modem should not have such settings unless it's a modem-router combined. Where ever it is the DHCP range includes it's own address so that may be stopping it run.
If that's the pfSense LAN address then you have two sets of values for it. ???
In the router configuration you have changed a 'gateway' setting from 192.168.1.180 to 192.168.1.155. The only place that should be using 192.168.1.180 as a gateway is the DHCP server settings. Since you have disabled DHCP it shouldn't make any difference.
You will probably have to reboot your modem in order for it give out a public address to the pfSense WAN interface which will have a different MAC to your router.
Are your LAN clients receiving an IP address from the pfSense dhcp server?
Steve
-
Cable COAX > Modem WAN > Modem LAN > pfSense WAN > pfSense LAN > router LAN1 (tried router WAN but doesn't work) > router LAN2 > network.
You really don't need (or want) that old router at the back-end in the chain. You want your private network directly attached to pfSense LAN:
Cable COAX > Modem WAN > Modem LAN > pfSense WAN > pfSense LAN > network.Then, if the old router was also providing WiFi for you, turn it into just a WiFi access point on your pfSense LAN network - plug its LAN into the pfSense LAN network, give it a LAN IP address, switch off DHCP on it, tell it pfSense LAN IP as its gateway (if you like or care - it does not really need a gateway if you just manage it from the pfSense LAN). Do not plug anything into its WAN port.
Also, from your description and as Stephen says, we assume that "Modem WAN > Modem LAN" is actually a routing device (it has a private IP on its back-end facing pfSense WAN, and routes (and NATs) private to public.)
-
Yes, the above questioned settings are the LAN settings on the cable modem, which is a cable modem/router.
My router has the static IP 192.168.1.180. I have set all my network devices with static IPs which makes it easy for me to manage the network.
So, no, my LAN clients aren't receiving an IP address as I have set most of them with static IPs.I am keeping the router because of Wi-Fi and also because of the ports available. I also have a switch connected to allow for all the devices. Cable COAX > Modem WAN > Modem LAN > pfSense WAN > pfSense LAN > router LAN1 (tried router WAN but doesn't work) > router LAN2 > switch > network.
So, if I remove the router, I will lose ports and need to buy a bigger switch.This begs the question in my mind…if the router is gone and there's only a bigger switch, where is the Wi-Fi which is still needed.
I will work on the Wi-Fi being managed from pfSense as this sounds good.
-
Ah, OK. The picture becomes clearer. :)
You can continue to use the wifi router as a wifi access point and as additional switch ports but you should have it configured as described in my first post here. You don't want it doing any routing or handing out IPs. I'm still not sure where you changed the gateway from 192.168.1.180 to 192.168.1.155. If that was in the wifi router it makes it makes no sense that it would have been using itself as a gateway.
If the cable modem/router is running a dhcp server it should be handing an IP to the pfSense WAN interface. Can you connect a client machine to it to check that the DHCP is working? Ideally you should configure your modem/router in bridge mode so that your public IP gets passed to the pfSense WAN but we can work on that later.
What settings do your client machines have that are failing to connect to the pfSense webgui on LAN? Can you ping the LAN interface? What is the response when you try?
Steve
-
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