From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ
Date: Wed, 12 Dec 2001 09:31:35 +0000 [thread overview]
Message-ID: <marc-lartc-100814954109331@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100814354131080@msgid-missing>
On Tue, Dec 11, 2001 at 11:50:12PM -0800, Don Cohen wrote:
> > > Here different flows are distinguished by source & dest addresses and
> > > source port.
> > >
> > > Is this right?
> >
> > Exactly.
> >
> > Regards,
> >
> > bert
>
> I think this is not quite right.
> Also dest port, right?
case __constant_htons(ETH_P_IP):
{
struct iphdr *iph = skb->nh.iph;
h = iph->daddr;
h2 = iph->saddr^iph->protocol;
if (!(iph->frag_off&htons(IP_MF|IP_OFFSET)) &&
(iph->protocol = IPPROTO_TCP ||
iph->protocol = IPPROTO_UDP ||
iph->protocol = IPPROTO_ESP))
h2 ^= *(((u32*)iph) + iph->ihl);
break;
}
In case of ipv4:
destination address
source address
ip protocol
source port/dest port tuple
I missed the fact that the first 4 octects of the IP sub-protocol header
were include in (u32).
> and re: > Subject: Re: [LARTC] sfq as solution to "Small ISP problems"
> > > > 1: SSH - to be realtime always.
> > > I don't think you want this to always be high prio - that includes scp.
> >
> > your'e right, only the real ssh traffic..
>
> How do you propose to tell the difference between ssh and scp?
Read the HOWTO. Scp doesn't set the 'minimum delay' flag.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-12 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 7:50 [LARTC] SFQ Don Cohen
2001-12-12 9:31 ` bert hubert [this message]
2003-11-26 15:02 ` Martin Krejcirik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-100814954109331@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox