Complete Noobie Question (SOLVED)

kycnotes

Installed pfSense onto my machine with the defaults being the following:

WAN: 192.168.254.2
LAN: 192.168.1.1

I plugged the lan connection directly to a machine and tried to access 192.168.1.1 to get to the Web GUI, but for some reason I am unable to reach this address. Can someone please inform me of what stupid mistake I am making?

Also, I noticed that my Speedstream modem has DHCP enabled, so should I disable this, set a static ip to something like the above?

Thanks in advance.

dreamslacker

@kycnotes:

Installed pfSense onto my machine with the defaults being the following:

WAN: 192.168.254.2
LAN: 192.168.1.1

I plugged the lan connection directly to a machine and tried to access 192.168.1.1 to get to the Web GUI, but for some reason I am unable to reach this address. Can someone please inform me of what stupid mistake I am making?

Also, I noticed that my Speedstream modem has DHCP enabled, so should I disable this, set a static ip to something like the above?

Thanks in advance.

If you connected your computer directly to the NIC of the pfSense box, did you use a cross cable or at least have MDIX capabilities on either of the network interfaces?

Also, did you configure a static IP on your client so that it is on the same subnet as the pfSense box? ie. An IP of 192.168.1.x other than 192.168.1.1

kycnotes

1.) No, I used a standard patch cable. Not a cross over.

2.) I do not want to setup a static IP for each machine, but want to use DHCP. I went to the network connections (XP) and remembered that I should be on the same subnet and tried to enter in an IP of: 192.168.1.100 on the test machine and went to enter the subnet mask of 192.168.1.0 like it said in the Wiki, but then I reach an error that the Subnet Mask "has to be contiguous".

johnvan

I'm a newb too so take this for what it's worth.
I just set my system up yesterday and I also have a speedstream modem (router)
I'm with bell sympatico.
I bridged the speedstream by going here http://192.168.2.1/brgmode.htm
Not sure if this is relevant to you but thought I'd post just in case.

dotdash

@kycnotes:

I do not want to setup a static IP for each machine, but want to use DHCP. I went to the network connections (XP) and remembered that I should be on the same subnet and tried to enter in an IP of: 192.168.1.100 on the test machine and went to enter the subnet mask of 192.168.1.0 like it said in the Wiki, but then I reach an error that the Subnet Mask "has to be contiguous".

192.168.1.0 is the subnet. The subnet mask would be 255.255.255.0
But anyway, if you had link on your network card plugged into the box, you should be able to go to the XP box and change the radio buttons to 'obtain address automatically'. The DHCP server on the pfSense machine should give you an IP.

wallabybob

@kycnotes:

1.) No, I used a standard patch cable. Not a cross over.

As discussed earlier, you MIGHT need a cross over cable to connect the transmitter of one side to the transmitter. A standard patch cable will connect the transmitter of each end to the transmitter at the other end and the receiver at each end to the receiver at the other end. This leaves both receivers with nothing talking to them, hence no communication.

Newer interfaces include some smart electronics that can switch over the receiver and transmitter, eliminating the need for a cross over cable.

Check the link status on the pfSense box. If its not "up" you should try a cross over cable. Most NICs have at least one LED to indicate status. If no LEDs are lit your link is almost certainly not "up". A more effective check is to check the link status from the shell in pfSense:

# ifconfig rl0

(where you should replace rl0 by the interface name.) If the status line says no carrier you have a cable problem, either a broken cable OR you need a cross over cable.

kycnotes

@wallabybob:

@kycnotes:

1.) No, I used a standard patch cable. Not a cross over.

As discussed earlier, you MIGHT need a cross over cable to connect the transmitter of one side to the transmitter. A standard patch cable will connect the transmitter of each end to the transmitter at the other end and the receiver at each end to the receiver at the other end. This leaves both receivers with nothing talking to them, hence no communication.

Newer interfaces include some smart electronics that can switch over the receiver and transmitter, eliminating the need for a cross over cable.

