[LARTC] Dual home gateway problem with redirect page

[LARTC] Dual home gateway problem with redirect page

[Mohammad Reza]

[-- Attachment #1: Type: text/plain, Size: 512 bytes --]

Dear Lists,
 
I have problem regarding multipath connection to internet behind NAT.
I use 2.4.26 kernel in RH-9.0 with Julian Anastasov patch, and   version
iproute2-ss020116 (Fedora RPM package).
Dual homing and dead gateway detection work fine as we expected, the
problem is , everytime we hit site that have redirect page address (URL
no absolute), it's doesn't reply. (ex: www.mild.com
<http://www.mild.com/> , www.kompas.com <http://www.kompas.com/> ). 
Please help me.
 
 
Regards
reza
 
 

[-- Attachment #2: Type: text/html, Size: 5031 bytes --]

RE: [LARTC] Dual home gateway problem with redirect page

[Mohammad Reza]

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

 
 
 
That site block  TCP Explicit Congestion Notification.
Wonder what kind type of firewall do that ?
 
Sorry for incovinience
 
Regards
reza
 
-----Original Message-----
From: Mohammad Reza 
Sent: Tuesday, June 29, 2004 12:10 PM
To: lartc@mailman.ds9a.nl
Cc: ja@ssi.bg
Subject: [LARTC] Dual home gateway problem with redirect page
 
Dear Lists,
 
I have problem regarding multipath connection to internet behind NAT.
I use 2.4.26 kernel in RH-9.0 with Julian Anastasov patch, and   version
iproute2-ss020116 (Fedora RPM package).
Dual homing and dead gateway detection work fine as we expected, the
problem is , everytime we hit site that have redirect page address (URL
no absolute), it's doesn't reply. (ex: www.mild.com
<http://www.mild.com/> , www.kompas.com <http://www.kompas.com/> ). 
Please help me.
 
 
Regards
reza
 
 

[-- Attachment #2: Type: text/html, Size: 9372 bytes --]

Re: [LARTC] Dual home gateway problem with redirect page

[Ed Wildgoose]

 

> That site block  TCP Explicit Congestion Notification.
>
> Wonder what kind type of firewall do that ?
>

It's not that uncommon for ECN to be blocked.  (It's not correct either)

I suggest that you send an email to the webmaster in each location and 
try to ask a human to correct this problem.  However, a workaround in 
the meantime is to use iptables to mangle your packets heading to that 
location to remove the ECN for the broken sites.

Search around on google, it's covered fairly well.  I even came a across 
a patch on the kernel list (and an angry conversation) which would 
automatically disable ECN for broken sites - it seems it wouldn't be 
applied for reasons like how it would be bad for us end users to have 
such a bandaid....

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/