Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Ricardo Soria
--- Andy Furniss [EMAIL PROTECTED] escribió: Andy Furniss wrote: So, my question would be, how to 'divide' or 'recognize' incoming and outgoing traffic, and to treat it as different channels?? I was thinking about using a IMQ device for incoming traffic, but this apperas to be a

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Andy Furniss
Ricardo Soria wrote: --- Andy Furniss [EMAIL PROTECTED] escribió: Andy Furniss wrote: So, my question would be, how to 'divide' or 'recognize' incoming and outgoing traffic, and to treat it as different channels?? I was thinking about using a IMQ device for incoming traffic, but this apperas

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Andy Furniss
Ricardo Soria wrote: There may be traffic for a local (linux box) process, but the most of the traffic will be redirected or passed. Do you want to shape eth0 aswell as the internet link or is it OK for spare bandwidth? I cannot translate/understand perfectly this question, but I do need to

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Ricardo Soria
--- Andy Furniss [EMAIL PROTECTED] escribió: Ricardo Soria wrote: --- Andy Furniss [EMAIL PROTECTED] escribió: Andy Furniss wrote: So, my question would be, how to 'divide' or 'recognize' incoming and outgoing traffic, and to treat it as different channels?? I was thinking

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Ricardo Soria
--- Andy Furniss [EMAIL PROTECTED] escribió: Ricardo Soria wrote: So, returning to the question that originated this discussion, how can I diferentiate/separate incoming and outgoing traffic for the same interface (eth0), without confusing each other, and without using IMQ

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Ricardo Soria
--- Andy Furniss [EMAIL PROTECTED] escribió: Ricardo Soria wrote: Very thanks for your suggestion, but... Consider that the traffic that comes from the cisco 1600 is not originated into itself; this router is just passing traffic that comes from Internet (infinite source MAC

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Andy Furniss
Ricardo Soria wrote: So, returning to the question that originated this discussion, how can I diferentiate/separate incoming and outgoing traffic for the same interface (eth0), without confusing each other, and without using IMQ devices if possible ?? My mails don't seem to be getting to/from

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-12-19 Thread Andy Furniss
Ricardo Soria wrote: Very thanks for your suggestion, but... Consider that the traffic that comes from the cisco 1600 is not originated into itself; this router is just passing traffic that comes from Internet (infinite source MAC addresses possible) I don't think so - ethernet is link layer ,

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-25 Thread Andy Furniss
Ricardo Soria wrote: Well, as I promised, here I am again :-) I have not got ESFQ yet, but what I think really helped was shorting bandwidth capacity to its 88%. But here I have a new problem again: there are certain moments when I am really running out of bandwidth. The scenario now is as

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-25 Thread Andy Furniss
Andy Furniss wrote: So, my question would be, how to 'divide' or 'recognize' incoming and outgoing traffic, and to treat it as different channels?? I was thinking about using a IMQ device for incoming traffic, but this apperas to be a 'little bit' more complicated that what I expected. So, may

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-24 Thread Ricardo Soria
Well, as I promised, here I am again :-) I have not got ESFQ yet, but what I think really helped was shorting bandwidth capacity to its 88%. But here I have a new problem again: there are certain moments when I am really running out of bandwidth. The scenario now is as follows: I am using my

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-24 Thread Ricardo Soria
that. - Original Message - From: Ricardo Soria [EMAIL PROTECTED] To: Andy Furniss [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 1:08 PM Subject: Re: [LARTC] SEPARATING VOIP AND SURFING Well, as I promised, here I am again :-) I have not got ESFQ yet

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-24 Thread Rick Marshall
PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 1:08 PM Subject: Re: [LARTC] SEPARATING VOIP AND SURFING Well, as I promised, here I am again :-) I have not got ESFQ yet, but what I think really helped was shorting bandwidth capacity to its 88%. But here I have a new problem

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-23 Thread Ricardo Soria
Dear friends: Very thanks for all your help. I have made many changes to my scrip this days, fixing up some problems and mistakes I found. It seems now I have a very acceptable VoIP quality, and everything is working notably better. I am actually using 450kbit of the total 512 available. Next

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-17 Thread Ricardo Soria
Jason Boxman wrote: On Monday 15 November 2004 20:06, Ricardo Soria wrote: snip Dear Andy: Very thanks for your answer. However, I need a little bit more extended explanation. First, you say that I should back off more from link speed - total ceils to about 80% and share that

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-17 Thread Andy Furniss
Ricardo Soria wrote: 1. So, starting at 80% of total 512kbit bandwidth (410kbit), there would be a waste of 102kbit. Is this completely necessary?? I think this is to ensure I have the queue on my side, and the queue is not on the side of the ISP. But, I fell tempted to think that 102kbit is

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-17 Thread Rick Marshall
Andy Furniss wrote: Ricardo Soria wrote: 1. So, starting at 80% of total 512kbit bandwidth (410kbit), there would be a waste of 102kbit. Is this completely necessary?? I think this is to ensure I have the queue on my side, and the queue is not on the side of the ISP. But, I fell tempted to

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-16 Thread Andy Furniss
Jason Boxman wrote: On Monday 15 November 2004 20:06, Ricardo Soria wrote: snip Dear Andy: Very thanks for your answer. However, I need a little bit more extended explanation. First, you say that I should back off more from link speed - total ceils to about 80% and share that between interactive

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-16 Thread Jason Boxman
On Tuesday 16 November 2004 09:53, Andy Furniss wrote: snip I would do a bit more work to priorotise dns/empty acks/small tcp etc. as well as VOIP, then give them a class with plenty of rate spare and make bulk borrow. This would mean that each user would notice a bit less the fact they have

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-16 Thread Andy Furniss
Jason Boxman wrote: On Tuesday 16 November 2004 09:53, Andy Furniss wrote: snip I would do a bit more work to priorotise dns/empty acks/small tcp etc. as well as VOIP, then give them a class with plenty of rate spare and make bulk borrow. This would mean that each user would notice a bit less the

Re: [LARTC] SEPARATING VOIP AND SURFING

2004-11-15 Thread Andy Furniss
Ricardo Soria wrote: Dear list: I have a problem I cannot handle yet, and need to solve it as soon as possible. Would be very greatful with anybody who can help me. I have a 512/512 link to internet, that I want to share between several computers. I have eth0, with a public IP address, conected

[LARTC] SEPARATING VOIP AND SURFING

2004-11-13 Thread Ricardo Soria
Dear list: I have a problem I cannot handle yet, and need to solve it as soon as possible. Would be very greatful with anybody who can help me. I have a 512/512 link to internet, that I want to share between several computers. I have eth0, with a public IP address, conected to Internet, and