Added network interface but can't reach the internet

[alink]

I have a Protectli computer that I’m using as my pfSense firewall. Recently I decided to add an interface assignment so I can connect to an old router that I’ve put in access point mode. That way I can have more than 1 Wi-Fi network to experiment with.

I followed the steps for creating Interface Assignments and Firewall Rules from this video :

Aside from creating a rule for blocking access to the admin console, I’ve configured everything else the same as far as I can tell. However, I can’t reach out to the internet.
Since I couldn’t load any websites, I decided to open Terminal and ping google.com
The following message appears : ping: cannot resolve google.com: Unknown host

Is there some sort of DNS issue going on? The only DNS related configuration I’ve customized is to use Quad 9.

[LTS_Tom]

Rules work from top down, do you have a rule blocking just the admin port or the IP? The first rule should allow traffic and ONLY the port(s) for admin should be blocked as the IP of pfsense is also the gateway.

[alink]

Apologies, I should have phrased it differently. What I meant to say was “Aside from not creating a rule for blocking access to the admin console”

The reason I chose not to block access is because (at least for now) I want the option to access the console from the new interface while I continue to experiment with it. So currently there’s only 1 firewall rule on this new interface, which I have named LAN2

• Here’s a screen shot of what the rules list currently looks like :

• And here is the configuration of the rule :

[LTS_Tom]

That is indeed an allow all rule so you can rule that out as the cause. Check to see if you can ping the pfsense itself to see if the physical layer is working.

[pavlos]

show the Interfaces > LAN2 screen.

[alink]

@LTS_Tom yup, I set the LAN2 Static IPv4 Configuration to be 10.0.2.1 and this is what I get :

@pavlos here’s the Interface configuration :

[pavlos]

did you configure a DHCP server for LAN2 ?

[alink]

Yup, and I made sure not to have a space at the beginning like how Tom accidentally copied and pasted it when defining the IP range

[pavlos]

what DNS do you use in the DHCP Server for LAN2 ?

It makes it easier if you post screens …

[alink]

I left it at default.

[pavlos]

I assume your LAN is 10.0.0.0/24 and its DNS is 10.0.0.1

Then, update your DHCP for LAN2 to use that DNS, 10.0.0.1

I have the exact same network.

[alink]

Huh, I can’t quite explain it, but it started working even though I didn’t change it to 10.0.0.1
It still says 10.0.2.1
Before it started working, I was doing some hardware troubleshooting by adding the OPT2 interface as LAN3 in the 10.0.3.1 range, but it still wouldn’t connect.

Then I decided to connect a device directly into the LAN2 interface with an ethernet cable and it was working, so I reattached the access point and sure enough that was working too.

Any theories?