From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Stephen Mack <smack815@gmail.com>, xen-devel@lists.xen.org
Subject: Re: xen configuration
Date: Wed, 08 Oct 2014 11:07:43 +0300 [thread overview]
Message-ID: <5434F0CF.4090903@bitdefender.com> (raw)
In-Reply-To: <CA+kMmLBsr2r33XCBef3pC9H375U4gRJzPyjiQ3sa8pcoOKieNQ@mail.gmail.com>
On 10/08/2014 02:23 AM, Stephen Mack wrote:
> Greetings,
>
> I have somewhat of a simple question about xen configuration possibilities.
>
> I would like to know if it is possible to restrict the ports from which
> a xen domain can receive traffic and have all other attempts sent to
> another domain to be processed.
>
> Say for example I have a web server deployed that I only want to accept
> traffic on port 80 and so it should never receive a request for
> ftp/ssh/dns/etc. However if such a request ever were to come in for my
> web server, I want that traffic to be sent to my honeypot for
> processing, logging and possible remediation.
>
> I must say that I am very new to xen and have not read any
> documentation. I am only looking for feedback if this is
> possible/feasible and if there are any negative implications of such a
> configuration.
Hello Stephen,
I'm not an expert on the subject, but Xen simply uses a bridge (xenbr0)
in dom0, so you can either use that or simply configure the firewall
directly in your guest, just as you would with any regular machine.
You should be able to find more details here:
http://wiki.xen.org/wiki/XenNetworking
Hope this helps,
Razvan Cojocaru
next prev parent reply other threads:[~2014-10-08 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 23:23 xen configuration Stephen Mack
2014-10-08 8:07 ` Razvan Cojocaru [this message]
2014-10-08 13:19 ` Stephen Mack
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 15:58 Johnson, Michael
2005-09-09 9:05 ` Tom Wilkie
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=5434F0CF.4090903@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=smack815@gmail.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.