kako podesiti mikrotik da 2 različite mreže komuniciraju

RoS 2.9.27

ADSL(192.168.101.2 gateway)----eth1 NATmaskarada<<<<<mikotik>>>>>>---wlan1HOTSPOT(192.168.102.0/24)
l_ _ _ eth2 LAN(192.168.105.1/24) moje računalo i moja lokalna mreža


Ima li neko upute kako podesit da se ove dvije mreže eth2 i wlan1 vide i da ja vidim računala unutar obje mreže, a da hotspot i dalje radi. probao sam sa bridge-om ali nikako to ne mogu podesit. ne mogu pristupit računalima i AP-ovima iz svog LANA na wlan1 mreži, a to mi je bitno kako zbog administracije tako i zbog mrežnog igranja i sl.

E ovako, odgovori na par pitanja:

1. Da li ti se MT konektuje na internet putem PPPoE konekcije, ili se na internet konektuje ruter?
2. Da nisi mozda pozatvarao neki opseg tcp i udp portova?
3. Da li se adrese dodeljuju preko DHCP-a na koji se poziva hotspot ,ili si dodeljivao preko poola (bez DHCP), ili adrese dodeljuje svaki korisnik manuelno?
4. Da li ti je za wireless interfejs stiklirana opcija "default forwarding"?

Objasni situaciju malo blize da bi mogao neko da ti pomogne.

POZDRAV I PUNO SRECE!!!

---

Za wlan1 korisnike iz mreže 192.168.102.0/24 stavi da ti gatwey ip wlan1 tj 192.168.102.1, Za računare iz tvoje mreže 192.168.105.0/24 stavi da je gw ip eth2 tj 192.168.105.1

Probaj pingat sa mikrotika klijente iz subneta 192.168.102.0 i 192.168.105.0 trebalo bi da radi, ak neradi javi?...

I postaj ovdje rute koje imas u mikrotiku.

Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf
# DST-ADDRESS PREF-SRC G GATEWAY DIS INTERFACE
0 ADC 192.168.101.0/24 192.168.101.1 ether1
1 ADC 192.168.102.0/24 192.168.102.1 wlan1
2 ADC 192.168.105.0/24 192.168.105.1 LokalnaEthernet
3 A S 0.0.0.0/0 r 192.168.101.2 ether1

