OK, good news (at least for me). I definitly solved my problems, and without obscure tweaks of the ATV2 (sysctl.conf removed and ATV2, wired again).
The problem lied on a TC parameter. I used (before also) the value "local" as the domain name for my network. This was to permit local name resolution on home network, without a local DNS server, using bonjour. With this setting it was possible to ping all my systems by name (server instead of server.local).
Removing this, all work fine again. I suspect there is an obscure conflict with the zeroconf capabilities of the newer nightlies, not a problem with the new gen TC itself (I did not watch those HD movies since a long time, but I used them to "burn" the new configuration, and came to bad assumptions).
Errata - nothing to do with "local" domain - maybe one day I will learn not to make more than one change at a time...
In fact the problem seems to be solved by forcing the WAN port mode. Maybe a bug in speed negociation with my modem. Did not have this before.
For those interested the TCP configuration is (more or less good translation since the TC is in french) :
- Connection via ethernet to a cable modem (WAN
forced 100M full duplex)
- Share a public IP address
- Configuration via DHCP, DNS, domain name
set to "local" and DHCP client id not set (empty)
- 10.0.x LAN
- PMP-NAT activated (need to check what it is exactly someday)
Will get back to DHCP reservation and hosts editing for name resolution
.
Regards,