unire 4 adsl

[anz]

Ho una RB493 e mi piacerebbe utilizzare 4 ADSL, che chiamerò A B C D, nel seguente modo:
- ADSL A in Load Balancing su C
- ADSL B backup di A
- ADSL D backup di C
e per finire, gestire la ether5 come Gateway.

p.s:
penso che per il backup sia sufficiente:
/ ip route
add dst-address=0.0.0.0/0 gateway=x.x.x.x,y.y.y.y check-gateway=ping

chi mi aiuta?

[antonioff]

Ciao,
Ti consiglio di configurare con LOAD BALACING(PCC) + FAIL OVER.

trovi molto sul sito di mikortik

[anz]

Trovati.. era quello che cercavo!
Per quanto riguarda il failover:

/ip route add gateway=192.168.1.1 check-gateway=ping
/ip route add gateway=192.168.2.1 distance=2
/ip route add gateway=192.168.3.1 check-gateway=ping
/ip route add gateway=192.168.4.1 distance=2

potrebbe andare bene?

[anz]

Posto la configurazione.. Appena ho tempo la provo e ti faccio sapere com'è andata

Codice: Seleziona tutto

/ ip address
add address=192.168.1.100/24 network=192.168.1.0 broadcast=192.168.1.255 interface=ether1
add address=192.168.2.100/24 network=192.168.2.0 broadcast=192.168.2.255 interface=ether2
add address=192.168.3.100/24 network=192.168.3.0 broadcast=192.168.3.255 interface=ether3
add address=192.168.4.100/24 network=192.168.4.0 broadcast=192.168.4.255 interface=ether4
add address=192.168.0.1/24 network=192.168.0.0 broadcast=192.168.0.255 interface=Local

/ ip firewall mangle
add chain=input in-interface=ether1 action=mark-connection new-connection-mark=ether1_conn
add chain=input in-interface=ether2 action=mark-connection new-connection-mark=ether2_conn
add chain=input in-interface=ether3 action=mark-connection new-connection-mark=ether3_conn
add chain=input in-interface=ether4 action=mark-connection new-connection-mark=ether4_conn
add chain=output connection-mark=ether1_conn action=mark-routing new-routing-mark=to_ether1   
add chain=output connection-mark=ether2_conn action=mark-routing new-routing-mark=to_ether2
add chain=output connection-mark=ether3_conn action=mark-routing new-routing-mark=to_ether3   
add chain=output connection-mark=ether4_conn action=mark-routing new-routing-mark=to_ether4
add chain=prerouting dst-address=192.168.1.100/24 action=accept in-interface=Local
add chain=prerouting dst-address=192.168.2.100/24 action=accept in-interface=Local
add chain=prerouting dst-address=192.168.3.100/24 action=accept in-interface=Local
add chain=prerouting dst-address=192.168.4.100/24 action=accept in-interface=Local
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:4/0 action=mark-connection new-connection-mark=ether1_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:4/1 action=mark-connection new-connection-mark=ether2_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:4/2 action=mark-connection new-connection-mark=ether3_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:4/3 action=mark-connection new-connection-mark=ether4_conn passthrough=yes
add chain=prerouting connection-mark=ether1_conn in-interface=Local action=mark-routing new-routing-mark=to_ether1
add chain=prerouting connection-mark=ether2_conn in-interface=Local action=mark-routing new-routing-mark=to_ether2
add chain=prerouting connection-mark=ether3_conn in-interface=Local action=mark-routing new-routing-mark=to_ether3
add chain=prerouting connection-mark=ether4_conn in-interface=Local action=mark-routing new-routing-mark=to_ether4

/ ip route
add dst-address=0.0.0.0/0 gateway=192.168.1.1 routing-mark=to_ether1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.2.1 routing-mark=to_ether2 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.3.1 routing-mark=to_ether3 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.4.1 routing-mark=to_ether4 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.1.1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.2.1 distance=2
add dst-address=0.0.0.0/0 gateway=192.168.3.1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.4.1 distance=2

/ ip firewall nat
add chain=srcnat out-interface=ether1 action=masquerade
add chain=srcnat out-interface=ether2 action=masquerade
add chain=srcnat out-interface=ether3 action=masquerade
add chain=srcnat out-interface=ether4 action=masquerade


[parabolino]

Per quanto riguarda il failover:

/ip route add gateway=192.168.1.1 check-gateway=ping
/ip route add gateway=192.168.2.1 distance=2
/ip route add gateway=192.168.3.1 check-gateway=ping
/ip route add gateway=192.168.4.1 distance=2

potrebbe andare bene?

Non credo sia sufficiente per raggingere il tuo scopo.
Le rotte con metrica 2 verranno utilizzate solo in caso di mancata risposta al ping
dei rispettivi GW.
Immaginando che siano dei router ADSL, essi risponderanno sempre al ping, anche
se l'ADSL è down... per attivare il failover dovrai fare qualche operazione manuale
tipo scollegare il cavo o spegnere il router con ADSL down in modo da non farlo
più rispondere...

[anz]

capito.. a questo punto conviene tenerne solo uno configurato come FailOver, che subentra in caso di crash, riavvio, spegnimento di un router adsl.E gli altri PCC

[parabolino]

Non so il traffico che generi, ma io metterei in PCC tutte le ADSL in modo da sfruttarle tutte e modificherei al volo la configurazione in caso di down di una ADSL.

Le ADSL sono PPPoE, PPPoA o altro protocollo?

[anz]

Le ADSL sono PPPoE, PPPoA o altro protocollo?

L'adsl A è PPPoE, la B è PPPoE, la C è PPPoA e la D è una ADSL satellitare bidirezionale (penso PPPoE)

[anz]

Ho provato la configurazione.. Funziona quasi alla perfezione, ma l'ether4 non ne vuole sapere. Non fa ne il PCC ne il failover.. qualche idea?

[parabolino]

Per favore, incolla qui la tua configurazione completa, meglio se in un file