On 06/08/2011 11:27 PM, Alexander Boström wrote:
I've never used the v6 support in libvirt, so I'm guessing here, but
wlan0 is the physical interface on the host that you're running radvd
on, right? That would pick up router advertisements from the router in
your wireless LAN, if you have
DIVERT and SOCKET are not usable for TPROXY4 stuff in Squid due to what
bug https://bugzilla.redhat.com/show_bug.cgi?id=662399 calls a user
space problem.
libvirtd VMs cannot have outside accessible IPv6 addresses
autoconfigured. I mentioned the problem, at least as far as I was able
to find it
On 08/06/11 16:20, Trever L. Adams wrote:
libvirtd VMs cannot have outside accessible IPv6 addresses
autoconfigured. I mentioned the problem, at least as far as I was able
to find it at https://bugzilla.redhat.com/show_bug.cgi?id=514749
Works fine for my VMs with bridged networking - they see
On 06/08/2011 09:32 AM, Tom Hughes wrote:
Works fine for my VMs with bridged networking - they see the radvd on
the network and configure an address.
Tom
Would you care to share some documentation of some kind?
network
nameTheCommons/name
uuid/uuid
forward mode='route'/
bridge
On Wed, Jun 08, 2011 at 09:42:22AM -0600, Trever L. Adams wrote:
On 06/08/2011 09:32 AM, Tom Hughes wrote:
Works fine for my VMs with bridged networking - they see the radvd on
the network and configure an address.
Tom
Would you care to share some documentation of some kind?
On 08/06/11 16:42, Trever L. Adams wrote:
Would you care to share some documentation of some kind?
network
nameTheCommons/name
uuid/uuid
forward mode='route'/
bridge name='virbr0' stp='off' delay='0' /
ip address='10.0.1.1' netmask='255.255.255.0'
/ip
ip
On Wed, Jun 08, 2011 at 04:53:51PM +0100, Tom Hughes wrote:
Ah that's a virtual bridge between your VMs. I'm bridging my VMs to br0
which is a bridge that includes the host's ethernet interface so that
the guests have direct access to the local LAN and can see the radvd
that is running on
On 06/08/2011 09:53 AM, Tom Hughes wrote:
Ah that's a virtual bridge between your VMs. I'm bridging my VMs to
br0 which is a bridge that includes the host's ethernet interface so
that the guests have direct access to the local LAN and can see the
radvd that is running on our gateway router.
On 06/08/2011 09:52 AM, Daniel P. Berrange wrote:
On Wed, Jun 08, 2011 at 09:42:22AM -0600, Trever L. Adams wrote:
Would you care to share some documentation of some kind?
network
nameTheCommons/name
uuid/uuid
forward mode='route'/
bridge name='virbr0' stp='off' delay='0' /
In a previous message I had this quote:
But these [serious NT security flaws] are not inherent flaws in the
operating system -- they don't happen by accident. They are the result
of deliberate and well-thought-out efforts. -- Mike Nash, Microsoft.
The _flaws_ are deliberate?
Someone kindly
On 06/08/2011 03:07 PM, Trever L. Adams wrote:
So, even though I restart wlan0 from rc.local, I get this:
Jun 8 14:56:00 HC kernel: [ 14.219624] ADDRCONF(NETDEV_UP): wlan0:
link is not ready
Does anyone know what would cause this? It takes the IPv4 address fine.
Again, the ifdown/ifup in
ons 2011-06-08 klockan 15:07 -0600 skrev Trever L. Adams:
After restarting from rc.local wlan0 has fe80, but not 2001 address
assigned.
I've never used the v6 support in libvirt, so I'm guessing here, but
wlan0 is the physical interface on the host that you're running radvd
on, right? That
12 matches
Mail list logo
