Displaying 3 results from an estimated 3 matches for "fe0d".
Did you mean:
fe00
2020 Apr 30
2
Diagnosing IPv6 routing
...ms
8 2600:3c01:3333:4::2 (2600:3c01:3333:4::2) 7.294 ms 7.728 ms 7.705 ms
9 * * *
>From Linode to AT&T:
[root at linode2 ~]# traceroute6 2001:1890:1837:5b01::100
traceroute to 2001:1890:1837:5b01::100 (2001:1890:1837:5b01::100), 30 hops
max, 80 byte packets
1 2600:3c01::8678:acff:fe0d:79c1 (2600:3c01::8678:acff:fe0d:79c1) 0.783
ms 2600:3c01::8678:acff:fe0d:a641 (2600:3c01::8678:acff:fe0d:a641) 0.834
ms 0.972 ms
2 2600:3c01:3333:4::1 (2600:3c01:3333:4::1) 0.645 ms 0.646 ms
2600:3c01:3333:2::1 (2600:3c01:3333:2::1) 0.508 ms
3 ix-ae-67-0.tcore1.sqn-san-jose.ipv6.as6453...
2020 Apr 28
3
Diagnosing IPv6 routing
On 4/28/2020 3:17 PM, Chris Adams wrote:
> - gateway sends a router solicitation and gets a router advertisement
> with "stateful config" set, which tells gateway to do DHCPv6 (but
> default route comes from RA)
I'm not seeing any outbound IPv6 traffic from my CentOS 7 box on the WAN
interface. I do see RA's emitting from the LAN interface, from radvd. Is
there
2012 May 23
4
Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
Package: xcp-xapi
Version: 1.3.2-6
Severity: normal
Tags: upstream
vbd plug to PV domain cause following error:
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760))
(same error