i am not understanding why probe 2285 does not seem to even get an ipv6 address on the in-rack lan, while a whole lot of other devices do. and 2283 managed to get a v6 address but no gateway, and of course no v6dns. what do the little puppies want, nd ra ??? randy
i am not understanding why probe 2285 does not seem to even get an ipv6 address on the in-rack lan, while a whole lot of other devices do.
this mailing list *really* works! a few minutes after posting the above, the problem went away, the device got a global ipv6 addy after a couple of weeks without.
and 2283 managed to get a v6 address but no gateway, and of course no v6dns.
now both are the same, ip addy but claim to have no gateway. otoh, they seem to be globally ping6able. wth? IPv4 IPv6 Internet Address: 147.28.0.132 2001:418:1:0:220:4aff:fee0:246d Local Address: 147.28.0.132 2001:df9::220:4aff:fee0:246d/64 Gateway: 147.28.0.1 Undetermined/Unknown DNS Resolver: 147.28.0.35 Undetermined/Unknown AS Number: AS3130 AS3130 IPv4 IPv6 Internet Address: 210.138.216.50 2001:240:6a8:0:220:4aff:fee0:227c Local Address: 192.168.0.27 2001:240:6a8:0:220:4aff:fee0:227c/64 Gateway: 192.168.0.1 Undetermined/Unknown DNS Resolver: 192.168.0.1 Undetermined/Unknown AS Number: AS2497 AS2497 randy
On Mon, May 28, 2012 at 8:26 AM, Randy Bush <randy@psg.com> wrote:
now both are the same, ip addy but claim to have no gateway. otoh, they seem to be globally ping6able. wth? Same problem here. I switched to static configuration, but that doesn't help.
IPv4 IPv6 Internet Address: 193.160.39.7 Undetermined/Unknown Local Address: 193.160.39.7 2001:67c:26f4::7/64 Gateway: 193.160.39.1 Undetermined/Unknown DNS Resolver: 2001:67c:26f4:100::20, 193.160.39.20 Undetermined/Unknown AS Number: AS57821 Undetermined/Unknown The probe just ignores whatever I put in there for static IPv6, except the address. It isn't ping6-able even with a static address (of course, since it has no gateway to route the responds to). -- Dan Luedtke http://www.danrl.de
Sorry, engineers are off today. It's a public holiday over here. I am sure they will be back to you tomorrow at the latest. On 28.05.2012, at 09:28, Dan Luedtke wrote: Daniel
On Mon, May 28, 2012 at 8:26 AM, Randy Bush <randy@psg.com> wrote:
now both are the same, ip addy but claim to have no gateway. otoh, they seem to be globally ping6able. wth? Same problem here. I switched to static configuration, but that doesn't help.
IPv4 IPv6 Internet Address: 193.160.39.7 Undetermined/Unknown Local Address: 193.160.39.7 2001:67c:26f4::7/64 Gateway: 193.160.39.1 Undetermined/Unknown DNS Resolver: 2001:67c:26f4:100::20, 193.160.39.20 Undetermined/Unknown AS Number: AS57821 Undetermined/Unknown
The probe just ignores whatever I put in there for static IPv6, except the address. It isn't ping6-able even with a static address (of course, since it has no gateway to route the responds to).
-- Dan Luedtke http://www.danrl.de
On Mon, May 28, 2012 at 03:26:08PM +0900, Randy Bush wrote:
i am not understanding why probe 2285 does not seem to even get an ipv6 address on the in-rack lan, while a whole lot of other devices do.
this mailing list *really* works! a few minutes after posting the above, the problem went away, the device got a global ipv6 addy after a couple of weeks without.
and 2283 managed to get a v6 address but no gateway, and of course no v6dns.
now both are the same, ip addy but claim to have no gateway. otoh, they seem to be globally ping6able. wth?
IPv4 IPv6 Internet Address: 147.28.0.132 2001:418:1:0:220:4aff:fee0:246d Local Address: 147.28.0.132 2001:df9::220:4aff:fee0:246d/64 Gateway: 147.28.0.1 Undetermined/Unknown
V6 Gateway is not reported in the UI. However, in this case, the probe has it and reports it. Probe 2285, the gw start with fe80 and ends wiht 341c. At the moment the only way to add V6 resolver is add it statically; you can add just resolvers(add both v4 adn v6). Probe Settings Change Probe's Network Configuration. Change DNS servers.
DNS Resolver: 147.28.0.35 Undetermined/Unknown AS Number: AS3130 AS3130
IPv4 IPv6 Internet Address: 210.138.216.50 2001:240:6a8:0:220:4aff:fee0:227c Local Address: 192.168.0.27 2001:240:6a8:0:220:4aff:fee0:227c/64 Gateway: 192.168.0.1 Undetermined/Unknown
v6 gateway ends with b500.
DNS Resolver: 192.168.0.1 Undetermined/Unknown AS Number: AS2497 AS2497
regards, -antony
mornin' antony,
this mailing list *really* works! a few minutes after posting the above, the problem went away, the device got a global ipv6 addy after a couple of weeks without.
any idea about this magic?
and 2283 managed to get a v6 address but no gateway, and of course no v6dns. IPv4 IPv6 Internet Address: 147.28.0.132 2001:418:1:0:220:4aff:fee0:246d Local Address: 147.28.0.132 2001:df9::220:4aff:fee0:246d/64 Gateway: 147.28.0.1 Undetermined/Unknown
V6 Gateway is not reported in the UI.
any chance for a low priority cosmetic fix for this?
However, in this case, the probe has it and reports it. Probe 2285, the gw start with fe80 and ends with 341c.
i will avoid heresies about RA and link local :)
At the moment the only way to add V6 resolver is add it statically; you can add just resolvers(add both v4 adn v6). Probe Settings Change Probe's Network Configuration.
<doh> thanks! randy
Hi Randy, On Tue, May 29, 2012 at 05:59:54AM +0900, Randy Bush wrote:
this mailing list *really* works! a few minutes after posting the above, the problem went away, the device got a global ipv6 addy after a couple of weeks without.
any idea about this magic?
from what i gather the probe got first RA around epoch 1337782688, and reported around 2012-05-23 14:20:09 UTC. When the UI got updated, that is close to magic:) I can't explain!! However, if you look at "Show last 25 connections" you see an entry for 2012-05-27 16:38:58 UTC from a v6 address. that means, in the worst case, UI could have picked up V6 address change around that time. Also, after this reconnection it sent/received v6 measurements.
and 2283 managed to get a v6 address but no gateway, and of course no v6dns. IPv4 IPv6 Internet Address: 147.28.0.132 2001:418:1:0:220:4aff:fee0:246d Local Address: 147.28.0.132 2001:df9::220:4aff:fee0:246d/64 Gateway: 147.28.0.1 Undetermined/Unknown
V6 Gateway is not reported in the UI.
any chance for a low priority cosmetic fix for this?
One day we shoule improve the UI; no idea when. To do it right we have to show multiple addresses and gateways. The probe can have multiple V6 addresses. When it receives multiple RA(different prefixes) and static IPv6 address it ends up with multiple V6 gateways too. Then it is a bit messy to show. Just now you switched to static V6. Yes,there was some down time, but it is back now:) Now the fun begins, because the probe has two v6 address and two gateways, ::1 and the one it got via RA! regards, -antony
mornin'antony,
When the UI got updated, that is close to magic:) I can't explain!!
i demand a full refund!
One day we shoule improve the UI; no idea when. To do it right we have to show multiple addresses and gateways. The probe can have multiple V6 addresses. When it receives multiple RA(different prefixes) and static IPv6 address it ends up with multiple V6 gateways too. Then it is a bit messy to show.
i will refrain from heresies about RA and link local
Just now you switched to static V6. Yes,there was some down time, but it is back now:)
i was a bit amazed at the length of down time
Now the fun begins, because the probe has two v6 address and two gateways, ::1 and the one it got via RA!
maybe, when it is statically configured it should drop what it learned via RA? hard call, as RA is a poor geek's vrrp6. sigh. randy
participants (4)
-
Antony Antony -
Dan Luedtke -
Daniel Karrenberg -
Randy Bush