Check the link status on the pfSense box. If its not "up" you should try a cross over cable. Most NICs have at least one LED to indicate status. If no LEDs are lit your link is almost certainly not "up". A more effective check is to check the link status from the shell in pfSense:
# ifconfig rl0
(where you should replace rl0 by the interface name.) If the status line says no carrier you have a cable problem, either a broken cable OR you need a cross over cable.

I used ifconfig at the prompt and both interfaces are active. I can ping the outside, so the WAN works, just not the LAN connection to get to the Gui?

dotdash

@kycnotes:

I used ifconfig at the prompt and both interfaces are active. I can ping the outside, so the WAN works, just not the LAN connection to get to the Gui?

You can ping what from where?
Try some simple tests-

Plug your workstation into the LAN side of the pfSense box, plug the DSL router into the WAN interface on the pfSense box. There should be no other connections.
Check your workstation. Try ipconfig /all. Does it say DHCP enabled=Yes? Is your IP address 192.168.1.something? Can you ping 192.168.1.1?

kycnotes

@dotdash:

@kycnotes:

I used ifconfig at the prompt and both interfaces are active. I can ping the outside, so the WAN works, just not the LAN connection to get to the Gui?

You can ping what from where?
Try some simple tests-

Plug your workstation into the LAN side of the pfSense box, plug the DSL router into the WAN interface on the pfSense box. There should be no other connections.

Check your workstation. Try ipconfig /all. Does it say DHCP enabled=Yes? Is your IP address 192.168.1.something? Can you ping 192.168.1.1?

Did all of the above, and this is what I received:

DHCP Enabled: Yes
Auto Config: Enabled
Auto Config IP: 169.254.100.155
Subnet Mask: 255.255.0.0
Default Gateway: _________________

I obviously see that the Auto COnfig IP should be something like 192.168.1.___. So I assume that the Pfsense box is not sending the the proper DHCP info.

When pinging I can ping my domain name and google with no problem.

dotdash

@kycnotes:

Auto Config IP: 169.254.100.155
Subnet Mask: 255.255.0.0
Default Gateway: _________________

When pinging I can ping my domain name and google with no problem.

That makes no sense to me at all. You have no default gateway, but you can ping google?
What does a 'route print' from the XP box show?

kycnotes

@dotdash:

@kycnotes:

Auto Config IP: 169.254.100.155
Subnet Mask: 255.255.0.0
Default Gateway: _________________

When pinging I can ping my domain name and google with no problem.

That makes no sense to me at all. You have no default gateway, but you can ping google?
What does a 'route print' from the XP box show?

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 20 72 b8 f4 ...... BCM5701 Gigabit Ethernet #2 - Packet Scheduler M
iniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
  255.255.255.255  255.255.255.255  255.255.255.255               2       1
===========================================================================
Persistent Routes:
  None

dotdash

You meant you could ping google from the pfSense box, right? That XP box ain't goin' nowhere.
You should try connecting the LAN via a crossover or small switch/hub.

kycnotes

@dotdash:

You meant you could ping google from the pfSense box, right? That XP box ain't goin' nowhere.
You should try connecting the LAN via a crossover or small switch/hub.

Yes, that is what I meant. Currently I have the LAN connection going in to a hub and have the XP box running off of that Hub

dreamslacker

@kycnotes:

1.) No, I used a standard patch cable. Not a cross over.

2.) I do not want to setup a static IP for each machine, but want to use DHCP. I went to the network connections (XP) and remembered that I should be on the same subnet and tried to enter in an IP of: 192.168.1.100 on the test machine and went to enter the subnet mask of 192.168.1.0 like it said in the Wiki, but then I reach an error that the Subnet Mask "has to be contiguous".

1) Use a cross-cable or at least stick a switch/ hub in between if you only have straight cables.

