Ho un problema che mi affligge: sto cercando di attivare sul CISCO877-K9 di casa mia servizio di DDNS ma, ahimè!, non ci riesco...
Cercherò di essere sintetico, ho una reputazione famigerata tra i miei colleghi...
Cominciamo con la configurazione del router:
___________________________________________________________
PHOBOSL3#sh running-config
Building configuration...
Current configuration : 5345 bytes
!
! Last configuration change at 07:38:28 UTC Wed Oct 19 2011
!
version 12.4
service nagle
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
service sequence-numbers
!
hostname PHOBOSL3
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$U4zo$8F**************teOxy1
enable password 7 10425D0A**********B213828
!
!
no aaa new-model
!
!
dot11 syslog
ip cef
!
!
ip dhcp use vrf connected
ip dhcp excluded-address 192.168.0.254
ip dhcp excluded-address 192.168.0.1
ip dhcp excluded-address 192.168.0.253
ip dhcp excluded-address 192.168.2.254
ip dhcp excluded-address 192.168.2.1
ip dhcp excluded-address 192.168.2.2
ip dhcp excluded-address 192.168.2.3
ip dhcp excluded-address 192.168.2.4
ip dhcp excluded-address 192.168.2.5
ip dhcp excluded-address 192.168.2.6
!
!
ip dhcp pool PHOBOS_DHCP_NET0
import all
network 192.168.0.0 255.255.255.0
update dns both
domain-name phobos
dns-server 192.168.0.254 208.67.222.222 208.67.220.220 193.70.152.15 193.70.152.25
default-router 192.168.0.254
lease 0 2
!
!
ip dhcp update dns both
no ip bootp server
ip host-list PHOBOSNET
host 192.168.0.254 PHOBOSL3.dydns-at-home.com
ip name-server 193.70.152.15
ip name-server 193.70.152.25
ip name-server 208.67.222.222
ip name-server 208.67.222.220
ip ddns update method PHOBOSDDNS
HTTP
add http://phobos6***1:laser_***61@members. ... h>&myip=<a>
interval maximum 0 23 0 0
!
!
ip dhcp-client update dns server both
!
multilink bundle-name authenticated
vpdn enable
!
vpdn-group 1
request-dialin
protocol pppoe
!
!
!
username phobos privilege 15 password 7 0703205F4******************7B***
!
!
archive
log config
hidekeys
!
!
ip tcp selective-ack
ip tcp synwait-time 10
!
bridge irb
!
!
!
interface ATM0
mtu 1492
bandwidth 6144
bandwidth receive 1024
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
no atm ilmi-keepalive
bundle-enable
dsl operating-mode adsl2+
hold-queue 224 in
!
interface ATM0.1 point-to-point
description $ES_WAN$
bandwidth 6144
bandwidth receive 1024
no ip redirects
no ip unreachables
no ip proxy-arp
logging event subif-link-status
pvc 8/35
encapsulation aal5snap
pppoe-client dial-pool-number 1
!
!
interface FastEthernet0
description >PHOBOS-VLAN1<-Server/Link
shutdown
!
interface FastEthernet1
description >PHOBOS-LAN2<
switchport access vlan 2
spanning-tree portfast
!
interface FastEthernet2
shutdown
!
interface FastEthernet3
description >PHOBOS-TRUNK<
switchport mode trunk
!
!
interface Vlan1
description >NATIVE-LAN<
ip address 192.168.0.254 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!
interface Vlan2
description >MEDIA-LAN<
ip address 192.168.1.254 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!
interface Vlan3
description >PHOBOS-LAN<
ip address 192.168.2.254 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!
interface Vlan16
description >HDD-CONFIGURING<
ip address 192.168.16.254 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!
!
interface Dialer0
bandwidth 6144
bandwidth receive 1024
ip dhcp client update dns server both
ip ddns update hostname phobosL3.dydns-at-home.com
ip ddns update PHOBOSDDNS
ip address negotiated
ip verify unicast reverse-path
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip tcp adjust-mss 1452
no ip mroute-cache
dialer pool 1
dialer-group 1
ppp authentication chap callin
ppp chap hostname benvenuto
ppp chap password 7 082E5F5E000D00
ppp pap sent-username benvenuto password 7 10411A090C0317
!
!
no ip classless
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
!
!
ip http server
ip http authentication local
no ip http secure-server
ip nat inside source list 100 interface Dialer0 overload
ip nat inside source static udp 192.168.0.254 14317 interface Dialer0 14317
ip nat inside source static tcp 192.168.0.254 14317 interface Dialer0 14317
ip nat inside source static udp 192.168.0.254 41238 interface Dialer0 41238
ip nat inside source static tcp 192.168.0.254 41238 interface Dialer0 41238
!
logging trap debugging
access-list 100 remark PHOBOS_ACL
access-list 100 permit ip 192.168.0.0 0.0.255.255 any
dialer-list 1 protocol ip permit
snmp-server group operator v3 auth read PHOBOSSNMv3
snmp-server community PHOBOSSNMP RW
snmp-server trap-source Vlan3
snmp-server location Stanza_Studio
!
!
!
!
control-plane
!
!
line con 0
timeout login response 150
password 7 1309****************13A30
login
no modem enable
line aux 0
password 7 121****************E6564
login
line vty 0 4
timeout login response 150
password 7 141*****************136
login
!
scheduler max-task-time 5000
scheduler allocate 4000 1000
scheduler interval 500
sntp server 193.204.114.232
sntp server 193.204.114.233
end
___________________________________________________________
Passo ora ad elencare cosa ho fatto:
1) Sono andato su http://www.dyndns.com ed ho aperto un'utenza
2) Ho modificato la configurazione del mio router come vedete sopra; le cose più significative (almeno secondo me) sono
(-)ip host-list PHOBOSNET
host 192.168.0.254 PHOBOSL3.dydns-at-home.com
ip name-server 193.70.152.15
ip name-server 193.70.152.25
ip name-server 208.67.222.222
ip name-server 208.67.222.220
ip ddns update method PHOBOSDDNS
HTTP
add
http://phobos6***1:laser_***61@members. ... =dyndns&ho
stname=<h>&myip=<a>
interval maximum 0 23 0 0
(.) interface Dialer0
...
ip dhcp client update dns server both
ip ddns update hostname phobosL3.dydns-at-home.com
ip ddns update PHOBOSDDNS
3) Per essere sicuro che l'interfaccia dialer0 autenticasse
correttamente ho quindi fatto questi passi:
-conf t
-int dia0
-shut
-exit (euscita dal configuration terminal)
-term mon (abilitazione del terminal monitor)
-debug ip ddns update (abilitazione del trace di debug per il ddns)
-conf t
-int dia0
-no shut (riabiliti la dialer0)
Questo è l'output della dialer0 dopo il no shut:
___________________________________________________________________________________________________
000057: Oct 18 21:49:42.116 UTC: %LINK-3-UPDOWN: Interface Virtual-Access1,changed state to down
000058: Oct 18 21:49:42.116 UTC: DYNUPD: SWIF goingdown 'Virtual-Access1'
000059: Oct 18 21:49:43.100 UTC: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Virtual-Access1, changed state to down
000060: Oct 18 21:49:44.100 UTC: %LINK-3-UPDOWN: Interface Dialer0, changed state to up
000061: Oct 18 21:49:44.100 UTC: DYNUPD: SWIF comingup 'Dialer0'
000062: Oct 18 21:50:04.227 UTC: %DIALER-6-BIND: Interface Vi1 bound to profile Di0
000063: Oct 18 21:50:04.231 UTC: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
000064: Oct 18 21:50:07.275 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up
000065: Oct 18 21:50:07.275 UTC: DYNUPD: SWIF comingup 'Virtual-Access1'Translating "members.dyndns.org"...domain server (193.70.152.15) [OK]
000066: Oct 18 21:50:09.595 UTC: DYNDNSUPD: Adding DNS mapping for phobosL3.dydns-at-home.com <=> 151.16.87.192
000067: Oct 18 21:50:09.595 UTC: HTTPDNS: Update add called for phobosL3.dydns-at-home.com <=> 151.16.87.192
000068: Oct 18 21:50:09.595 UTC: HTTPDNSUPD: Session ID = 0x4
000069: Oct 18 21:50:09.595 UTC: HTTPDNSUPD: URL ='http://phob******1:l***r_*****1@members ... .16.86.152'
000070: Oct 18 21:50:09.595 UTC: HTTPDNSUPD: Sending request
000071: Oct 18 21:50:09.879 UTC: HTTPDNSUPD: Response for update phobosL3.dydns-at-home.com <=> 151.16.87.192
000072: Oct 18 21:50:09.879 UTC: HTTPDNSUPD: DATA START404
000073: Oct 18 21:50:09.879 UTC: HTTPDNSUPD: DATA END, Status is Response data recieved, successfully
000074: Oct 18 21:50:09.883 UTC: HTTPDNSUPD: [u]Call returned SUCCESS for update phobosL3.dydns-at-home.com <=> 151.16.87.192[/u]000075: Oct 18 21:50:09.883 UTC: DYNDNSUPD: Another update completed (outstanding=0, total=0)
000076: Oct 18 21:50:09.883 UTC: HTTPDNSUPD: Clearing all session 4 info
___________________________________________________________________________________________________
Guardiamo se...
__________________________
PHOBOSL3#sh ip interface dialer 0
Dialer0 is up, line protocol is up
Internet address is 151.16.87.192/32
Broadcast address is 255.255.255.255
__________________________
Sembra tutto ok, vero ?
Ma manco per niente: guardate un po' qua:
__________________________
C:\Windows\system32>ping phobosL3.dydns-at-home.com
Esecuzione di Ping phobosL3.dydns-at-home.com [67.215.65.132] con 32 byte di dati:
Risposta da 67.215.65.132: byte=32 durata=44ms TTL=55
Risposta da 67.215.65.132: byte=32 durata=44ms TTL=55
Risposta da 67.215.65.132: byte=32 durata=45ms TTL=55
Risposta da 67.215.65.132: byte=32 durata=45ms TTL=5
67.215.65.132 e chi è questo ? Ancora sta su dyndns.com... ecco chi è...
__________________________
Ovvio che non va; 67.215.65.132 non è 151.16.87.192... ed anche al traceroute si punta fuori, come si vede da qui:
__________________________
C:\Windows\system32>tracert phobosL3.dydns-at-home.com
Traccia instradamento verso phobosL3.dydns-at-home.com [67.215.65.132] su un massimo di 30 punti di passaggio:
1 1 ms 1 ms <1 ms 192.168.2.254 #my router#
2 12 ms 17 ms 25 ms 151.23.224.69
3 12 ms 13 ms 25 ms 10.0.31.1
4 11 ms 12 ms 25 ms 151.6.252.65
.... Non è necessario arrivare fino in fondo, ormai sono uscito nel mondo e dovevo arrivarci in un hop soltanto... ^C
__________________________
Per farlo funzionare bisogna essere a casa mia ed andare sulla pagina di http://www.dyndns.com ed aggiornare a mano l'ip sulla pagina dell'elenco degli host...
Ecco, l'essenza del problema è tutta qui...
Bisogna essere a casa mia (poiché l'ip pubblico dinamico deve essere individuato sulla portante DSL riferita alla mia interfaccia dialer0 ), andare sulla pagina e salvare, poi funziona.
Non dovrebbe essere il mio router a passare il mio ip pubblico a DYNDNS, ogni volta che viene acceso ?
E non io a farlo a mano... ma, come avete visto dal shut/no shut della dialer0 che ho postato sopra sembra che lo faccia ...
Call returned SUCCESS for update phobosL3.dydns-at-home.com <=>151.16.87.192, ricordate ?
Guardiamo come funziona dopo aver salvato sulla pagina web:
__________________________
C:\Windows\system32>ping phobosl3.dyndns-at-home.com
Esecuzione di Ping phobosl3.dyndns-at-home.com [151.16.87.192] con 32 byte di dati:
Risposta da 151.16.87.192: byte=32 durata=1ms TTL=255
Risposta da 151.16.87.192: byte=32 durata=1ms TTL=255
Risposta da 151.16.87.192: byte=32 durata=1ms TTL=255
Risposta da 151.16.87.192: byte=32 durata=1ms TTL=255
__________________________
Adesso guardiamo il traceroute:
__________________________
C:\Windows\system32>tracert phobosl3.dyndns-at-home.com
Traccia instradamento verso phobosl3.dyndns-at-home.com [151.16.87.192] su un massimo di 30 punti di passaggio:
1 2 ms 1 ms <1 ms 151.16.87.192
Traccia completata.
__________________________
Ci voleva tanto ?
Quindi, ripeto, solo dopo che ho salvato nuovamente sul portale web, e l'ip pubblico dinamico corrisponde a quello del mio router sembra funzionare...
Non riesco proprio a capire dove sta l'errore; spero che qualcuno dei destinatari riesca ad individuare l'errore che io non vedo; ci sto venendo matto...
Vi ringrazio anticipatamente!
