Re: IPv6 config... grmpf!

On Sat, 11 Aug 2012, Michelle Konzack wrote:
> Am 2012-08-11 16:41:16, hacktest Du folgendes herunter:
>> You could try a traceroute6 from your server to ipv6.google.com or
>> you could use Hurricane Electric's Looking Glass at
>> http://lg.he.net/ to do a traceroute from one of their routers to
>> your server.
> My first Server <mail.tamay-dogan.net> seems to work now with IPv6
> properly.  Unfortunately, the second Server <dns1.tamay-dogan.net>
> currently not.  I hope I can resolv this problem this weekend.

What does ifconfig eth0 have to say about it?

> However, while I use for the Server the IPv6 from
>    <2a01:4f8:d12:1300:::0:0> to <2a01:4f8:d12:1300:::0:ffff>
> I have configured my <intranet1.tamay-dogan.net> subnet to use
>    <2a01:4f8:d12:1300:::1:0> to <2a01:4f8:d12:1300:::1:ffff>
> but I can not establish connections between my my workstations and
> servers:
>
> --[ '/etc/bind/masters/net/tamay-dogan/net.tanmay-dogan.intranet1' ]--
> @		3600	IN SOA		dns1.tamay-dogan.net.	hostmaster.tamay-dogan.net. ( 1344640689 14400 3600 604800 86400 )

# dig @dns1.tamay-dogan.net +short -t soa intranet1.tamay-dogan.net
dns1.tamay-dogan.net. hostmaster.tamay-dogan.net. 1342711104 14400 3600 604800 86400

An older serial... Have you asked bind to reload the zone?

> router.intranet1.tamay-dogan.net.		IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0001

This and the other AAAA records seems fine, but asking your DNS about that 
AAAA-record doesn't return anything. I don't know if you're using views or 
if it's because you haven't reloaded the new zone file.

> Is there something missing?

Maybe a /etc/init.d/bind9 reload

Anyway... I would make sure IPv6 works before adding AAAA-records. It 
seems like you're trying to do both at once and that's what making it 
harder to troubleshoot the problem.

I.e. make sure a traceroute6 to 2a01:04f8:0d12:1300::1:1 works before you 
try to get a traceroute6 to router.intranet1.tamay-dogan.net working.

> On my Workstation it looks like:
>
> --[ '/etc/network/interfaces' ]-----------------------------------------
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
>        address 192.168.0.13
>        netmask 255.255.255.0
>        network 192.168.0.0
>        broadcast 192.168.0.255
>        gateway 192.168.0.1
>        dns-nameservers 192.168.0.11
>        dns-search intranet1.tamay-dogan.net
>
> iface eth0 inet6 static
>  address   2a01:04f8:0d12:1300:0000:0000:0001:0013
>  netmask   64
>  gateway   2a01:04f8:0d12:1300:0000:0000:0000:0001

Seems ok so far.

>        dns-nameservers 2a01:04f8:0d12:1300:0000:0000:0001:0011
>        dns-search intranet1.tamay-dogan.net
>        up   ip -6 route add         2a01:04f8:0d12:1300:0000:0000:0000:0001 dev eth0
>        down ip -6 route del         2a01:04f8:0d12:1300:0000:0000:0000:0001 dev eth0
>        up   ip -6 route add default 2a01:04f8:0d12:1300:0000:0000:0000:0001 dev eth0
>        down ip -6 route del default 2a01:04f8:0d12:1300:0000:0000:0000:0001 dev eth0

I don't use those extra lines in my /etc/network/interfaces. The route 
commands shouldn't be necessary as you already have a gateway line for 
eth0.

> Same on the <dns1>, <samba> and <cups> server  and  <work2>  workstation
> and of course, with there own rigth IPs.

Can you show us the output of ifconfig?

> If I get my local network running with IPv6, I will  continue  to  setup
> the VPN between the <mail> server which then will be act  like  an  IPv6
> Broker and as Gateway...

I haven't dealt with VPNs before, so I can't help you with that.

> I have some problems with "nmap" and IPv6.  Do I need special options to
> check an IPv6?

Besides -6? I don't think so.

# nmap -6 2a01:04f8:0d12:1300:0000:0000:0000:0002

works for me (22, 25, 80, 143, 443, 465, 587 and 993 open).

What problems are you having? Any error messages?

-- 
Povl Ole