probao sam to što se tiče getveja koje pišeš, tako je podešeno stalno ali računala se ne vide. Inače net radi meni, a i korisnicima na hotspotu (wlan1). što me muči je to šno ne mogu pristupati računalima iz mreže xxxxxx.105 u mreži xxxxxx.102 i obrnuto Predpostavljam da treba zadat rute (getveje) za slučaj kad se iz mreže 105 ide u 102 i obrnuto ALI NE ZNAM kako... :-(

Jesil probao ping, kao što sam ti rekao? trebalo bi da radi...

Kad kažeš da se računari ne vide, na koji način misliš da se ne vide, neradi ping, neradi filesharing ili šta već.

Ako misliš da neradi filesharing, on radi ali računarima pristupaš preko run pa kucaš \\ip računara

probaj sa walled garden-ip list i vidi da definises src i dst adrese koje hoces da "zaobidju" hotspot
/ip hotspot walled-garden ip add action=accept src-address=192.168.102.0/24 dst-address=192.168.105.0/24 server=naziv_hotspot_servera

ovo je primer za celu hotspot korisnicku mrezu 192.168.102.0/24 .Moj savet ti je da prvo omogucis pristup ap-ima iz mreze 192.168.102.0/24 samo na tvoju ip pa vidi kako radi, a kasnije pusti kako ti mislis da ti odgovara
pozdrav

---

Pod tim da se ne vide mislim na to da niti prolazi ping od mog računala na AP-ove koji su na hotspotu niti im mogu pristupit preko njihovih IP adresa. uređajima koji su iza tika na eth1 spojeni mogu pristupit, predpostavljam radi maskarade koja ide tim putem... možda tako nešto treba podesit i od mog interfacea prema hotspotu??

bez obzira sto si ap-ima dodelio staticke adrese hotspot im je dodelio adrese iz hotspot pool-a tako da ces morati da im rucno dodelis adrese tj. da vezes mac ap-a sa ip ap-a
/ip hotspot ip-binding add mac-address=MAC_AP-a address=IP_adresa_APP-a_koju si postavio to-address=IP_adresa_APP-a_koju si postavio server=all type=bypassed

poz.

---

In “normal” routing, you have a set of routes that tell the router about how to reach certain networks. Policy routing is a way to do the same thing, but have different “paths” or routes for various types of traffic. In this article, we will explore the requirements for setting up policy routing and explain some of the concepts involved.

Policy routing is implemented in 3 parts. The first part is to define the routes and which policies will use those routes. The second part is the routing rules, which will define how the policies apply to certain traffic. The third is to define the actual policies. We’ll look at each of these individually.

The network below is the one we will use for this example.

We will assume that you already have the IP addresses set up on your router.

First, we must define our routes. We will add three “default” routes. These are below:

/ip route
add gateway=10.10.11.1 routing-mark=ISP2
add gateway=10.10.10.1 routing-mark=ISP1
add gateway=10.10.10.1

The first 2 routes will be used by our policies. The third route will be used by any traffic that does not have a policy defined and by traffic from the router itself.

Next, we need to define our routing rules. There are many ways to accomplish this, but what I will show here is the cleanest way I have found to implement a working policy.

/ip route rule
add dst-address=192.168.0.0/24 action=lookup table=main
add dst-address=192.168.1.0/24 action=lookup table=main
add dst-address=10.10.10.0/30 action=lookup table=main
add dst-address=10.10.11.0/30 action=lookup table=main
add src-address=10.10.10.0/30 action=lookup table=ISP1
add src-address=10.10.11.0/30 action=lookup table=ISP2
add routing-mark=ISP1 action=lookup table=ISP1
add routing-mark=ISP2 action=lookup table=ISP2


The first 3 rules tell the router to ignore routing marks for all packets destined for the “connected” networks. The next 2 rules that tell the router to use ISP1 and ISP2 for the traffic FROM the router on those particular interfaces. These rules will allow us to manage the router remotely from either of the 2 “public” interfaces. Finally, there are 2 rules that use the ISP1 and ISP2 tables for traffic that we will “mark” for those tables.

Finally, we need to define the policies. A policy basically says, “use this routing table for this type of traffic”. Policies are implemented in the firewall using Mangle. We will use a couple of examples. In our first example, we will use the following policy:

All traffic from the 192.168.0.0/24 network will use ISP1 and all traffic from the 192.168.1.0/24 network will use ISP2. Here is the implementation:


/ip firewall mangle
add chain=prerouting src-address=192.168.0.0/24 action=mark-routing \
new-routing-mark=ISP1 passthrough=no

add chain=prerouting src-address=192.168.1.0/24 action=mark-routing \
new-routing-mark=ISP2 passthrough=no

The above 2 rules are all that are needed. Note that the “new-routing-mark” matches the “routing-mark” entry in the route statements we added earlier.

A common policy is to route certain traffic (by type) over certain networks. For example, we could implement a policy like the following:

Route all http, smtp, dns and pop3 traffic over our ISP1 circuit and all other traffic over the ISP2 circuit.

/ip firewall mangle
add chain=prerouting dst-port=80 protocol=tcp action=mark-routing \
new-routing-mark=ISP1 passthrough=no

add chain=prerouting dst-port=25 protocol=tcp action=mark-routing \
new-routing-mark=ISP1 passthrough=no

add chain=prerouting dst-port=110 protocol=tcp action=mark-routing \
new-routing-mark=ISP1 passthrough=no

add chain=prerouting dst-port=53 protocol=udp action=mark-routing \
new-routing-mark=ISP1 passthrough=no

add chain=prerouting action=mark-routing \
new-routing-mark=ISP2 passthrough=no

The above 4 rules will implement the policy requirement I stated. NOTE: In this policy, Peer-to-peer traffic will use ISP2, unless the peer-to-peer traffic tries to use one of the ports defined by the policy.

Peer-to-peer traffic requires more than one packet to identify, so if you want to implement a policy that applies to this traffic, you have to define OTHER traffic first, and let the peer to peer traffic follow the “default” action, as I did above.

This is not a complete description of all the possible implementations for policy routing, but it will give you a head start in implementing policy routing. I hope you find this article helpful.

---

Ko može li mi neko napisat kako da izrutiram promet da mogu igrat mrežno igre između mreže HOTSPOT i eth2 LAN?

Nikako ja to ne mogu dobro postavit