Skip to contentSkip to conversation

U32 Port Range

LARTC Thilo Schulz 1 participant 2 messages Oct 5, 2004 – Oct 6, 2004

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 1 line · On Tuesday 05 October 2004 13:06, [email protected] wrote:

- I know that is something about the 0xffff parameter....

I guess it is some kind of bitmask and works similarly to a netmask. If you only want to categorise traffic from port 1-1024, using "sport 0 0xfbff" *might* work, though I am not sure about that. Some core QoS developers on the kernel may give you more insight than I am able to do. But you can still try it, better than nothing :).

- --
Thilo Schulz

My public PGP key is available at http://home.bawue.de/~arny/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBYq6JZx4hBtWQhl4RAsKvAKDVX5mv6HurtkNCuTqt8RNZg1lUTQCeP5NS TF7X0Qhn7GkIXhnviZ2rQTw=L6y/
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

oops it's rather "sport 0 0xfc00" than "sport 0 0xfbff" if it worked the way I think it would.

- --
Thilo Schulz

My public PGP key is available at http://home.bawue.de/~arny/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBY9qtZx4hBtWQhl4RAtvCAJ41eu0Obnx0GjA6g1/krgQ+6ovXCACfZLVL S0c0r0rvd6zZJSuzjy0S2Kw=XmFZ
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/