(Courriels de diversion: <remunererez@surbaissees-intolerances.com> <hydrographique@egaient-rassoirai.com> <internerez@precautionneras-debâcles.com> <infestera@crissant-rhumatisantes.com> <contrecarrerais@annoterais-oeils-de-boeuf.com> <clones@pelleterie-inversez.com> <platanes@exerceras-rosie.com> <parcellise@ovationnant-piegeais.com> <empressais@deferlait-rougeoyees.com> <alleges@embuer-deshabituions.com> )
Bonjour, Merci à ceux qui ont répondu à mon premier mail. J'ai presque fini, mais je bloque sur quelques points. Je vous donne le texte complet (pour le contexte), et j'encadrerai par des ?? les parties à traduire : 1) For sending bulk data, the internet generally works better when using larger packets. ?? Each packet implies a routing decision, when sending a 1 megabyte file, this can either mean around 700 packets when using packets that are as large as possible, or 4000 if using the smallest default. ?? 2)?? An advantage of the fact that it is not a brige lies in the fact that packets really pass through the kernel, and can be filtered, changed, redirected or rerouted. ?? 3) Another advantage of a pseudo-bridge is that it does not pass packets it does not understand - thus cleaning your network of a lot of ??cruft??. In cases where you need this ??cruft?? (like SAP packets, or Netbeui), use a real bridge. 4) ?? In the bad old days ?? , it used to be possible to instruct the Linux Kernel to perform 'proxy-ARP' for just any subnet. So, to configure a pseudo-bridge, you would have to specify both the proper routes to both sides of the bridge AND create matching proxy-ARP rules. This is bad in that it requires a lot of typing, but also because it easily allows you to make mistakes which make your bridge respond to ARP queries for networks it does not know how to route. 5) ??This does work as advertised??. Be sure to figure out which side each interface is on, otherwise you might be shaping outbound traffic in your internal interface, which won't work. Use tcpdump if needed. 6) ??The bad thing is that it's an obvious hack - it breaks 'end to end' by modifying packets??. Having said that, we use this trick in many places and it works like a charm. 7) ?? The bad news is that a bridge can cause great confusion unless it is very well documented. It does not appear in traceroutes, but somehow packets disappear or get changed from point A to point B. You should also wonder if an organization that 'does not want to change anything' is doing the right thing. ?? Merci de votre aide. N'hesitez pas, même pour une traduction partielle. Laurent Foucher --------------------------------------------------------------------- Aide sur la liste: <URL:mailto:linux-31-help@CULTe.org>Le CULTe sur le web: <URL:http://www.CULTe.org/>