PfSense with ARRIS MODEM and Linksys E900 DDWRT
-
I'm referring to the LAN DHCP server. This needs to be disabled (see picture)
It is disabled.
You want pfSense to be acquiring the WAN address
It is acquiring a WAN address.
As for the WAN DHCP, I believe you should be able to disable WAN DHCP and just ignore the settings for static IP
WAN DHCP is disabled through setting a static WAN IP; can't ignore it.
-
It is acquiring a WAN address.
Is it acquiring this address from your ISP?
If I understood you correctly, you said pfSense had an IP that never changed but you said your WAN IP changes. I'm having trouble understanding this. What is the WAN IP on pfSense? Is it static or is pfSense set to DHCP?
-
If I understood you correctly, you said pfSense had an IP that never changed but you said your WAN IP changes.
pfSense successfully obtains a WAN IP when connected to the modem. That IP does not change. As far as before, whenever I use to check my public IP through google, it would show the pfSense WAN IP as my public IP. Before setting pfSense, it would show my modem's WAN IP as the public IP. When I set up the linksys, it would be the Linksys WAN IP as the public. For some reason, it stopped and show an entirely different WAN IP for my public IP, which does not match pfsense.
That's the IP that changes. It looks like NAT but I am not sure how to adjust it.
-
This behavior indeed seems strange.
Is the WAN interface on pfSense set to DHCP?
-
This behavior indeed seems strange
Yes it is and annoying. But I just decided to use what I have rather than trying to re-establish what was there before. I port forwarded with the public ip and it works now. Thanks a bunch. Would like for it to be how it was but time is a factor. :) But now i have another problem. Will start a separate post for that one x.x
-
DDNS clients that run on Windows/Mac/Linux client machines will use an external website to verify your public IP (there may also be such a client available as a package for pfSense as I don't think the built-in client does this). You could use one of those to update your DDNS so that your cameras or VPN can be used if your public IP changes, even if it doesn't change on pfSense.
-
Some ISPs require that you use their gateway (modem + router in one) in order to get a static public IP address. They run a routing protocol on their router that communicates with their upstream routers, telling them to route data for your static IP address to your gateway. They don't allow third-party devices to run the same routing protocol because there is significant potential for abuse by giving out the key(s) needed for the routing protocol to function.
So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.
-
Some ISPs require that you use their gateway (modem + router in one) in order to get a static public IP address. They run a routing protocol on their router that communicates with their upstream routers, telling them to route data for your static IP address to your gateway. They don't allow third-party devices to run the same routing protocol because there is significant potential for abuse by giving out the key(s) needed for the routing protocol to function.
So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.
Ahhhhh, ok. Thanks for the info. Things is now that I have opened the required ports, and have access to the cameras, I don't have access from a remote location. I think when I go there for the weekend, I will reset the modem back to default and see what I can do.
My VPN don't work remotely either. On site, all is well, offsite no connection
-
So if you were using your "modem" (in quotes because I'm guessing that it's really a gateway) as a router before, and you had a static IP address before, then that's why you're not getting a static IP address anymore. You've changed your "modem" so that it is strictly operating as a modem (bridge mode), so it's not running that routing protocol anymore and isn't able to accommodate a static IP address as a result.
Quick update
Ok, here is another thing now. I got the same modem home (think it should be the same model, ISP change the models some time) and the modem in bridged and my public IP is the same as my router WAN IP. -
Why aren't you setting pfsense to update ddns any time the IP changes ? thats all you have to do to keep using dynamic IP
-
Why aren't you setting pfsense to update ddns any time the IP changes ? thats all you have to do to keep using dynamic IP
The DDNS service is from the camera manufacturer. If I can set pfSense to use the service that would be great. Is there a tutorial on how to set it up if possible?
https://myq-see.com/ That's the website
-
check your IP camera if it has something like a polling task that checks your wan ip every x minutes. if those IP cameras doesnt have that feature, those IP camera probably suck ask the manufacturer to fix that.
and since you paid for DDNS service (I dont know why you would since there's a lot of free DDNS service out there anyway) ask them how to integrate the DDNS service to pfsense.
-
check your IP camera
Not IP cameras (sadly)
since you paid for DDNS service
The service is free with the product (but yea guess in a way it is paid for)
there's a lot of free DDNS service out there anyway
Will check online but you recommend? Desperate here.
UPDATE
For a quick fix, I reset the modem again, set in bridged mode and directly connected to the linksys. WAN IP is shown as my public IP online. Decided to work "normally" for some reason but still getting hiccups with that ddns thing. Worked fine last night when i tested it at home but now…....in and out x.xUPDATE 2
I took the pfsense PC to my home to do further troubleshooting and diagnostics. And again my public ip matches my pfsense WAN IP. Lol This is a odd things that's happening here. Right now, I'm going to monitor it and I have isolate the issue either to the modem or linksys (thoughts are pointing to the modem for me personally) -
Just setup pfsense to update you ddns account anytime the IP changes.
NO-IP is free https://www.noip.com/
Tutorial https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense
 -
Just setup pfsense to update you ddns account anytime the IP changes.
NO-IP is free https://www.noip.com/
Tutorial https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense
Ok thanks. I setup pfSense already with the DDNS but I took the machine to my home to troubleshoot certain issues I was experiencing. Got one more thing to solve, then all should be good. My public IP is operating good, matching my WAN IP on pfSense. So after I resolve one more issue, I will be bringing it back. Thanks
-
Just setup pfsense to update you ddns account anytime the IP changes.
NO-IP is free https://www.noip.com/
Tutorial https://turbofuture.com/computers/How-to-Configure-Dynamic-DNS-in-pfSense
Just wanted to say thanks for your input. I got it working properly now. It was even better than the DDNS Service the manufacturer provides.
-
"Just wanted to say thanks for your input. I got it working properly now. It was even better than the DDNS Service the manufacturer provides."
Very glad to hear it, even happier got it working for a church ;)
-
What model of modem?
http://badmodems.com/Puma modems will bog down with lots of UDP traffic and cause issues similar to yours.
