Holger Bauer <[EMAIL PROTECTED]> writes: > > Sure, go to Services>DHCP in the webgui. You'll notice a seperate tab for each internal interface you have > (like your OPT1, it's labeled with the interface name). Switch to that tab and make your settings. > DHCP-Server in pfSense is per Interface, so you can have different DHCP-settings for each of your interfaces. > > Holger > > > -----Ursprüngliche Nachricht----- > > Von: Nate Davis [mailto:[EMAIL PROTECTED] > > Gesendet: Montag, 2. Januar 2006 18:39 > > An: [EMAIL PROTECTED] > > Betreff: [pfSense Support] DHCP Server on OPT1 > > > > > > Hello Everyone, > > > > Could someone detail for me what I need to do to enable the > > DHCP server > > for OPT1 and the LAN interface? It is running great on LAN, > > but I need a > > DHCP server running on the OPT1 Interface. Is this even > > possible? The > > Subnet for OPT1 is 192.168.60.0/24 (OPT1 is 192.168.60.1). > > > > Thanks, > > Nate > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > ____________ > Virus checked by G DATA AntiVirusKit >
Hi all, So I've continued reading & analyzing the DHCP on wireless interface situation. Could someone please tell me if this is the correct functionality? The goal is to get the DHCP server that is running on the LAN interface to serve addresses to both, the LAN interface and the ath0 aka OPT1 interface. The way I was connecting my laptop to configure pfsense was via copper 10/100 ethernet interface. Once I had the wireless interface and bridging configured, I would disable my copper ethernet interface in windows, or simply disconnect the cable, to ensure that the laptop is really getting the DHCP address via the wireless link. This seemed like a good idea, but I overlooked the fact that in pfsense, the wireless interface, ath0, is bridged to the LAN interface, and also vice versa, the LAN is bridged back to the wireless interface... The problem as you might have guessed is that my laptop could never get the DHCP address via the wireless link... why? Because each time I disconnected the cable, or disabled the link, the LAN interface would go down and the bridge would get broken... disconnecting the DHCP server from the wireless interface. Also, I observed that, if the laptop already has an IP address.. and the LAN interface goes down.. then wireless connectivity to the WAN and on to internet gets broken. I am guessing that the most appropriate 'fix' or rather, better configuration, is simply to not bridge the wireless and LAN interfaces and instead to setup 2 seperate DHCP pools, one on each interface, and then just route between them. Please, could someone confirm if this is the 'best practice' solution or not, and if not, what is or what could you suggest? This behavior finally became clear when I began trying to connect another laptop via the wireless DHCP, while at the same time, leaving my laptop connected to the wrap... This allowed the LAN interface, and the bridge on the wrap to stay UP... which allowed ath0 to offer the DHCP address to the other laptop :-) So... is there a way to add a virtual interface, similar to cisco's so that the DHCP server can run on that interface instead of an actual interface? Then bridge that virtual interface to the LAN or ath0 as necessary?... or again.. is this unnecessary because we can run DHCP on each interface? Would it save cpu and memory if running only 1 DHCP process which served multiple interfaces? In conclusion my observation regarding DHCP on the wireless interface is: !!! When ath0 aka OPT1 and LAN interface are bridged, !!! !!! pfsense will not offer DHCP address on the wireless interface if... !!! !!! the LAN interface is in down state, or otherwise not connected. !!! !!! because the bridge is broken and there is no connectivity between !!! !!! the 2 interfaces. !!! Thank you in advance for any comments & suggestions! :-) Jim K. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
