New install - no browser menu or internet communication
-
Ah, this is good!
So what is the client computers IP address currently? I assume you entered that directly?At that prompt enter 'y' and then set a range of addresses you want to use for clients. Since you only have one client this is not important. Assuming the LAN is still 192.168.2.1/24 you could use:
Start address: 192.168.2.11
End address: 192.168.2.20This allows for up to 10 clients, you can change that at any time later though.
Now in order for this to make any difference you need to set the cleint computer to obtain it's IP address automatically via DHCP. Is it a Windows box?
Steve
-
Yes, Win7 box.
I'm unsure about how to answer your question of setting the client IP address. As far as I know, that was automatic. I didn't set anything.
The LAN is still 192.168.2.1
I can get to the modem configuration via 192.168.1.1 and it lets me set address and submask. No DHCP.
-
Found the client DHCP settings through 192.168.1.1
DHCP: On
Beginning IP Address: 192.168.1.64
Ending IP Address: 192.168.1.254
Subnet Mask:255.255.255.0
Lease Time: 86400
Domain Name: domain_not_set.ir
DNS Dynamic or Static (Dynamic selected)
DNS Server 1: Blank
DNS Server 2: Blank -
Windows by default is set to obtain an IP address via dhcp so if you haven't changed that and manually configured an address it should get an address from pfSense in the specified range. You may have to trigger it to ask for an address though by disconnecting/reconnecting the cable or rebooting. If it fails to find a dhcp server Windows will assign itself an address in the form 169.254.X.X. This is bad!
The modem is working fine, handing an address to pfSense, so don't change anything there. An interesting point though is where are you accessing the modem from? If it's from the Win7 machine through pfSense then you should be good to go.
Steve
-
I've set the pfSense address range per your directions. Should I reboot both boxes now?
-
You shouldn't need to reboot the pfSense box (almost ever!) but if you do make sure it's up and running before the windows box tries to get it's address.
You said you could ping the client computer earlier. What address were you pinging it on?
Steve
-
xxx.13.128.32
Not that I don't trust the folks here. Just policy. ;)
-
Hmm, now I'm confused. :-
I assume that is a public IP which is why you have sensibly redacted part of it. How did your Win7 machine get that address?Steve
-
How did your Win7 machine get that address?
Maybe it didn't. Maybe xtek was pinging that address and thought the response was coming from the windows machine.
-
When I hook up the firewall cables to the modem and Win box, I don't have any internet. So to post here, I have to disconnect from the firewall LAN and plug back into the modem. Then I can post here and determine my IP.
Hope that's not a problem.
-
I'm running a Firefox addon that shows my windows box IP, and I verified it through a online tool too.
-
I'm looking at getting 2 of these cards from eBay to replace the antique ones I'm using now. Any thoughts?
Intel PRO/100 S PCI RJ-45 Fast Ethernet Network Adapter LAN Like New PILA8460C3
And - is a crossover adapter as functional as buying a crossover cable? It's a lot cheaper and I've got extra Cat5e cables.
-
I'm running a Firefox addon that shows my windows box IP, and I verified it through a online tool too.
That might show the user's view of your IP (the public IP of your modem) rather than the actual IP of your computer. Because of the limited number of IPv4 addresses most home users access the Internet through a NAT (Network Address Translation) box so the private IP addresses space (192.168.0.0 to 192.168.255.255 among others) can be reused.
In Windows start a command prompt window and give the command```
ipconfig -
Sorry about that. All this IP/WAN/LAN stuff is mostly new to me. Ipconfig says 192.168.1.64.
It sounds like we're back to a problem with one or both of the cards I'm using. I'm going to order a couple replacements tonight and we'll try again when they come in. wallabybob, I do appreciate the input you and stephenw10 have given me.
Xavier
-
Sorry about that. All this IP/WAN/LAN stuff is mostly new to me. Ipconfig says 192.168.1.64.
Is that with the Win7 box connected to the modem?
It sounds like we're back to a problem with one or both of the cards I'm using. I'm going to order a couple replacements tonight and we'll try again when they come in.
Lets get your pfSense configuration right first. There are a few important details that are unclear to me. Have you changed your pfSense LAN interface to 192.168.2.1/24 with DHCP enabled? Did you reboot after that change? (It has been my experience a reboot is sometimes necessary for a "major" configuration change to take effect.) If you then connect your Win7 box to the pFsense LAN interface does it get an IP address in the DHCP range you configured? If not, what address does it get?
-
Ah! This is making a lot more sense this morning. :)
Steve
-
Is that with the Win7 box connected to the modem?
Yes
Have you changed your pfSense LAN interface to 192.168.2.1/24 with DHCP enabled?
Yes
Did you reboot after that change?
Yes
If you then connect your Win7 box to the pFsense LAN interface does it get an IP address in the DHCP range you configured?
Yes, 192.168.2.11
-
If you then connect your Win7 box to the pFsense LAN interface does it get an IP address in the DHCP range you configured?
Yes, 192.168.2.11
Good. You must have physical communication between your Win7 box and the pfSense box.
On the Win7 box, in a command prompt window, please type the following commands in turn and report if you get a ping response. If there is no ping reponse please report what ping reports:```
ping 192.168.2.1
ping 8.8.8.8
ping www.google.comThese will help determine if you have basic connectivity to the Internet and if you have a correctly configured Name Server. -
I just refreshed all the LAN/WAN settings we've discussed, rebooted, and… success! pfSense is running and I'm able to access the browser menu and have internet access.
-
Now that I can access the browser menu, do you guys have any recommendations on a setup guide? I've watched a couple YouTube videos but they seemed more oriented toward networked systems.
Thanks a bunch. I'd never have figured all that stuff out.
