From owner-freebsd-xen@FreeBSD.ORG Fri Oct 10 10:54:31 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E651F7CB for ; Fri, 10 Oct 2014 10:54:31 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0017F5 for ; Fri, 10 Oct 2014 10:54:31 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s9AAo7eG088994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Oct 2014 11:50:08 +0100 (BST) Date: Fri, 10 Oct 2014 11:50:06 +0100 From: Karl Pielorz To: Marko Lerota , FreeBSD XEN Subject: Re: Routing/NAT problem on Xenserver 6.2 with virtual firewall Message-ID: <971643C23A6DD25E72F11864@Mail-PC.tdx.co.uk> In-Reply-To: <86fvfxove9.fsf@arch.perpetuum.hr> References: <86k359p1qm.fsf@arch.perpetuum.hr> <9864A2A7BE97EB706ED0FC04@Mail-PC.tdx.co.uk> <86fvfxove9.fsf@arch.perpetuum.hr> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2014 10:54:32 -0000 --On 12 September 2014 14:50 +0200 Marko Lerota wrote: > Thanks Karl. It may be something that is 'easy' to fix. ICMP traffic > already goes through. So why not just add TCP/UDP in the code :-) > It would be a shame that I have to use Iptables again. Any of the > free DEVs are listening? I'm buying a beer :-). Replying late as I've just walked into this issue, yet again - which prompts me to ask: - Is there any way of having the FreeBSD virtual machine use the Xen disk services, but the legacy 'realtek' network card? I had asked about this a while ago - I think someone said it would be 'very tricky' - and much later someone replied that it might be possible... That would hopefully give us some agility back to these machines - which at the moment are languishing on a separate pool - running pure HVM, which is a real pain for backend storage changes / upgrades :( Maybe it's time for beer++? :) -Karl