iptables diagram (ex: ipchains + mark in output chain ?)
Hello,
Quoted 4 lines · Ciprian Niculescu
so you say that are 3 routing decision:
- after nat prerouting
- afterlocal_process, and before mangle output
- before nat postrouting
Basicly, there are 2 routing decisions, for the others
I like the name rerouting:
1. Input Routing: after prerouting, kernel performs source validation and nexthop decision, result: local_deliver/forwarding
2. Output Routing: local_process selects source address, creates connected route or selects route for each packet. The resolved route is attached to the packet and is used later. The Netfilter's LOCAL_OUT chain detects complete packet which is obviously loaded with some addresses. Which ones do you think if routing _decision_ is not performed? :)
3. Output Rerouting: netfilter at LOCAL_OUT changes the already selected output route if any of the routing keys are changed:
addresses, tos, nfmark, etc. The intention is the packet to change its attached route and probably to go in another direction. The connected sockets do not notice this change, they remain connected to the initial route.
Quoted 1 line
what is the use of the routing decision after local process???
see 2.
Note also that after FORWARD there is no routing
decision :)))
I'll not iterate this issue anymore. We already disturb
the LARTC subscribers :)
Regards
--
Julian Anastasov <[email protected]>
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Sorry, Julian, I can't follow the list every day, it goes too fast for my schedule.
You wrote,
Quoted 5 lines
Basicly, there are 2 routing decisions, for the others
I like the name rerouting:1. Input Routing: after prerouting, kernel performs source validation and nexthop decision, result: local_deliver/forwarding
OK, I understand.
Quoted 6 lines
2. Output Routing:
local_processselects source address, creates connected route or selects route for each packet. The resolved route is attached to the packet and is used later. The Netfilter\'sLOCAL_OUTchain detects complete packet which is obviously loaded with some addresses. Which ones do you think if routing _decision_ is not performed? :)
This phrase from you is very important:
** Which ones do you think if routing _decision_ is not performed? **
Now I understand; LOCAL_OUT (mangle, nat & filter) must have a destination address to work with and this must be written before by "Output Routing".
Quoted 6 lines
3. Output Rerouting: netfilter at
LOCAL_OUTchanges the already selected output route if any of the routing keys are changed:
addresses, tos, nfmark, etc. The intention is the packet to change its attached route and probably to go in another direction. The connected sockets do not notice this change, they remain connected to the initial route.
I'm not very clear here. Can I suppose you are talking about mangle and nat OUTPUT and you call it "Output Rerouting"?
Quoted 1 line
Note also that after FORWARD there is no routing decision :)))
Ok, but in FORWARD itself?
I read this in an article from Saravanan Radhakrishnan; the ** are mine.
"The basic principle involved in the implementation of QoS in linux is shown in Figure 1. This figure shows how the kernel processes incoming packets, and how it generates packets to be sent to the network. The input de-multiplexer examines the incoming packets to determine if the packets are destined for the local node. If so, they are sent to the higher layer for further processing. If not, it sends the packets to the forwarding block. ** The forwarding block, which may also received locally generated packets from the higher layer **, looks up the routing table and determines the next hop for the packet. After this, it queues the packets to be transmitted on the output interface. It is at this point that the linux traffic control comes into play. Linux traffic control can be used to build a complex combination of queuing disciplines, classes and filters that control the packets that are sent on the output interface."
+---------------+
+---->| TCP, UDP, ... |
| +---------------+
| | TRAFFIC CONTROL
| v |
+---------------------+ +------------+ +----------------+
-->|Input de-multiplexing|-->| Forwarding |-->| Output queuing |-->
+---------------------+ +------------+ +----------------+Figure 1
An another article from Werner Almesberger, Jamal Hadi Salim and Alexey Kuznetsov says:
""Forwarding" includes the selection of the output interface, the selection of the next hop, encapsulation, etc. Once all this is done, packets are queued on the respective output interface. This is the point where traffic control comes into play. Traffic control can, among other things, decide if packets are queued or if they are dropped (e.g. if the queue has reached some length limit, or if the traffic exceeds some rate limit), it can decide in which order packets are sent (e.g. to give priority to certain flows), it can delay the sending of packets (e.g. to limit the rate of outbound traffic), etc."
With all this info I'm trying an improved diagram:
Network
-----------+-----------
|
+-------+------+
| mangle |
| PREROUTING | <- MARK REWRITE
+-------+------+
|
+-------+------+ Policy rule database
| PRDB | <- controlled by ip rule
+-------+------+
|
+-------+------+
| nat |
| PREROUTING | <- DEST REWRITE
+-------+------+
|
packet is for +-------+------+ packet is for
this address | INPUT | another address
+--------------+ ROUTING +---------------+
| +--------------+ |
+-------+------+ |
| filter | |
| INPUT | |
+-------+------+ |
| |
+-------+------+ |
| Local | |
| Process | |
+-------+------+ |
| |
+-------+------+ |
| OUTPUT | +-------+-------+
| ROUTING | | filter |
+-------+------+ | FORWARD |
| +-------+-------+
+-------+------+ |
| mangle | |
| OUTPUT | MARK REWRITE |
+-------+------+ |
| |
+-------+------+ |
| nat | |
| OUTPUT | DEST REWRITE |
+-------+------+ |
| |
+-------+------+ |
| filter | |
| OUTPUT | |
+-------+------+ |
| |
| |
+----------------+ +--------------------+
| |
| |
+--+-------+---+
| | selection of the output
interface,
| FORWARDING | selection of the next hop,
+-------+------+ encapsulation, etc.
|
|
+-------+------+
| nat |
| POSTROUTING | SOURCE REWRITE
+-------+------+
|
|
+-------+------+
| TRAFFIC |
| QUEUE | <- controlled by tc
+-------+------+
|
|
-----------+-----------
NetworkWhat's your opinion?
Quoted 2 lines
I'll not iterate this issue anymore. We already disturb the LARTC subscribers :)
Honestly I don't think this kind of discussion disturbs the list; instead avoid the list to become itself in a "cookbook" list.
I use these tools: iproute2, iptables, cipe, lvs and tc. It would be very pedagogyc to have a diagram showing how a packet transverse the kernel and which tool controls each block of the diagram.
Thanks a lot for your explanation; also excuse because I'm bother you.
Best regards,
Leonardo Balliache
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
Quoted 9 lines · Leonardo Balliache
Quoted 6 lines
3. Output Rerouting: netfilter at
LOCAL_OUTchanges the already selected output route if any of the routing keys are changed:
addresses, tos, nfmark, etc. The intention is the packet to change its attached route and probably to go in another direction. The connected sockets do not notice this change, they remain connected to the initial route.I'm not very clear here. Can I suppose you are talking about mangle and nat OUTPUT and you call it "Output Rerouting"?
Yes, mangle can reroute.
Quoted 6 lines
Quoted 1 line
Note also that after FORWARD there is no routing decision :)))
Ok, but in FORWARD itself?
I read this in an article from Saravanan Radhakrishnan; the ** are mine.
Quoted 9 lines
"The basic principle involved in the implementation of QoS in linux is shown in Figure 1. This figure shows how the kernel processes incoming packets, and how it generates packets to be sent to the network. The input de-multiplexer examines the incoming packets to determine if the packets are destined for the local node. If so, they are sent to the higher layer for further processing. If not, it sends the packets to the forwarding block. ** The forwarding block, which may also received locally generated packets from the higher layer **, looks up the routing table and determines the next hop for the packet. After this, it queues the packets
Here the input and the output routing are mixed. The input
routing determines local/forward. The output routing is performed from "higher layer". Note that the routing, the forwarding are called as functions from specific place in the code. nexthop/outdev are determined both from the input and the output routing. The Forwarding process is after routing and does not perform nexthop/outdev selection. Of course, sometimes the word Forwarding is used for the routing and forwarding :)
Quoted 5 lines
to be transmitted on the output interface. It is at this point that the linux traffic control comes into play. Linux traffic control can be used to build a complex combination of queuing disciplines, classes and filters that control the packets that are sent on the output interface."
Quoted 8 lines
+---------------+
+---->| TCP, UDP, ... |
| +---------------+
| | TRAFFIC CONTROL
| v |
+---------------------+ +------------+ +----------------+
-->|Input de-multiplexing|-->| Forwarding |-->| Output queuing |-->
+---------------------+ +------------+ +----------------+ Looks good, except that TCP, UDP do not go to Forwarding
but to Output_Routing->LOCAL_OUT(including mangle rerouting)->POST_ROUTING At least, as Forwarding I assume the process of receiving and sending the same packet but in the context of all these hooks the code that sends ICMP redirects (demanded from input routing), decs the IP TTL, performs dumb NAT and calls the filter chain. This code is used only for forwarded packets.
Quoted 7 lines
Figure 1
An another article from Werner Almesberger, Jamal Hadi Salim and Alexey Kuznetsov says:
""Forwarding" includes the selection of the output interface, the selection of the next hop, encapsulation, etc. Once all this is done, packets are
What I can say against the authors :) They said Forwarding
with big 'F' :) They simply want to say that QoS egress is when the packet reaches the output device, after post_routing in NF terms.
Quoted 11 lines
queued on the respective output interface. This is the point where traffic control comes into play. Traffic control can, among other things, decide if packets are queued or if they are dropped (e.g. if the queue has reached some length limit, or if the traffic exceeds some rate limit), it can decide in which order packets are sent (e.g. to give priority to certain flows), it can delay the sending of packets (e.g. to limit the rate of outbound traffic), etc."
With all this info I'm trying an improved diagram:
Quoted 8 lines
Network
-----------+-----------
|
+-------+------+
| mangle |
| PREROUTING | <- MARK REWRITE
+-------+------+
|ip rule is input routing, more correctly, part of the routing, not before nat PREROUTING
Quoted 9 lines
+-------+------+ Policy rule database
| PRDB | <- controlled by ip rule
+-------+------+
|
+-------+------+
| nat |
| PREROUTING | <- DEST REWRITE
+-------+------+
|You can add here ipchains FILTER and QoS Ingress :)
Quoted 31 lines
packet is for +-------+------+ packet is for
this address | INPUT | another address
+--------------+ ROUTING +---------------+
| +--------------+ |
+-------+------+ |
| filter | |
| INPUT | |
+-------+------+ |
| |
+-------+------+ |
| Local | |
| Process | |
+-------+------+ |
| |
+-------+------+ |
| OUTPUT | +-------+-------+
| ROUTING | | filter |
+-------+------+ | FORWARD |
| +-------+-------+
+-------+------+ |
| mangle | |
| OUTPUT | MARK REWRITE |
+-------+------+ |
| |
+-------+------+ |
| nat | |
| OUTPUT | DEST REWRITE |
+-------+------+ |
| |
+-------+------+ |Quoted 7 lines
| filter | |
| OUTPUT | |
+-------+------+ |
| |
| |
+----------------+ +--------------------+
| | Remove the forwarding from here, the both clones already
performed selection of next hop (routing). Filter FORWARD was in the forwarding.
Quoted 7 lines
| |
+--+-------+---+
| | selection of the output
interface,
| FORWARDING | selection of the next hop,
+-------+------+ encapsulation, etc.
|Place for ipchains FILTER
Quoted 21 lines
| +-------+------+ | nat | | POSTROUTING | SOURCE REWRITE +-------+------+ | | +-------+------+ | TRAFFIC | | QUEUE | <- controlled by tc +-------+------+ | | -----------+----------- NetworkWhat's your opinion?
Quoted 2 lines
I'll not iterate this issue anymore. We already disturb the LARTC subscribers :)
Quoted 6 lines
Honestly I don't think this kind of discussion disturbs the list; instead avoid the list to become itself in a "cookbook" list.
I use these tools: iproute2, iptables, cipe, lvs and tc. It would be very pedagogyc to have a diagram showing how a packet transverse the kernel and which tool controls each block of the diagram.
http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-19.html#ss19.21
after the 2.2 net diagram there are the places used from LVS. Of course, this info does not include the recent MANGLE extensions that work in all chains.
Quoted 3 lines
Best regards,
Leonardo Balliache
Regards
--
Julian Anastasov <[email protected]>
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] Re: iptables diagram (ex: ipchains + mark in output
In reply to Julian AnastasovHello all,
I am working for similar structure recently. In my cases, I am
working on IPSEC freeS/WAN. I just wonder, does anyone knows how IPSEC NAT working on which hooks/filter/chain. Based on the testing I made, I believe it is on NAT output.
One more question is when I use IPSEC, I guess all the packet will go to "local process" (network layer) to encrypt and pass to outgoing interface. If it is, is that means INPUT ROUTING is unless since all the packet (no matter the destination is) will be go to the user sapce instead of forwading chain.
Patrick
Quoted 120 lines
Quoted 9 lines
Network -----------+----------- | +-------+------+ | mangle | | PREROUTING | <- MARK REWRITE +-------+------+ |ip rule is input routing, more correctly, part of the routing, not before nat PREROUTING
Quoted 9 lines
+-------+------+ Policy rule database | PRDB | <- controlled by ip rule +-------+------+ | +-------+------+ | nat | | PREROUTING | <- DEST REWRITE +-------+------+ |You can add here ipchains FILTER and QoS Ingress :)
Quoted 31 lines
packet is for +-------+------+ packet is for this address | INPUT | another address +--------------+ ROUTING +---------------+ | +--------------+ | +-------+------+ | | filter | | | INPUT | | +-------+------+ | | | +-------+------+ | | Local | | | Process | | +-------+------+ | | | +-------+------+ | | OUTPUT | +-------+-------+ | ROUTING | | filter | +-------+------+ | FORWARD | | +-------+-------+ +-------+------+ | | mangle | | | OUTPUT | MARK REWRITE | +-------+------+ | | | +-------+------+ | | nat | | | OUTPUT | DEST REWRITE | +-------+------+ | | | +-------+------+ |Quoted 7 lines
| filter | | | OUTPUT | | +-------+------+ | | | | | +----------------+ +--------------------+ | |Remove the forwarding from here, the both clones already
performed selection of next hop (routing). Filter FORWARD was in the forwarding.Quoted 7 lines
| | +--+-------+---+ | | selection of the output interface, | FORWARDING | selection of the next hop, +-------+------+ encapsulation, etc. |Place for ipchains FILTER
Quoted 21 lines
| +-------+------+ | nat | | POSTROUTING | SOURCE REWRITE +-------+------+ | | +-------+------+ | TRAFFIC | | QUEUE | <- controlled by tc +-------+------+ | | -----------+----------- NetworkWhat's your opinion?
Quoted 2 lines
I'll not iterate this issue anymore. We already disturb the LARTC subscribers :)
Quoted 6 lines
Honestly I don't think this kind of discussion disturbs the list; instead avoid the list to become itself in a "cookbook" list.
I use these tools: iproute2, iptables, cipe, lvs and tc. It would be very pedagogyc to have a diagram showing how a packet transverse the kernel and which tool controls each block of the diagram.
http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-19.html#ss19.21
after the 2.2 net diagram there are the places used from LVS. Of course, this info does not include the recent MANGLE extensions that work in all chains.
Quoted 3 lines
Best regards,
Leonardo Balliache
Quoted 9 lines
Regards
--
Julian Anastasov <[email protected]>_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hi all,
Is it possible to mark packets (fwmark in mangle table of some sort) after ingress policing and before Input routing? I need the ingress policer (ingress queue), to filter and classify packets first, then the firewall has to filter them again and set the fwmark. All this has to be done before the packet reaches its "routing table".
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Network -----------+----------- | +-------+------+ | mangle | | PREROUTING | <- MARK REWRITE +-------+------+ |
Quoted 5 lines
Quoted 5 lines
ip rule is input routing, more correctly, part of the routing, not before nat PREROUTING
Quoted 1 line
+-------+------+ Policy rule
database
Quoted 1 line
Quoted 1 line
Quoted 1 line
| PRDB | <- controlled by ip
rule
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
+-------+------+ |
At this point I should need another mangle table->
Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
+-------+------+ | nat | | PREROUTING | <- DEST REWRITE +-------+------+ |You can add here ipchains FILTER and QoS Ingress :)
Quoted 16 lines
Quoted 8 lines
Quoted 8 lines
packet is for +-------+------+ packet is for this address | INPUT | another address +--------------+ ROUTING +---------------+ | +--------------+ | +-------+------+ | | filter | | | INPUT | | +-------+------+ |Quoted 8 lines
Quoted 8 lines
| | +-------+------+ | | Local | | | Process | | +-------+------+ | | | +-------+------+ | | OUTPUT |
+-------+-------+ > > > | ROUTING | | filter | > > > +-------+------+ | FORWARD | > > > | +-------+-------+ > > > +-------+------+ | > > > | mangle | | > > > | OUTPUT | MARK REWRITE | > > > +-------+------+ | > > > | | > > > +-------+------+ | > > > | nat | | > > > | OUTPUT | DEST REWRITE | > > > +-------+------+ | > > > | | > > > +-------+------+ |
Quoted 14 lines
Quoted 14 lines
Quoted 8 lines
| filter | | | OUTPUT | | +-------+------+ | | | | | +----------------+ +--------------------+ | |Remove the forwarding from here, the both clones already performed selection of next hop (routing). Filter FORWARD was in the forwarding.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
| | +--+-------+---+ | | selection of the outputinterface,
| FORWARDING | selection of the next
hop,
Quoted 22 lines
Quoted 22 lines
Quoted 2 lines
+-------+------+ encapsulation, etc. |Place for ipchains FILTER
Quoted 16 lines
| +-------+------+ | nat | | POSTROUTING | SOURCE REWRITE +-------+------+ | | +-------+------+ | TRAFFIC | | QUEUE | <- controlled by tc +-------+------+ | | -----------+----------- Network
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
What's your opinion?
Quoted 2 lines
I'll not iterate this issue anymore. We already disturb the LARTC subscribers :)
Honestly I don't think this kind of discussion disturbs the list;
instead
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
avoid the list to become itself in a "cookbook" list.
I use these tools: iproute2, iptables, cipe, lvs and tc. It would be
very
Quoted 1 line
Quoted 1 line
Quoted 1 line
pedagogyc to have a diagram showing how a packet transverse the kernel
and
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
which tool controls each block of the diagram.
http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-19.html#ss19.2
1
Quoted 11 lines
Quoted 11 lines
after the 2.2 net diagram there are the places used from LVS. Of course, this info does not include the recent MANGLE extensions that work in all chains.
Quoted 3 lines
Best regards,
Leonardo Balliache
Regards
Cheers,
Jan
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
I'd very much like to see this diagram again with all the updates.
Thanks ...John
Quoted 154 lines · Jan Coppens
Hi all,
Is it possible to mark packets (fwmark in mangle table of some sort) after ingress policing and before Input routing? I need the ingress policer (ingress queue), to filter and classify packets first, then the firewall has to filter them again and set the fwmark. All this has to be done before the packet reaches its "routing table".
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Network -----------+----------- | +-------+------+ | mangle | | PREROUTING | <- MARK REWRITE +-------+------+ |Quoted 5 lines
Quoted 5 lines
ip rule is input routing, more correctly, part of the routing, not before nat PREROUTING
Quoted 1 line
+-------+------+ Policy ruledatabase
Quoted 1 line
Quoted 1 line
Quoted 1 line
| PRDB | <- controlled by ip
rule
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
+-------+------+ |At this point I should need another mangle table->
Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
+-------+------+ | nat | | PREROUTING | <- DEST REWRITE +-------+------+ |You can add here ipchains FILTER and QoS Ingress :)
Quoted 16 lines
Quoted 8 lines
Quoted 8 lines
packet is for +-------+------+ packet is for this address | INPUT | another address +--------------+ ROUTING +---------------+ | +--------------+ | +-------+------+ | | filter | | | INPUT | | +-------+------+ |Quoted 8 lines
Quoted 8 lines
| | +-------+------+ | | Local | | | Process | | +-------+------+ | | | +-------+------+ | | OUTPUT |+-------+-------+ > > > | ROUTING | | filter | > > > +-------+------+ | FORWARD | > > > | +-------+-------+ > > > +-------+------+ | > > > | mangle | | > > > | OUTPUT | MARK REWRITE | > > > +-------+------+ | > > > | | > > > +-------+------+ | > > > | nat | | > > > | OUTPUT | DEST REWRITE | > > > +-------+------+ | > > > | | > > > +-------+------+ |Quoted 14 lines
Quoted 14 lines
Quoted 8 lines
| filter | | | OUTPUT | | +-------+------+ | | | | | +----------------+ +--------------------+ | |Remove the forwarding from here, the both clones already performed selection of next hop (routing). Filter FORWARD was in the forwarding.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
| | +--+-------+---+ | | selection of the outputinterface,
| FORWARDING | selection of the nexthop,
Quoted 22 lines
Quoted 22 lines
Quoted 2 lines
+-------+------+ encapsulation, etc. |Place for ipchains FILTER
Quoted 16 lines
| +-------+------+ | nat | | POSTROUTING | SOURCE REWRITE +-------+------+ | | +-------+------+ | TRAFFIC | | QUEUE | <- controlled by tc +-------+------+ | | -----------+----------- NetworkQuoted 6 lines
Quoted 6 lines
Quoted 6 lines
What's your opinion?
Quoted 2 lines
I'll not iterate this issue anymore. We already disturb the LARTC subscribers :)
Honestly I don't think this kind of discussion disturbs the list;
instead
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
avoid the list to become itself in a "cookbook" list.
I use these tools: iproute2, iptables, cipe, lvs and tc. It would be
very
Quoted 1 line
Quoted 1 line
Quoted 1 line
pedagogyc to have a diagram showing how a packet transverse the kernel
and
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
which tool controls each block of the diagram.
http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-19.html#ss19.2
1Quoted 11 lines
Quoted 11 lines
after the 2.2 net diagram there are the places used from LVS. Of course, this info does not include the recent MANGLE extensions that work in all chains.
Quoted 3 lines
Best regards,
Leonardo Balliache
Regards
Cheers,
Jan
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Signature · 8 lines
John Telford - Owner JohnTelford.com LLC 503-292-6865 - fax:503-292-3094 [email protected] - www.johntelford.com _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] Re: iptables diagram (ex: ipchains + mark in output chain
In reply to Julian AnastasovQuoted 2 lines · John Telford
I'd very much like to see this diagram again with all the updates.
I'd be willing to draw it in Dia afterward ... :
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 4 lines · Michael T. Babcock
Quoted 1 line · John Telford
I'd very much like to see this diagram again with all the updates.
I'd be willing to draw it in Dia afterward ... :
And I was waiting for the final picture to put it on www.docum.org :)
Stef
Signature · 7 lines
[email protected] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.openprojects.net _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/