wow didnt think I was still such a noob!!
Heres the deal, spent 5 hours in the damn van and even killed the battery with 110v inverter lol
Dont ask why but this is how I need it done..
I have a 133c running as AP or just Bridge tried both, connected to ISP via ether..
Router 1 133c
ether - 192.168.1.107/24 is IP setup to ether1
wlan1 - 10.8.80.3/24 IP setup to wlan1
bridge - wlan thats it and ifcourse wds`s
Router 2-2 Radios 133c
wlan1 - station wds 10.8.80.1/24 IP setup to wlan1
wlan2 - AP
bridge - wlan1 wlan2 and ether1
Router 3 2 Radios 433A for the moment will be 3 radios in a couple days
wlan1 - station wds
wlan2 - AP 10.8.80.4/24 setup to wlan2
bridge - wlan1 and wlan2
DNS=10.8.80.4 + DNS of ISP as number 2
Gateway=192.168.1.1 added in routes as bridge1 (ip is gateway of D-Link rouer)
added IP pool 10.8.80.100 - 10.8.80.254
Setup Hotspot as I normaly would with my other APs with ISP connected on same RB as ISP
Issue - setup as above I canot get to internet from CPE conected to rtr 3, sometimes fiddling around I get Hotspot login but then get Gateway Error page in browser. I get DHCP from Router 3 as desired.
If I go back to Router 1 and add ether in the bridge and release IP in DHCP server in rtr 3 then I get IP from rtr1 dlink router and I can access the net from rtr3. Obviously this is not want I desire.. I tried gateway in rtr3 set to 10.8.80.3 which is rtr1 with no luck played with a whole lot a junk. cant get it for the likes of me.. Please give a hand guys..!
thx
mickeymouse690 -
Not really sure what the heck you’re trying to do here…why bridge and wds everything? Why don’t you just route everything where it needs to go and set the Hotspots up on the desired interfaces (WLans I presume)? You can NAT out at your ISP linkup - so only one NAT…
Maybe a little more info on ‘where’ you’re trying to get to might yield a better way to get there…
R/
Well honetly its cause I just dont know how to do what your saying..
rtr 1 and rtr2 are just repeaters to get around a mountain. Rtr 3 is in a small valley in the mountain where there are 30 or so customers wanting my service so thats why I want the hotspot on rtr 3, also the other main reason is because its a more powerfull RB on rtr3. So what the heck do I do here, im suppose to finish this up today.
I have never nated or routed anything, all my other networks are simple hotspots on main rtr and then repeaters with wds one after the other daisy chained to repeat..
Could yah help with a kinda step by step?
Galaxynet -
will redo ips as follows
rtr1
wlan 10.8.80.1
ether 192.168.107
rtr2
wlan1 10.8.80.2
wlan2 10.8.80.3
rtr3- Hotspot
wlan1 10.8.80.4
wlan2 10.8.80.5
wlan3 10.8.80.6 to rtr 4
rtr4 Repeater
wlan1 10.8.80.7
wlan2 10.8.80.8
wlan3 10.8.80 9 to rtr5
rtr5 Repeater
wlan1 10.8.80.10
wlan2 10.8.80.11
mickeymouse690 -
Well here’s a stab at it - great talking to you on the phone…
RT1 - eth1 gets it’s IP from your Internet router (dlink I think you said…)
RT1 - Wlan1 - let’s give it an IP of 10.8.82.1/24 Interface=Wlan1
In winbox / ip route add ( + ) the routes to the other wlans and hostspot
dst-addr=10.8.81.0/24 gw=10.8.82.2
dst-addr=10.8.80.0/24 gw=10.8.82.2
Go to the rule tab under routes as well… add this src-addr=0.0.0.0/0 dst-addr=0.0.0.0/0 check interface = ping, action=lookup table=main LEAVE everything else default.
Go to /ip firewall NAT
add these nat rules
src-addr=10.8.80.0/24 out-interface=eth1 go to the action tab, action=masquerade
src-addr=10.8.81.0/24 out-interface=eth1 go to the action tab, action=masquerade
src-addr=10.8.82.0/24 out-interface=eth1 go to the action tab, action=masquerade
RT2 Wlan1 (the wlan pointing to RT1 Wlan1)
IP addr= 10.8.82.2/24 Interface=Wlan1
Default route = dst-addr=0.0.0.0/0 gw=10.8.82.1
Add this route as well 10.8.80.0/24 gw=10.8.81.2
Go to the rule tab under routes as well… add this src-addr=0.0.0.0/0 dst-addr=0.0.0.0/0 check interface = ping, action=lookup table=main Leave everything else default.
Still in RT2, Wlan2 (wlan pointing to RT3)
ip addr = 10.8.81.1/24 Interface=Wlan2
RT3 Wlan1 (pointing to RT2)
IP addr 10.8.81.2/24 Interface=Wlan1
Default route = dst-addr=0.0.0.0/0 gw=10.8.81.1
Go to the rule tab under routes as well… add this src-addr=0.0.0.0/0 dst-addr=0.0.0.0/0 check interface = ping, action=lookup table=main Leave everything else default.
RT3 - Hotspot Wlan, setup as normal… 10.8.80.1 all the rest is the same…
R/
mickeymouse690 -
(Chris) It was a pleasure to talk with you last nite… Please don’t forget to post here, when you get done absorbing all the info and the configs we created last nite - including how you decided how to setup future CPEs on your Hotspots, your lessons learned. They will help someone else in the future that’s trying to do something similiar…
For those of you just joining us… mickeymouse690 was trying to setup a data backhaul around a mountain - hence the several backhaul ‘stop over’ points, and then serve a Hotspot. Additionally, past RT3 (see above), he is planning to add two more backhauls with an AP on each as well making his ‘string’ include an RT4 & RT5.
R/
Thom
Hi Galaxynet - (Thom)
Again, I dont know what to say for the hours spent on the horn with me these past couple days…
Just as an update- the night before last, we seemed to have gotten her almost ready to go.. We had intenret access from rtr3. What was left to do on my end was get rtr4 up and going and have clients attached to it be able to access the net via the hotspot on rtr3 and so on for rtr5. Well dont know what the heck happened cause as I went back up there today thinking that everything should be good to go since the additional rtrs after rtr3, I was setting them up via wds like I had done in the past with my other networks. Well,, no go!! llol again it seemd that I couldnt resolve DNSs like the night before. The night before we figured out the problem failry easily once we got the rest taken care of.. I forgot to add a default gateway on rtr1, after we did that well domain names where resolving. Now today hmmm cant resolve through rtr4 after fiddling with the darn things, realised that couldnt resolve through any rtr no matter which one i was connected to. that was weird as before I had a small fit,!!(and tried to reconfigure all rtrs via wds again) I hadnt changed anything in the rtrs.. Well, put back all the rtrs as they where before, and then Thom had some ESP issues cause he called me right when I told myself I wasnt callin him for help lol. After checking all the rules, routes and fixing a couple mistakes I made etc etc, Thom came to the conclusion that something was up with the router behind rtr1 or the dsl modem.. Nothing was tracerouting after the dlink..hmm.
Drove back again to the town after an insane near miss with a HUGE MOOSE!!! (was told that there not suppose to be in the area) (YEAH RIGHT!!) and when I got upstairs I noticed a computer that was on with a IP conflict Error msg.. hmm before I attempted to fix that, I went into the rtr1 and tried to ping and traceroute without success.. Went and fixed the ip conflict in the dlink and voila!! rtr1 can now ping a domain and traceroute.! So, seems like it should work now from rtr3 and rtr4 I really hope so, didnt want to drive back up there again for the fifth time. Midnight is pretty much my cutoff time.! So we will see tomorrow if the other rtr`s wil resolve correctly…
Let me just say that Thom deserves some sort of Mikrotik patience and really wanting to help metal!
Learned a hack of alot in the past couple days. Once I really understand what the heck im doing with Nat rules and why this has to point there and so forth, i will definitly extent what I have learned to the forum here…
My hats off to yah Thom. Really! Clasa ct guy that one, and to everyone else lending a helping hand in here.!
Hi Chris -
First - thanks for the compliments - you seemed to be desperate so helping you out was a pleasure…
I see from your post that you had an IP conflict - you forgot to change the IP on the Desktop back to it’s original IP didn’t you - so it still had 192.168.1.1 as it’s IP which conflicted with the Dlink router… 
You didn’t mention that you also had to setup a ‘bypass’ for rt4 to bypass rt3 hotspot authentication in the hotspot at rt3 via WDS. Thought it was important for other users to know that so am mentioning it here…
I look forward to your futher adventores being chronicled here - they make good reading
Ok Chris - let us all know how this turns out for you!
R/
Thom
hihi..
Oups forgot to mention that one yah.. I had to go into rtr3 Hotspot and add rtr4 in ipbindngs as bypassed. INitially last night that seemed to be an issue because rtr4 wasnt pinging out anywhere therefore was not authenticated with rtr3.
Will keep all posted.!
thx again!