Having same gateway addres for all interfaces.
-
So i'm just getting pfsense up and running. Internet and wired machine is running fine. But i want to add wifi as well. But it appears i can't have the same gateway address for both em0 and em1. Is there a way around this, i'd like having the wired and wifi on the same subnet.
-
Not sure how this fits in this particular forum subject.. "DHCP and DNS".
You should not have a "Gateway" address assigned to any of your LAN ports. Although Im betting that's not really what you mean.
Id move this to "General Questions" and start by explaining your setup.
;)
-
I assume you mean the default gateway and the 2 interfaces have different network addresses, such as 192.168.1.0/24 and 192.168.2.0/24? If so, no. The gateway address must be within the address range of that network. As for having both WiFi and Ethernet on the same subnet, what's stopping you? That's a very common configuration.
-
The reason i put it under dhcp was because em1 is 192.168.1.1 and em0 is 192.168.2.1, but i wanted em0 to also be 192.168.1.1 so em0 and em1 is running the same dhcp ip pool and same subnet. Meaning both the wired and wireless devices would be on the same network, just like a normal router.
And i thought it was about merging the dhcp servers somehow. But i've found it's not.
And the reason i used "gateway" was because 192.168.1.1 is the gateway for em1 etc. -
Why do you have 2 DHCP servers? You only need one. That said, you can have 2 within the same subnet range, provided there's a means to prevent them from handing out the same addresses. While modern DHCP clients are supposed to do a gratuitous arp, before accepting an address, you can just configure the DHCP servers to hand out separate blocks within the subnet.
Now back to your problem. Why is the access point not just connected to the LAN. That is what I have here and is the usual configuration. If you're using a router as an access point, then just connect the LAN side of it to your network. You might have to configure the WAN side with a dummy static address, as some routers won't work without an address on the WAN side. Some routers can even be specifically configured for use as a plain access point.
-
Because if i try to set em0 to 192.168.1.2 it'll give an error. I was forced to give each interface it's own ip range from a different subnet.
My ap is connected to lan. But i read that to be able to have two interfaces on the same subnet you need to bridge them and doing that costs some performance. Also that it apparently can be quite a bitch to get working properly.
-
Why do you have those 2? You only need a single LAN and you connect the WiFi to it.
It appears to me you're making things more complicated than they should be. In my network here, on the LAN side of pfSense, I have an Ethernet switch, which everything else, including the access point, plugs into. Why do you need 2 interfaces???
-
Because my pc is connected to em1. em1 is wired, em0 is wireless.
-
I must be missing something. Is the wireless access point you're using built into the computer?
-
Put a switch on LAN and connect your wired devices and the access point to that.
-
Put a switch on LAN and connect your wired devices and the access point to that.
But that's not what i wanted to do, i didn't want to add more devices. But i guess i'll have to rethink the setup.
I must be missing something. Is the wireless access point you're using built into the computer?
No, it's just a regular wifi ap.
-
The best answer (for the moment) is to use an external switch.
-
The best answer (for the moment) is to use an external switch.
Seems like i'd have to do it anyway. Only two of the three nics are intel, the onboard one is a RTL8111GR which apparently is bad for business as i've experienced it loosing connection. So i'll change the setup to only use the intel nics.
-
The best answer (for the moment) is to use an external switch.
+1