2) If you did not configure the DHCP server during the installation, you need to set a static IP address for the client first. This will allow you to connect to the WebGUI and enable/ configure the DHCP server.
In your instance, you'll punch 192.168.1.100 for the IP address, 255.255.255.0 for the subnet mask and 192.168.1.1 for the gateway.
Ignore the DNS setting for now. You can revert the windows client to use dhcp once the pfsense box is configured properly.

kycnotes

Thank you,

That is what I did and I am now able to get into the webgui and go from there.

kycnotes

Ok, I am still not getting this thing to work fully. I was able to access the web gui, but I am still unable to access the web. I went through chapter 4 of the book (yes, i bought the book) and followed all of the tips and instructions, but still am having a problem.

In the general settings I left the hostname: pfsense and domain: local. I set my WAN connection to DHCP because I have a Speedstream modem/router which is set for DHCP. (I also configured PPOe using the connection credentials in the modem, but that didn't work either.)

I left the MAC address blank and left the gateway blank because of DHCP as well as the DHCP hostname.

I used the default Lan IP address of: 192.168.1.1, because I will not and never will need VPN access.

Does anyone have any advice as to what I am doing wrong? I would greatly appreciate any help.

Thanks

dotdash

@kycnotes:

In the general settings I left the hostname: pfsense and domain: local. I set my WAN connection to DHCP because I have a Speedstream modem/router which is set for DHCP. (I also configured PPOe using the connection credentials in the modem, but that didn't work either.)

I left the MAC address blank and left the gateway blank because of DHCP as well as the DHCP hostname.

When using DHCP, you should be able to select type: dhcp and leave everything else at defaults/blank.
Check status, interfaces. You may need to renew the wan ip. If the speedstream is giving dhcp, it's probably private, 192.168.something if so, you'll want to uncheck the 'block private networks' box on the WAN interface. To use PPPoE, you probably will need to change the speedstream to bridge mode.
I'm assuming you've used the DSL with a PC or something. Did you just get a dhcp address on the computer, or did you have to set up PPPoE to connect? pfSense will need to connect the same way.

kycnotes

@dotdash:

@kycnotes:

In the general settings I left the hostname: pfsense and domain: local. I set my WAN connection to DHCP because I have a Speedstream modem/router which is set for DHCP. (I also configured PPOe using the connection credentials in the modem, but that didn't work either.)

I left the MAC address blank and left the gateway blank because of DHCP as well as the DHCP hostname.

When using DHCP, you should be able to select type: dhcp and leave everything else at defaults/blank.
Check status, interfaces. You may need to renew the wan ip. If the speedstream is giving dhcp, it's probably private, 192.168.something if so, you'll want to uncheck the 'block private networks' box on the WAN interface. To use PPPoE, you probably will need to change the speedstream to bridge mode.
I'm assuming you've used the DSL with a PC or something. Did you just get a dhcp address on the computer, or did you have to set up PPPoE to connect? pfSense will need to connect the same way.

I entered ifconfig in the shell and both WAN and LAN are active.

With regards to the LAN not receiving DHCP:

As I stated above both connections are active and the LAN is set to DHCP with everything left blank. When ipconfig /all is used:

Windows IP Configuration

Host Name . . . . . . . . . . . . : passissue
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
for hp #2
Physical Address. . . . . . . . . : 00-0F-20-72-B8-F4
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 255.255.255.255

As for not having access to the web, The WAN is active and I unchecked block private networks. The WAN does have an IP from the modem/router of 192.168.254.1

Update
I changed my speedstream into bridge mode. When doing this I entered the PPOe info into pfsense and it did get an IP address, but the subnet mask was 255.255.255.255, but on the LAN the subnet mask is 255.255.255.0. I know this isn't right.

dotdash

@kycnotes:

Update
I changed my speedstream into bridge mode. When doing this I entered the PPOe info into pfsense and it did get an IP address, but the subnet mask was 255.255.255.255, but on the LAN the subnet mask is 255.255.255.0. I know this isn't right.

No, that's fine. That's just how PPPoE works.

kycnotes

Problem solved, now everything works like a champ. Thanks to all that helped.