NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk CM2000, RAXE300, pfSense CE, XS712Tv2 12-Port 10G Managed Switch Setup
Bought the Nighthawk CM2000 and RAXE300 to replace Spectrum ISP gear needing to eliminate the double NAT as I never succeeded in direct connection of Spectrum modem to the pfSense router. Without the...
I'd be more wondering if its an issue with pfsense and how its negotiating a public/private IP address setup from the ISP.
I've dabbled in a few aftermarket 3rd party software but never pfsense. They've been a bit more complicated and not as user friendly in my experience. And I didn't do it enough to be worth the time so went back to direct modem---router setups. So not much help but based on prior experience, I'd be on the pfsense forums asking assistance.
Zaphod-17 wrote:
My goal was to configure an Internet - NetGear CM2000 - pfSense Router - Managed Switch - NetGear RAXE300 Access Point linkage configuration with the pfSense Router presenting a WAN public IP address.
That's the way to do it.
There could be other options, but if you want that, fine. Just don't expect the RAXE300 to do everything in its repertoire.
Disabled Features on the Router when set to AP Mode | Answer | NETGEAR Support
Because the RAXE300 is in AP mode, it has little influence over your network. Problem solving is probably down to the upstream devices, the pfSense Router and Managed Switch. Not much help that anyone here can give with those.
Sadly, I haven't been able to respond because, just as I feared, after cloning the pfSense configuration and rebooting the Nighthawk modem would no longer connect to the pfSense Router. That was Thursday, June 27th. Pretty much non-stop since then trying to get a public WAN address to be accepted on the pfSense Router. Which remarkably it just did and I again have no understanding as to why.
I must beg pardon as simply too exhausted to realize that indeed the RAXE300 had been removed from the situation and that this should be addressed on a pfSense forum.
Thank you all for your input!
good luck on the pfsense forum!
The RAXE300 is pretty solid so would work going modem---->raxe while you're trying to get the pfsense to function properly.
In closing, boy howdy! I really screwed the pooch on this one. In my headlong rush to GTD, I inadvertently re-titled a duplicate RAXE300 user manual download to Nighthawk CM2000 Manual. I remember thinking: Gee, the modem must really not be that important. Everything is dependent on the router settings!
Pulling all-nighters is not for the aged.
After logging into the CM2000 Event Log, I find it replete with Critical and Error messages that may need ISP intervention.
In addition, having finally found the How to Power Cycle your Network KB, I had never executed the proper power cycling of the network. I never shut down the HP z840 computer that houses the pfSense vm entirely. It houses a lab setup with 3 ESXi along with the pfSense and this failure to truly dislodge the ghosts of settings past may well be causal.
A pause to #RTFM and then I'll revisit this on the CM2000 modem forum.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
