I have the following setup and cannot get a Mikrotik device to pass data via station mode.
AP v2.9.38
Mode: AP Bridge
WDS Mode: Disabled
Bridge: Bridge1, ether1 and wlan1
I can connect a LS2 unit via station mode to this AP and data will pass through the wlan1 port to the ether1 port to the Internet but if I connect a Mikrotik client to this AP then no data will pass through. Why?
How do I setup a Mikrotik client in station mode and get it to pass data through to the AP?
Since an LS2 unit will connect in station to the AP, I’m assuming that the AP is configured correct. This is a Mikrotik station mode issue.
this has been coverd in many many posts before, and is the whole reason station-psudobridge was created. It works great so far in our testing, and saves us a ton of overheard not needing to use WDS anymore.
Can you tell me what I have to setup to do this routing or point me to the thread that covers this? I’ve installed v3 on a few routers and for me it is unstable. I’m waiting for it to get out of beta before I start installing on my production environment.
What commands need to be added to a station client for it to pass data across?
I think there are references in the manual and wiki, but in the event there aren’t you can take a look at this sample script I use to setup our CPE’s/mikrotik devices as routers.
/interface wireless set wlan1 mode=station
/ip address add address=192.168.100.1/24 interface=ether1
/ip firewall nat add chain=srcnat src-address=192.168.100.0/24 action=masquerade
/ip firewall connection tracking set enabled=yes
/ip dns set allow-remote-requests=yes
/ip pool add name=dhcp1 ranges=192.168.100.200-192.168.100.254
/ip dhcp-server network add address=192.168.100.0/24 gateway=192.168.100.1 dns-server=192.168.100.1
/ip dhcp-server add interface=ether1 lease-time=3d address-pool=dhcp1 authoritative=yes add-arp=yes name=dhcp1
/ip dhcp-server enable dhcp1
/interface pppoe-client add interface=wlan1 user=default password=changeme add-default-route=yes use-peer-dns=yes
/system ntp client set enabled=yes primary-ntp=aa.bb.cc.dd
/system clock set time-zone-name=America/Los_Angeles
/snmp set enabled=yes
/snmp community add name=xyz address=0.0.0.0/0 read-access=yes
/snmp community remove public
That example uses a PPPoE interface for connectivity. If you are not using PPPoE then you’ll have to modify the script to suite your needs.
I was trying to send a private message as the question I have doesn’t really pertain to this post.. anyway I was unable to do so…
Are you able to pass PPPoE traffic through the CPE’s setup in station-pseudobridge mode?
I would like to do away with our WDS clients as it causes much overhead and for most clients transparent 802.1d bridging is not required. I thought I saw something about the Pseudo-bridge mode not allowing PPPoE passthrough… Anyway if it does, it’s definitely something to look forward to in ROS v3.
sorry for the slow response, didn’t see your message… and no for some reason I can’t send PM’s either…
yes, we are passing PPPoE through station psudobridge just fine. just ensure that there is only one device plugged into ether1 otherwise you’re going to see some really odd symptoms if there are 2 machines (even if only 1 is active, the arp traffic will cause the psudobridge to re-configure it’s self and screw things for both machines connected.
my favorite thing about psudobridge, aside from not having WDS and the delay it causes when connecting, as well as that overhead, is that the default forward option actually does something again, and when you run winbox from a customer’s house, you only see, their CPE, the AP, and the PPPoE server (assuming the discovery interface is enabled…)