[bulkwayne]

Sir Dans.

Sharing lang po.  I have here my configuration on running a PCC method. Main configuration is load balancing with failover. I found out by defining each of the same packet to two out interface will not break the connection even it is https.

example:

Download:
ml-packet 

Upload:
ISP1
ml-packet

ISP2
ml-packet

So if in load balancing, my configuration will be Mark Packet passthrough=no.

However, if ISP 2 is in high latency, packet marks routed to ISP 1 only, 

So Mark Packet Passthrough=Yes, then Mark routing passthrough=no. 
Then define a routing mark to your Routes.

Sana ma improve po natin eto. 

A partial of this configuration has been with me since 2015, and ever since trying to improve this.

[Dans]

PCC is inherently can break a connection session especially in tcp lalo na magkakaiba ang public ip ng mga WANs mo, if one of the line goes down, no matter how good your configuration is, however there are several sites that are "connection friendly", but very rare. (actually i know nothing that actually worked)

this is what happened with the PCC, simple explanation lang ito ha, i will not elaborate more.

supposed.. meron kang dalawang WAN at may public ip din

WAN1 (104.104.10.50)
WAN2 (122.165.33.5)

then, meron kang 2 clients na naka NAT sa mga WAN mo

Client1 (192.168.1.10)
Client2 (192.168.1.20)

supposed si client1 ay dumaan sa WAN1, at si client2 ay dumaan sa WAN2.
then si client1 ay may connection session sa isang server sa internet using the designated WAN na nakuha nya sa PCC,

ang outgoing IP ni client1 ay yung public ip ni WAN1 na 104.104.10.50 at yung server ay may public ip na 105.20.30.2

during the PCC, yung public ip na kilala ng server na may session si client1 ang kilala ng server,

WAN1 (104.104.10.50) --> Server (105.20.30.2) - remember, ang kilala ni server ay ang public ip ni WAN1 na nilabasan ni client1

so once na mag-down ang WAN1, at nag switch over sa WAN2 ang client1 mo, yung server na may session si client1 ay mag "stall and terminate" dahil hindi na bumalik sa server yung public ip ni WAN1, hindi kilala ni server ang Public IP ni WAN2 dahil hindi naman yon ang naging initial public IP ng client1 nung nag initiate ng connection, so considered na broken na agad ang session... walang continuity.

so, how to test it?

for simple test..

mag continuous ping or trace route ka sa client1, tapos idown mo ang isa sa mga WAN mo kung saan dumaan si client1, you will see na mag timeout na agad yan, walang continuity, don't cancel the session ha.

for a better test.

mag connection session ka sa server using TCP like ssh, telnet, ftp, or even mail transfer.
then i-down mo ang isa sa mga WAN na dinaan mo, you will see na broken connection na agad yan. you must re-do your session para sa WAN2 na dumaan, pero yung unang session mo ay terminated na,

sa speedtest nga eh, during the latency test, sa isang WAN lang ang natetest ng speedtest kapag meron kang multiple WAN.

so you understand how PCC is inherently can break connections?

the only way na may continuity ang session mo at may multiple WAN/upstream ka ay kung naka peering ka sa provider mo.

[bulkwayne]

Thank you sir Dans. Clear po eto.

Follow-up questions po.

Do we need an ASN for peering sir Dans?

Yung si BGP po ba via TCP?

[Dans]

Thank you sir Dans. Clear po eto.

Follow-up questions po.

Do we need an ASN for peering sir Dans?

Yung si BGP po ba via TCP?

yes and no.

yes if you have your own ip-block from apnic, to begin with, di ka naman makakakuha ng ip-block sa apnic kung wala kang asn.
asn is tied to your ip-prefixes resources

no if your ip-block is leased to you by your provider. and if your ip-prefixes is own by your provider, tapos gusto mong maki-pag peer sa ibang provider mo, chances are... hindi ka pwedeng makipag-peering, kasi yung asn owner ang dapat makipag-coordinate sa ibang provider.

[bulkwayne]

In this case sir, viable po ba real hardware bonding/aggregator appliances for the purpose of combining two or more isp sir? Considering the above scenario, na nagkaubusan na ipv4 ips?

[Dans]

In this case sir, viable po ba real hardware bonding/aggregator  appliances for the purpose of combining two or more isp sir? Considering the above scenario, na nagkaubusan na ipv4 ips?

this is what you must understand.

maraming devices na pwedeng mag-aggregate/bonding ng speed, but in reality, hindi naman talaga nag-aaggregate yan lalo na pag magkaiba ang provider mo at hindi ka naman naka-peering sa kanila


the principle of.. "wherever you go out, you must come back on the same way"

in other words, kung may 2 provider ka, let say may pldt ka na ang speed ay 100mbps/100mbps and globe na 500mbps/500mbps , at kung lumabas ka sa pldt, sa pldt ka rin babalik, don't expect na babalik ka sa globe mo.

pwede lang yan sa mga peering system, na pag lumbas ka sa pldt eh pwede ka bumalik sa globe.

[bulkwayne]

In this case sir, viable po ba real hardware bonding/aggregator  appliances for the purpose of combining two or more isp sir? Considering the above scenario, na nagkaubusan na ipv4 ips?

this is what you must understand.

maraming devices na pwedeng mag-aggregate/bonding ng speed, but in reality, hindi naman talaga nag-aaggregate yan lalo na pag magkaiba ang provider mo at hindi ka naman naka-peering sa kanila


the principle of.. "wherever you go out, you must come back on the same way"

in other words, kung may 2 provider ka, let say may pldt ka na ang speed ay 100mbps/100mbps and globe na 500mbps/500mbps , at kung lumabas ka sa pldt, sa pldt ka rin babalik, don't expect na babalik ka sa globe mo.

pwede lang yan sa mga peering system, na pag lumbas ka sa pldt eh pwede ka bumalik sa globe.

Loud and Clear sir. Thank you po. So balik sa drawing board for an ASN and IP Address and peering hopefully.

[Dans]

In this case sir, viable po ba real hardware bonding/aggregator  appliances for the purpose of combining two or more isp sir? Considering the above scenario, na nagkaubusan na ipv4 ips?

this is what you must understand.

maraming devices na pwedeng mag-aggregate/bonding ng speed, but in reality, hindi naman talaga nag-aaggregate yan lalo na pag magkaiba ang provider mo at hindi ka naman naka-peering sa kanila


the principle of.. "wherever you go out, you must come back on the same way"

in other words, kung may 2 provider ka, let say may pldt ka na ang speed ay 100mbps/100mbps and globe na 500mbps/500mbps , at kung lumabas ka sa pldt, sa pldt ka rin babalik, don't expect na babalik ka sa globe mo.

pwede lang yan sa mga peering system, na pag lumbas ka sa pldt eh pwede ka bumalik sa globe.

Loud and Clear sir. Thank you po. So balik sa drawing board for an ASN and IP Address and peering hopefully.

pakilala ka nga? di kita kilala eh.