Hi,
We have the 192.168.1.0/24 which are our wired clients on one router, and then the 192.168.2.0/24 subnet which are our wireless clients. How do we use RouterOS to make them be able to see each other (ie, shares on Windows)? I suspect something through proxy-ARP? Perhaps something else?
If so, could someone please list how I would achieve this? Thanks.
you should create a bridge with both the ether1 and wlan1 as members (ports).
then assign an ip address range of 192.168.1.0/23 to the bridge
then make sure the ‘proxy-arp’ setting is enabled on the bridge
Personally, I would route them on the mikrotik box. I suppose, the mikrotik board is the standard gateway for both lan and wlan !?!. If that’s true, all you have to do is to make sure that the wlan-interface is on 192.168.2.0/24 and the lan-interface is on 192.168.1.0/24. Then you should already be able to see the other windows computers. You might have to search for them by IP-Adress rather than DNS or netbios name, because netbios is not able to be routed, and dns you would have to configure on the routerboard to run. This setup will work only if ether and wlan are not bridged together.
If you use DHCP on mikrotik router, you could use 192.168.2.0/23 (SM: 255.255.254.0) for both lan and wlan together. If you want the adresses of wlan and lan separated, just use two DHCP-pools, one on interface lan 192.168.1.10-192.168.1.250 and one on interface wlan 192.168.2.10-192.168.2.250 (left room for some IP’s for routerboard or other hardware, please check against your actual setup if other IP’s have to be chosen).
Sincerly
Schnulch
EDIT:
-Hilton:
Actually, 192.168.1.0/23 will not work properly, because SM for /23 is 255.255.254.0, so the last bit of SM is 1, which would be part of IP-space in your example.
[quote=“Schnulch”]-Hilton:
Actually, 192.168.1.0/23 will not work properly, because SM for /23 is 255.255.254.0, so the last bit of SM is 1, which would be part of IP-space in your example.[/quote]
You are so right, I was in such a rush to finish my post before going out that I didn’t think it through. My example assumed networks of 192.168.0.0/24 and 192.168.1.0/24.
So he would have to use 192.168.0.0/22 then no doubt and have 1022 available addresses?
The network 192.168.0.0/22 will give him opportunity for 1022 IP’s, but I think Windows PC will not be able to see each other while on a different /24 subnet in that range, they could see the router if it’s address is inside the same range as the clients (192.168.1.0/24 for LAN and 192.168.2.0/24 for WLAN. If the router is rouing, then it would work, if it’s a bridge, it won’t with his actual setup of 2 /24 nets separated for wlan and lan clients.
This setup i would not recommend, because using different subnet masks in two networks connected by a bridge who’s in a larger subnet could probably work, but could also cause strange problems. I prefer the KISS- solution, if he wants the lan and wlan seperated he could use routing to connect them, or he could use bridgeing, then my suggestion with two dhcp-ranges (inside the same subnet, but on opposite ends of it) would help a bit to tell if a client is on wlan or lan side just by looking at it’s IP.
He could of course put all his clients into this 192.168.0.0/22 network, then it would work with bridge (but not with routing).
My suggestion was to put all his clients in 192.168.2.0/23, which would work with a bridge too, of course.
Sincerly
Schnulch
RB133 has a wlan1 address of 192.168.2.1/24 and ether1 is at 192.168.1.50/24. Through the primary router (it’s a dlink), we have defined the static route of 192.168.2.0 255.255.255.0 192.168.1.50.
Currently, the wired and wireless clients can do windows shares via IP but dns/netbios does not go. DNS/netbios is an absolute necessity. How do I achieve this? I tried to make a bridge but I don’t see how to add both interfaces.
Sorry, I’m very new to routeros and I need newbie instructions.
Go into ‘bridges’.
then click the red plus sign to create a new bridge, making sure the ‘ARP’ setting is configured as ‘proxy-arp’.
Then go into ‘ports’ and under ‘interfaces’, choose ‘ether1’ (or whatever you lan is) and then choose the name of your bridge under ‘Bridge’.
That’s about it really.
You should be able to browse via windows now.
To use RB133 as a bridge between wired an wireless lan the easiest way is to use only one IP-Range for both sides of the bridge (LAN and WLAN). If you have too much PC’s connected to your Network for a 192.168.1.0/24 Subnet (Allows you 254 machines) just use 192.168.2.0/23 Network for all clients (WLAN and LAN) (192.168.2.0 / 255.255.254.0. If you have a DHCP-Server in your network, just change the DHCP-Pool at the end of the working day, next morning make sure all PC’s are started / rebooted, and you will have them all in one Subnet, netbios and DNS will work, as soon as you have made a bridge of wlan and lan ports of your RB133.
If you have static IP’s on all of your machines, well, then you have some work to do…
Building a bridge:
First delete the ip-adresses assigned to lan-port and wlan-card in winbox - ip - adresses
Then go to bridge, left-klick on “+”, give the baby a name, klick “OK” then go to the second Tab of bridge menu, called “Ports”, left klick on “+”, select the correct ether port, klick “OK”. Now klick again on the “+”, then choose the wlan-interface, again, “OK”.
Now you have yourself a nice shiny new bridge.
Go to IP- Adresses, give an IP-Adress to the newly made bridge, matching your new subnet as explained above.
If winbox disconnects you while making the above mentioned, just reconnect and continue, this sometimes happens when you change Interfaces. Nothing to worry about.
You will then have to remove your static route from your dlink router, because no routing will be done except for internet connection.
Sincerly
Schnulch
Thanks, it seems to be working!
I followed the instructions as such:
Removed IP addresses from ether1 and wlan1.
Created bridge, and then added ether1 and wlan1.
Gave the bridge an IP of 192.168.1.50/24
So now all of the clients get their DHCP from the D-link router, and are on 192.168.1.1/24. I disabled the RB133 DHCP server and there is no more 192.168.2.0 subnet.
Since we have few clients right now, this should work fine. We will re-evaluate as our network grows and perhaps use the /23 subnet.
Thanks for your help!