Static IP Wan -> no internet
-
And What about your DNS Servers settings ?
-
Here is the thing. Is this the USA? If so, they like to hold you hostage with DHCP.
They will give a consumer an IP via DHCP and change it periodically.
They could just as easily give you a static IP but they know that if they do that you can run a server there.
So, they will pull out all the stops to make sure you never get a static assignment to work…UNLESS you pay them extra for a "business" connection, which is pretty much the same connection you have now except they don't hamstring you with dynamic IPs and blocked port 25 "for your safety".
If you pay them more, they will allow what you are trying to do and stop screwing you on port 25. Its extortion.
-
You know what? It actually takes effort on the part of an ISP to make internet this broke.
A business connection is basically just an un-tampered-with, unmolested connection with simple bandwidth limits.(End of ISP rant - My advice is go with the DHCP setup on WAN and get yourself a DynDNS account)
-
To move this somewhere: what's exactly "no internet"?
traceroute 8.8.8.8
traceroute www.google.com -
I had the exact same thing happen to me and none of my settings were wrong. Doesn't take a genius to type in an IP address and a subnet.
However, I knew what was going on. Its the ISP - If you want a static IP they will make you buy one. -
I had the exact same thing happen to me and none of my settings were wrong. Doesn't take a genius to type in an IP address and a subnet.
However, I knew what was going on. Its the ISP - If you want a static IP they will make you buy one.Where, the ISP comes to Play in the OP Scenario ?
Setup:
Cable modem -> router -> Pfsense Wan -> Pfsense Lan -> PC
My setup is :
Cable modem
Router wan ip 82.73.xxx.xxx
Router lan: DHCP 192.168.11.100 - 192.168.11.255
Netmask: 255.255.255.0
Gateway: 192.168.11.1Pfsense :WAN 192.168.11.39/24 (static ip)
Netmask 255.255.255.0
Gateway 192.168.11.1Pfsense: Lan DHCP 192.168.1.10 - 192.168.1.255
Netmask 255.255.255.0
Gateway 192.168.1.1it's a seperate router.
i know i am doing double nat.
i am testing pfsense at home for fun.why does everything works fine When the wanside get's An ip from dhcp?
i don't see why setting a static ip/24 and gateway of 192.168.11.1 won't work -
Hmmm. I was under the impression he was trying to static IP on the pfsense connected to the modem.
That might have been wrong and if so, then yeah - My rant wouldn't apply.If he is double NATing, should be easy so long as OP assigns different IP to the WAN on pfsense2 than is on pfsense1, puts it outside the DHCP range on the LAN (assuming DHCP is running) and unchecks the block private IP block.
-
taktje-
Can you ping your cablemodem through the pfsense box?
c:>ping 192.168.100.1
-
Are you kidding me?
There is nothing to ping at 192.168.100.1
cable modem gives a wan ip to my router of 82.73.xxx.xxx
I think it's a DNS issue.
I set everything to "default settings" (again) and try again.
-
As already requested a couple of hours ago…
traceroute 8.8.8.8
traceroute www.google.com -
So, by doing this for fun, you mean having fun watching us chase our tails?
-
Problem solved :D
Had wrong DNS settings.
And i'm doing this for fun and to learn.
My goal is to setup a hotspot at a campground with Pfsense and some Ubiquiti Nanostations M2 (great stuff).Thx all
-
doktornotor - I think you were on the right track way back.
-
i know.
lack of time and some private stuff.
have not worked on pfsense for a long time so i am starting from the beginning.
