From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 69 working on Xen HVM
Date: Wed, 12 Jun 2013 10:37:35 +0200 [thread overview]
Message-ID: <1371026255.11840.108.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <assp.0875804c4c.51B7E0DD.300@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
I am not sure where you are going with this...
Reports that something works
A good place for that is the hardware section in the wiki. Although
virtual machines are not exactly hardware, I think it's a good place to
make list or table with working configurations.
Reports that something doesn't work
First make sure, that is really is a bug. Ask other people to make the
same steps you did.
If you can verify that something does not work as expected or is
misbehaving in some way, make a bug report.
Detailed information about that can be found here:
http://planet.ipfire.org/post/how-to-write-a-good-bug-report
-Michael
On Tue, 2013-06-11 at 21:45 -0500, R. W. Rodolico wrote:
> I'm not sure where to report this to, but I have Core 69 running on a
> Xen HVM, using Debian Wheezy, Xen 4.1 and the xl toolstack. It is doing
> a site-to-site vpn, some road warriors, and runs dhcp and NAT.
>
> This was an upgrade from Core 68.
>
> Please let me know where reports should be made in the future as I have
> a couple of other routers to upgrade.
>
> Rod
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2013-06-12 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 2:45 R. W. Rodolico
2013-06-12 8:37 ` Michael Tremer [this message]
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=1371026255.11840.108.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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