PF Sense Setup
-
@johnpoz I did not get a 192.168.100.1 address when my modem was in bridge mode which really confused me because literally a few days ago I purposely put my router in bridge mode and pulled it back out of bridge mode just to know how to do it/if it would save the settings, etc.
The other day when I put my modem into bridge mode, I was able to go to 192.168.100.1 and login and reset it back out of bridge mode but tonight I couldnt get to that 192.168.100.1 IP at all no matter what i tried/rebooted which really threw me for a loop because i would have figured if anything I should be able to get that and log back in to take it out of bridge mode but that wasn't the case. I even shut pf sense box off at one point and just plugged my laptop into my modem and went to the 192.168.100.1 address to see if i could reach it and login to revert it out of bridge mode but I couldn't. Is there a specific reason why i couldn't reach the 192.168.100.1 address to revert it out of bridge mode instead of having to reset it?I'll try it again tomorrow or later this week and see. I know i rebooted my modem quiet a few times and the pf sense box a few times as well after plugging things in and verify everything was on the right port.
-
As a last resort I’d hit the reset button for your modem. Set it back to defaults.
Where did the IP address that worked come from?
That’s not the IP your ISP gives you for the WAN.
Also is your laptop network properties manually set? If your modem isn’t given out IP’s, which it shouldn’t be in bridge mode, your laptop IP could be outside the subnet so it can’t connect to the modem.
-
@jsmiddleton4 i did reset my modem and uploaded my prior configs backup so everything is working normally for work tomorrow.
the IP address that worked was a static one that I set when I was going through the initial configuration. So I set a static IP for my LAN.
the only way i could connect to the pfsense box was by setting my laptop up w/a static IP (via network settings, ipv4, setting the IP to 192.168.0.10, subnet 255.255.255.0, and gateway to 192.168.0.1 and physically connecting the cat5 cable from my laptop to my modem that is in bridge mode.
-
@stephenw10 i did try swapping the cables at one point and it didn't make a difference. i cant recall if it made it worse or not i just know it was not progress moving forward when i swapped them lol. (so then i reverted the swap to keep troubleshooting.)
-
You set the static IP for the modem?
While this can be very frustrating you should know it shouldn’t be. Its not this hard to make PFSense work as a basic router/firewall.
You set the modem to pass WAN information to the PFSense box. If configured with the initial simple settings, PFSense picks up the WAN information on its WAN port.
Are you able to access the console mode for PFSense, simple menu, etc.?
-
@jsmiddleton4 this is the back of my modem/router combo. from what i know it doesn't specify wan or lan.
it says 1 wan port on the doc but then when you look closer it says:
WAN ports: 1
WAN port(s) type: Coax F-connector
LAN ports: 4sooo technically, id take that as it doesn't have a wan port and it just uses the coax as wan and gives you 4 lan ports.
-
@travelmore It seems that you're over complicating your setup for a person that's new to pfSense...start simple for now with WAN > public IP, LAN > non-static, DHCP.
-
Coax for WAN….
NOPE. That’s for “out there” WAN.
You need “in here” WAN port.
When you go into bridge mode one of those LAN ports is the WAN port.
Which model modem?
-
@travelmore In bridge mode you only need the first and nothing else plug in...every thing else plugs into pfSense.
-
Which is the first? One closest to COAX or closest to USB ports?
-
@jsmiddleton4 yes closest to the cable port.
-
@jsmiddleton4
Hitron CGNM (model) 1C:AB:C0:65:6C:A0 (mac) 251164055728 (serial #) -
Your’s has wireless?
-
@travelmore I had to buy a cable modem on eBay (Motorola 3.0) without the WIFI as all Cox had was as yours, and you have to do the same unless you can find info how to disable it.
-
They call it “IP Passthrough”? That’s what your’s says?
You select the port that’ll be the Ethernet WAN port. I’m gonna guess LAN port 1 is by the USB ports. 4 by the coax jack.
https://support.shaw.ca/t5/internet-articles/ip-passthrough-for-hitron-cgnm-2250/ta-p/6787
EDIT: Also if you reset the modem its default IP address I found is 192.168.0.1. People with your modem set up their own router and use the modem as only a modem. Which is what you’re trying to do.
-
@jsmiddleton4 this is what it looks like. I took a video of all the settings so if i ever had to go back and look i had an exact replica aside from a backup file.
Thank you for that info. I wasnt sure how to set it to be just a modem besides just throwing it in bridge mode. I appreciate your help. I will try this again sometime this week and give updates. hopefully it'll work and i can rely that!
-
You want to enable IP Passthrough and then pick the Ethernet port you want to use for the WAN.
Once you know for sure your modem is passing the WAN’s IP information through to your PFSense box, everything else is all PFSense configuration.
I have to ask what bridge mode were you setting then? We’re you braiding two Ethernet ports? More commonly called bonding.
Also I would consider blasting the drive with a new PFSense install.
-
@travelmore said in PF Sense Setup:
@stephenw10 i did try swapping the cables at one point and it didn't make a difference. i cant recall if it made it worse or not i just know it was not progress moving forward when i swapped them lol. (so then i reverted the swap to keep troubleshooting.)
I would try it again to be sure.
If you can access the pfSense GUI when the laptop is connected to the modem that means the pfSense LAN must also be connected to the modem which is obviously not what you want.
It also explains why you see no IP on the WAN as that is in fact connected to your internal switch where no DHCP server exists.
Swapping the cables at the pfSense box (reversing the WAN and LAN NICs) should correct that.Steve
-
I'm not sure the modem was in IP Pass Through mode. Which means of course no WAN information was being passed to the PFSense box. The modem was "seeing" the PFSense box as a LAN client.
-
@jsmiddleton4 said in PF Sense Setup:
The modem was "seeing" the PFSense box as a LAN client.
Which is not a problem - you can for sure run double nat setup. As long as pfsense wan and lan do not overlap networks.. If your pfsense wan is say 192.168.1/24 - just make pfsense lan 192.168.2/24 or something.
Doesn't matter if pfsense wan gets an IP or doesn't get an IP, or gets an IP and can not go anywhere.. You would still be able to connect to pfsense lan from client on its lan.
