No Internet after initial pf sense configuration
-
You seem to have two separate problems though.
You get not external access from a client on the LAN.
Wireless clients cannot connect to the pfSense GUI even.
I was attemptiong to address the second which only seems likely if the TP-Link is actually still routing in some way rather than acting as a pure layer 2 AP.
Steve
-
@stephenw10 But I already stated that I still have these issues when the TP-link router isn't even connected to the pfsense box and I'm wired in to pfsense. I think it might be a NAT or DNS issue since it's isolated to pfsense and it gives me the "the website could not be found or changed ip" when I try to access the internet, but I don't know what would be wrong besides leaving the DNS blank and not using Google's DNS on the default config, but I've seen this done and it work flawlessly. @Raffi_ also mentioned the private ip issue, but that was the default config given by pfsense.
I disabled the DHCP completely on the TP-link before I ever connected it to the pfsense box and I only connected it to the LAN. Though at first I did connect it to the wan of the TP-link during the very first configuration; but I factory reset it, disabled dhcp, set the static ip, and then connected it correctly to the pfsense. I did not try to connect to the gui or the internet during that period.
-
Show your config with screenshots, or it's just wild guessing here.
-
Yes, we need to see your setup.
I would still say that you have two separate issues there. If you can open the pfSense gui from a wired connection you should also be able to from a wireless connection with the TP-Link connected to the same intrerface. If you can't then it's not acting as a pure AP.
Steve
-
The wan and lan of the tp box cannot be in the same subnet.. unless that device has a "bridge mode"..
-
@Grimson @Raffi_ @stephenw10 a private ip is also used for wan for the TP-link router when used as my regular router and works over a public ip for the lan just fine. That limits it to the firewall or NAT issue
-
Ok, then we need to see how it's configured to offer more.
Steve
-
@Grimson @Raffi_ @stephenw10 Update: the entire problem was registering the mac add to the ISP. I'm receiving full internet capabilities, but now I'm running into a new obstacle. I've configured the admin access to allow more than one device access it and anytime I try to access it from another device besides the laptop I was wired to, it will not let me. I'm also unable to connect to the internet with my phone
-
@the_jaeger said in No Internet after initial pf sense configuration:
I've configured the admin access to allow more than one device access it
Not entirely sure what you mean by that. Can you be more specific about where that setting is and what you set it to?
Steve
-
@stephenw10 I live in an apartment and with my subscription, anytime that a new router is introduced to the wan, it's mac address must be registered with the ISP before that device receives an active connection to the internet.
it works now, but now I have the issue of all cell phones that connect to internet take 5 minutes to finally connect. Would port forwarding solve this issue or at least mitigate it?
-
@the_jaeger I'm also confused by what you mean on the limited admin access. Do you mean admin access to pfSense or the TP-link ap? Please be more specific.
Can a device wired directly into the TP-link ap get internet access immediately? Is it only a wireless device which has a delay before it can access the web?
-
Port forwarding will not help at all with outbound connectivity.
How are they failing? Unable to resolve IPs? No route to host? Just timing out?
Steve
