Hi Milosz,
I had the same problem yesterday. Direct protocol did not learn routes
either with implicit or explicit multichannel configuration. After
splitting it in 2 protocols, it worked for me. Maybe that's a feasible
workaround for you, too.
protocol direct direct4 {
ipv4;
interface "*";
}
Hi All,
We are purposing L3 IXP design to one of our customer as below, where all
ISP routers will have one eBGP peering with Quagga/Bird Route-Server. As
we are new in IXPs design so would like to take your suggestions if you
have and we have some queries below. Please respond, It would be helpf
Hi
In bird 2.0 protocol direct works correctly?
New config:
protocol direct {
ipv4;
ipv6;
interface "*";
}
And it doesn't announced any local prefix to upstream peers, only to
ibgp peer.
--
inż. Miłosz Oller
smime.p7s
Description: Kryptograficzna sygnatura S/MIME
Hi,
I don’t know if it helps, but here is the netlink options compiled in my
kernel:
regis linux # grep -i netlink /usr/src/linux/.config
CONFIG_NETFILTER_NETLINK=y
# CONFIG_NETFILTER_NETLINK_ACCT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CT_N
Hello,
It's a still opened vmtoolsd bug:
https://github.com/vmware/open-vm-tools/issues/186
setting
[guestinfo]
poll-interval=900
will move the cpu spike only on 900seconds intervals.
Giuseppe
On 12/20/2017 01:25 PM, Andrea Verni wrote:
> Hi guys,
>
>
>
> I noticed that the VM where I have
