From: Fabio Fantoni <fantonifabio@tiscali.it>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Question about antispoofing and sys-flood protection on xen bridges
Date: Tue, 09 Oct 2012 10:09:14 +0200 [thread overview]
Message-ID: <5073DBAA.8010509@tiscali.it> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 328 bytes --]
I'm in doubt about antispoofing and sys-flood protection on dom0 and
their effect on xen bridges.
If I add these parameters on /etc/sysctl.conf:
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.tcp_syncookies=1
Can they give problem on xen bridges and/or its performance?
Thanks for any reply
[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-10-09 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 8:09 Fabio Fantoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-05 13:41 Question about antispoofing and sys-flood protection on xen bridges Fabio Fantoni
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=5073DBAA.8010509@tiscali.it \
--to=fantonifabio@tiscali.it \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).