netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[2.6 PATCH] sctp - provide valid tos and oif values for ip_route_output_

from [Julian Anastasov] [Permanent Link][Original]
To: netdev@xxxxxxxxxxx
Subject: [2.6 PATCH] sctp - provide valid tos and oif values for ip_route_output_key
From: Julian Anastasov <ja@xxxxxx>
Date: Wed, 3 Dec 2003 01:49:12 +0200 (EET)
Cc: Sridhar Samudrala <sri@xxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx 
        Hello,

        I'm not sure if this change is needed (it is not tested).
Is SO_BINDTODEVICE supported for SCTP? It seems it is bad for
PMTUD not to provide valid tos and oif values for the routing call.

Regards

--
Julian Anastasov <ja@xxxxxx>

Attachment: tos-sctp-1.diff
Description: SCTP tos and oif

[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [2.6 PATCH] sctp - provide valid tos and oif values for ip_route_output_key, Julian Anastasov <=
Previous by Date:  Re: [ROUTE] PMTU only works on half the time, Julian Anastasov
Next by Date:  [2.6 PATCH] bridge - provide valid tos value for ip_route_output_key, Julian Anastasov
Previous by Thread:  [PATCH] (3/8) n2 and c101 hdlc dis-embedding, Stephen Hemminger
Next by Thread:  [2.6 PATCH] bridge - provide valid tos value for ip_route_output_key, Julian Anastasov
Indexes:  [Date] [Thread] [Top] [All Lists]