xen configuration

xen configuration

[Stephen Mack]

[-- Attachment #1.1: Type: text/plain, Size: 808 bytes --]

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.

Warm regards!

--Stephen

[-- Attachment #1.2: Type: text/html, Size: 979 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: xen configuration

[Razvan Cojocaru]

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

Re: xen configuration

[Stephen Mack]

[-- Attachment #1.1: Type: text/plain, Size: 1374 bytes --]

Thank you Razvan.

On Wed, Oct 8, 2014 at 5:07 AM, Razvan Cojocaru <rcojocaru@bitdefender.com>
wrote:

> 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
>

[-- Attachment #1.2: Type: text/html, Size: 1952 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

xen configuration

[Johnson, Michael]

[-- Attachment #1.1: Type: text/plain, Size: 365 bytes --]

Could you point me to documentation on how to get the xen web interface
working?  The only documentation I've found says start xensv then open
up a browser.  I'm get an exception error "no such file or directory"
/var/lib/xen/sv.  True, it doesn't exist.  
 
Also, I'm looking for more detailed documentation on how to install a
guest O/S.
 
thanks,
Mike

[-- Attachment #1.2: Type: text/html, Size: 1128 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: xen configuration

[Tom Wilkie]

Right now, XenSV is in a state of flux, so this will probably all change 
soon...

You need to install apache and mod_python, copy the files from /tools/sv 
/ in the reopository to somewhere under you web root (typically 
/var/www/), and add the following lines to you apache config file:

LoadModule python_module modules/mod_python.so

AddHandler mod_python .psp
PythonHandler mod_python.psp

And optionally:

PythonDebug On

Then it should work if you point you browser at the index.psp page!  I 
did some work on it about a month ago, but my guess is it will need a 
little more to work smootly again.

Cheers

Tom


Johnson, Michael wrote:
> Could you point me to documentation on how to get the xen web interface 
> working?  The only documentation I've found says start xensv then open 
> up a browser.  I'm get an exception error "no such file or directory" 
> /var/lib/xen/sv.  True, it doesn't exist. 
>  
> Also, I'm looking for more detailed documentation on how to install a 
> guest O/S.
>  
> thanks,
> Mike
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel