[SOLVED] pfSense ALIX 2D13 OPT1 problems
-
Sigh… outta here, waste of time.
-
I really didn't change the configuration of the local interfaces. LAN as well as OPT1 are configured the same.
Here are the settings:
IPv4: Static IPv4
IPv6: Track Interface
IPv4 address: 192.168.1.1/24Okay, so the pfSense box is sitting behind another router, which acts as a DHCP server limited to one client (in this case the ALIX 2D13).
Every interface needs to have a unique IP address/subnet.
-
@hda:
So then, are all the other tabs empty ?
Yes, the other tabs under "Interfaces>(assign)" such as VLAN, Interface groups etc. are empty.
Every interface needs to have a unique IP address/subnet.
I forgot to mention that everything with LAN and OPT1 is identical except the IP address. The LAN one is 192.168.1.1, but the OPT1 one has the address 192.168.1.2 assigned.
-
:'( a solution is with a /24. Hint : both LAN's are separate and could have a Switch …
-
The LAN one is 192.168.1.1, but the OPT1 one has the address 192.168.1.2 assigned.
Totally broken. Let me state this again: every interface needs to have a unique IP address and subnet.
-
I'd suggest reading some networking 101 before configuring firewalls.
-
Okay, so I mixed up the subnet mask syntax with actual subnets. Anyways, LAN and OPT1 are now working thanks to the suggestions.
I assigned 192.168.2.1 to OPT1 and the client (gaming console) gets the IP address 192.168.2.100.
The LAN (192.168.1.1) interface client (a computer) gets the address 192.168.1.100.So, now it's working, as the subnets are separated, but the gaming console can't connect properly. It doesn't detect the NAT type and shows a DNS error. The computer however, connects just fine to the internet.
-
As I said, LAN is working fine now, but OPT1 still got problems. It gets assigned a proper IP address via DHCP, but there is some kind of DNS problem I can't figure out. The DNS for OPT1 is configured as 192.168.2.1.
What am I doing wrong this time?
-
Not sure if you're still having trouble, but it sounds like you may benefit from drawing up your network configuration and looking at where data needs to flow.
In this case, if you're having DNS issues, test DNS resolution to the gateway:
nslookup google.com<gateway_ip></gateway_ip>
If that fails, then you need to go to either the DNS forwarder or DNS resolver section and make sure that DNS is listening on your OPT1 interface (or just set it to all interfaces).
You can also test DNS to the Internet, like this:
nslookup google.com 8.8.8.8
Hope you can read up on some other networking info which should help you out.
-
ShutterBC, thanks for your suggestions.
On the LAN interface everything works fine regarding the nslookup. The problem with the OPT1 interface however is, that I don't know how to execute the nslookup on a gaming console. In my pfSense configuration, only the DNS forwarder is used with default settings including the option to listen on all interfaces.
I have attached a network diagram and hope this proves useful. I still can't figure out what I am doing wrong with the DNS configuration on the OPT1 interface, however, I found out that instead of pfSense.localdomain, 192.168.2.1 just shows up as localhost, which must be wrong. DHCP works fine on OPT1, though.
-
Did you put firewall rules on OPT1 allowing traffic into pfSense?
-
I did not create any manual rules for the OPT1 interface, meaning it's configured just like the LAN interface:
| ID | Proto | Source | Port | Destination | Port | Gateway | Queue | Schedule | Description |
| | IPv4 * | LAN net | * | * | * | * | none | | Default allow LAN to any rule |
| | IPv6 * | LAN net | * | * | * | * | none | | Default allow LAN IPv6 to any rule | -
LAN net? That is NOT correct.
-
LAN net? That is NOT correct.
Thanks for the hint. After changing the "LAN net" values to "OPT1 net", everything started working. Thank you again, for helping a network noob out!
