cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <daan.hoogl...@gmail.com>
Subject Re: firewall problems and proxy problems
Date Thu, 16 Oct 2014 13:36:16 GMT
Marc,

The only difference I see is de vice cloudbr0 becoming cloud0, in the third
line. Am I correct?

On Thu, Oct 16, 2014 at 3:28 PM, Marc Leeman <marc.leeman@gmail.com> wrote:

> ‚Äč
> OK, there is something off here:
>
> This is my routing table where I can ping another physical host with an
> link-local address
>
> route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 0.0.0.0         10.158.231.1   0.0.0.0         UG    0      0        0 eth1
> 10.158.231.0   0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
> cloudbr0
> 172.16.0.0      0.0.0.0         255.255.0.0     U     0      0        0
> cloudbr0
> 172.16.8.0      0.0.0.0         255.255.255.0   U     0      0        0
> cloudbr0
>
>
> If I restart the cloudstack-agent; the routing table has changed to:
>
> route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 0.0.0.0         10.158.231.1   0.0.0.0         UG    0      0        0 eth1
> 10.158.231.0   0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
> cloud0
> 172.16.0.0      0.0.0.0         255.255.0.0     U     0      0        0
> cloudbr0
> 172.16.8.0      0.0.0.0         255.255.255.0   U     0      0        0
> cloudbr0
>
> and link-local devices cannot be accessed.
>
> In both cases, I cannot access the system VMs with ssh.
>



-- 
Daan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message