[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: IPv6 config... grmpf!



Hello Povl Ole Haarlev Olsen,

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.

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 )

					NS	dns1.tamay-dogan.net.
					NS	dns2.tamay-dogan.net.
					NS	dns3.tamay-dogan.net.
					NS	dns.intranet1.tamay-dogan.net.

					MX 10	samba.intranet1.tamay-dogan.net.

intranet1.tamay-dogan.net.		TXT	"v=spf1 a mx ~all"

www.intranet1.tamay-dogan.net.		IN CNAME	vserver09.tamay-dogan.net.

router.intranet1.tamay-dogan.net.		IN A	192.168.0.1
router.intranet1.tamay-dogan.net.		IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0001
easybox-o2.intranet1.tamay-dogan.net.		IN A	192.168.0.2
easybox-ortel.intranet1.tamay-dogan.net.	IN A	192.168.0.3
easybox-bouygues.intranet1.tamay-dogan.net.	IN A	192.168.0.4

dns.intranet1.tamay-dogan.net.		IN A	192.168.0.11
dns.intranet1.tamay-dogan.net.		IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0011
samba.intranet1.tamay-dogan.net.	IN A	192.168.0.12
samba.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0012
work1.intranet1.tamay-dogan.net.	IN A	192.168.0.13
work1.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0013
backup.intranet1.tamay-dogan.net.	IN A	192.168.0.14
backup.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0014
admin.intranet1.tamay-dogan.net.	IN A	192.168.0.15
admin.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0015
asterisk.intranet1.tamay-dogan.net.	IN A	192.168.0.16
asterisk.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0016
pgsql.intranet1.tamay-dogan.net.	IN A	192.168.0.18
pgsql.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0018
work2.intranet1.tamay-dogan.net.	IN A	192.168.0.19
work2.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0019

onlinestore.intranet1.tamay-dogan.net.	IN A	192.168.0.20
onlinestore.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0020

cups.intranet1.tamay-dogan.net.		IN A	192.168.0.50
cups.intranet1.tamay-dogan.net.		IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0050
fs3700.intranet1.tamay-dogan.net.	IN A	192.168.0.51
fs3700.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0051
fs1030d.intranet1.tamay-dogan.net.	IN A	192.168.0.52
fs1030d.intranet1.tamay-dogan.net.	IN AAAA	2a01:04f8:0d12:1300:0000:0000:0001:0052

$include /etc/bind/master/net/tamay-dogan/Kintranet1.tamay-dogan.net.+005+55290.key
$include /etc/bind/master/net/tamay-dogan/Kintranet1.tamay-dogan.net.+005+40822.key
------------------------------------------------------------------------

Is there something missing?

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
        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
------------------------------------------------------------------------

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

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...

> Unfortunately that looking glass service doesn't provide a way to
> test if a port on your server is open or not, but the ping and
> traceroute tests are a good starting point.
> 
> If anyone knows a good looking glass service with a port test, I
> would like to know. Thanks in advance...

You are not alone.

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

Thanks, Greetings and nice Day/Evening
    Michelle Konzack

-- 
##################### Debian GNU/Linux Consultant ######################
   Development of Intranet and Embedded Systems with Debian GNU/Linux
               Internet Service Provider, Cloud Computing
                <http://www.itsystems.tamay-dogan.net/>
                  <http://www.debian.tamay-dogan.net/>

itsystems@tdnet                     Jabber  linux4michelle@jabber.ccc.de
Owner Michelle Konzack

Gewerbe Strasse 3                   Tel office: +49-176-86004575
77694 Kehl                          Tel mobil:  +49-177-9351947
Germany                             Tel mobil:  +33-6-61925193  (France)

USt-ID:  DE 278 049 239

Linux-User #280138 with the Linux Counter, http://counter.li.org/

Attachment: signature.pgp
Description: Digital signature


Reply to: