I’ve had the pcwrt router for several months now, with a basic home netork configuration:
AT&T Pace 5031NV router -> pcwrt router -> home devices
Wireless is turned off on the AT&T router, and all my devices connect via wired or wireless interfaces to the pcwrt router, with addresses assigned on the default pcwrt private network. Up to now, this has sufficed.
However, I’d now like to configure the AT&T router as a bridge, so that I can make selected devices accessible to outside traffic. This means that
a) I need to configure a server on my home network to get the dynamic public IP assigned to the AT&T router and send it to the OpenDNS server to keep my OpenDNS public static IP always pointing to my AT&T dynamic public IP;
b) I need to configure the AT&T router to function as a bridge, to allow external traffic to get to the pcwrt router, where it can be properly routed (via NAT?) to the correct server.
Has anyone managed to get a fairly standard configuration like this working the the Pace 5031NV router? I’ve tried some things suggested on the AT&T forums, with no luck. Suffice to say, this router is… peculiar.
By a) do you mean to keep OpenDNS current with your public IP address assigned by AT&T? If so, no specific setup is needed beyond setting up Dynamic DNS on the pcWRT. And that’s needed only if you use OpenDNS Home instead of OpenDNS Family Shield.
For A) I’ll give it a try; I had some issues setting it up when I first got the router, but I’m more familiar with it now, and will look at setting up Dynamic DNS again.
For B), the Pace 5031NV router has quite a bit of a different user interface, and I’m not sure about IP passthrough being an option, although it does have some DMZ forwarding settings that others have had some luck with. I’ll take a look again tonight, and report back.
I’ve double and triple-checked that my credentials are correct in the settings. The test dnsomatic URL correctly updates the OpenDNS and Google Domains services (it shows the updates in the activity logs), so I’m thinking the problem must be on the router, or somewhere between the router and dnsomatic.
This reply was modified 4 years, 6 months ago by tecoripa.
I tried disabling parental control entirely, and got the same result when I went to update Dynamic DNS: Failed to update Dynamic DNS, please check your network connection. I rebooted the router and tried it again, just to make sure, to no avail.
I updated the filter to only exclude IPs in those ranges (changed line 588, and added a line): [ $use_ipv6 -eq 0 ] && __IP=$(echo $1 | grep -v -E "(^0|^10\.|^127|^192\.168)") # no private IPv4's
[ $use_ipv6 -eq 0 ] && __IP=$(echo $1 | grep -v -E “^172\.(1[6-9]|2[0-9]|3[0-1])\.”) # no private 172.16.0.0/12 IPv4s`
After that, I was able to set and save and confirm my Dynamic DNS updater settings in the pcwrt interface.
Unfortunately, however, this change I made will be wiped out next time I update the OS, unless it’s folded into the pcwrt codebase. Can you open this up as a bug, and apply the fix with the next release of the OS?
FWIW, the latest version of this script in the openwrt github repo correctly filters private address spaces: