PF Sense Setup
-
@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.
-
I understand. He isn't or wasn't trying to setup a double NAT config though.
Go back and set up the modem so its doing just the modem piece, IP Pass through. That's what I was calling bridge mode. Pick the port he wants to be the WAN port.
I'd blast PFSense and start clean.
Then follow the PFSense document step by step for install/setup.
-
@jsmiddleton4 I would suggest he gets it working in double nat, before messing with any sort of bridge/passthru mode on his modem.
Once he has that working - it its minor to change over to pfsense actually getting a public IP.
-
If you read back through this thread it seems pretty clear to me that the WAN and LAN were swapped. Everything else is secondary to that, obviously nothing will work as expected in that situation.
the pfSense webgui could not be accessed from the LAN side. It can only be accessed from the WAN side. (using the LAN IP?) The only rational explanation for that is the LAN and WAN are swapped.
Steve
-
@stephenw10 quite true - and agree with you.. My point is before concerning with what IP is on pfsense wan.. I would make sure you can access it from the lan.. What pfsense internet/wan interface is doing or not doing has little to do with being able to access it via lan on initial setup.
-
Once he gets the modem configured the way its supposed to be.
-
@jsmiddleton4 said in PF Sense Setup:
way its supposed to be.
Supposed to be for what - out of the box it almost for sure it going to be natting. So you could argue that is the way it is "suppose" to be ;) There are plenty of instances in double nat, shoot even triple nat that cause the users no grief. So I would leave that until after.
He seems to be having a hard time getting even a basic setup. So I would get pfsense working to the point you can access it from something behind it on its lan. Before worry about what IP is on wan if any.. Yes it really helps you understand which interface pfsense is using for its lan and wan interfaces ;)
-
The way it is supposed to be for what he's clearly stated he's trying to accomplish. Which is not double NATing.
-
@jsmiddleton4 said in PF Sense Setup:
for what he's clearly stated he's trying to accomplish
Where did he state that?
@travelmore said in PF Sense Setup:
my goal is to monitor all the devices on my network (wired and wireless) and see how much bandwidth they are pulling and by what method (browsing, gaming, streaming, etc.)
That has zero do to with him double natting or not.
@travelmore said in PF Sense Setup:
I still am using my ISP-provided modem/router to hand out DHCP (I’d prefer to keep it that way until I get more familiar w/everything)
From that, seems more like he doesn't want to touch anything on his modem router. I am all for removing double nat... My point is might be better to just get his setup working with stuff behind pfsense before messing with anything at all on the router. If his isp device is working.. Then just connect pfsense behind it - get it working and clients behind it working before messing with the config of the isp device. That is all I am trying to say.
