WLAN and LAN on Same Subnet

You could place both the WiFi and internal into a zone, and configure them that way. They would have different subnet masks, but you would only need to set up one set of policies.

thanks, but both would have to be on the same subnet due to limitations of the software (example: iTunes library sharing). I ended up running a cable and not using wireless for this project.

I have the same problem I want to have wifi network and wired network in the same subnet. Now I use an other Linksys wifi router. I don’t want to do a complicate configuration just to put the wifi network and wired network in the same subnet. It must to be the same subnet by default. Thanks

I do not know if works but try like this: 1 vdom (transparnet) vdomlink, internal, wlan 2. vdom nat vdomlink,wan or you can enable in system settings (cli) allow-subnet-overlap enable

You cannot use vdomlinks in transparant mode. But boys, the network design is wrong, don' t try to fix the proposed problem. wireless and fixed should have 2 seperate network ip' s. Then provide static nat' s and firewall rules for the itunes library computers. That' s all. Cheers, Eric

what you can do is to ' group' your internal and wlan interface into a new virtual Interface - this feature is called " switchgroup" After that you have a new " virtual" Interface (lets say ' LAN' ) and the other 2 disappear. So you than run your DHCP, routing, policies etc on that new virtual Interface.

  config system switch-interface   edit " LAN"     set member " internal1"  " wlan"                

-R.

Where I find this feature " switchgroup" ?

it´s in v3 MR7 also, i believe it was introduced in MR6

When I use the command: config system switch-interface edit lan set member .... just dmz , modem and wan2 is in available interfaces. I need the internal and wlan. What I need to do to have this interface in available interfaces?

We have been using switch-interface since build 668, so yes, it does work, and has to either be done at the CLi (as above, after removing ALL DHCP servers, Firewall policies, etc.) or built in a full script. Here is ours, offering one wireless for internal users (on the same subnet as the LAN), and another for guests. config system switch-interface edit " NewInterfaceName" set member " internal" " wlan" next end config system interface edit " wlan" set vdom " root" set wifi-ssid " InternalUsers" set wifi-security WPA set wifi-passphrase ENC *see caveats* next edit " internal" set vdom " root" next edit " wan2" set vdom " root" set status down set type physical next edit " wan1" set vdom " root" set ip x.x.x.x y.y.y.y set allowaccess ping https ssh snmp set type physical next edit " modem" next edit " ssl.root" set vdom " root" set type tunnel next edit " NewInterfaceName" set vdom " root" set ip 10.0.0.1 255.255.255.0 set allowaccess ping https ssh set type switch next edit " GuestWireless" set vdom " root" set ip 192.168.1.1 255.255.255.0 set type wireless set wifi-ssid " ExternalUsers" set wifi-security WPA set wifi-passphrase ENC *see caveats* next end *CAVEATS* Because it is now in a switch, the wlan is no longer a stand-alone interface. Therefore, you lose the ability to manipulate ANY portion of it in the GUI. If you want to restart it, you have to CLi it. If you want to change the SSID, or the passphrase, you have to CLi it. Broadcast/silent? CLi. Also, because of the above, it is not possible to change the passphrase in plain text, so you will have to find other means to determine the encrypted hash. I would suggest you create a third guest wireless, set the passphrase you want in the GUI, then go to the CLi, highlight the hash, and paste it into your wlan. Then remove/disable the 3rd guest wireless. Hope this helps!