07-16-2025 03:44 AM
Hello everyone,
I'm currently taking a course on OpenClassrooms:
https://openclassrooms.com/fr/courses/7192261-simulez-le-schema-de-votre-reseau-avec-cisco-packet-tracer/7444299-realisez-le-routage-inter-vlan
I've followed the course right up to the stage where I have to ping the various end devices.
This is where things get complicated: all the PC1s can communicate with each other, the entire VPN remote site, the entire Wifi network and the Servers, but it is impossible to ping the PC2s and Printers. (This is not a problem with IPv4).
I noticed that the PC2s couldn't communicate with their Ipv6 gateway. For printers, it is possible to ping the gateway, but not to go any further.
There are several VLANs: 20 Management, 21 Exams/Competitions, 22 Payroll/HRD, 23 Employment, 24 Medicine, 25 Insurance, 27 Info/RGPD, 30 Server, 40 Printing, 50 Telephony, 60 Wifi and 100 Administration.
Please note that a password is required for most switches and routers.
Here is the password: 1234-MetroPole:1234.
Here's the configuration in a nutshell:
1. 2960 :
- End device interfaces: access mode with voice vlan 50, access vlan x (depending on the network), mls qos trust cos
- Interface to 3650: switchport trunk mode, native trunk 100 and trunk allowed x,x,40,50,100.
- Configuration and security for SSH connection.
2. 3650 :
- ipv6 unicast-routing ;
- Interfaces linked to the 2960: switchport mode trunk, trunk native 100 and trunk allowed x,x,40,50,100.
- Interfaces linked to Servers: switchport mode access, access vlan 30
- Interfaces linked to Wifi: switchport mode access, access vlan 60
- Interfaces VLAN x, description SVI Gateway x, ip address 192.168.x.254 255.255.255.0, ipv6 address 2001:db8:acad:x::254/64.
- Interface with RouterCG: no switchport, ip address 192.168.10.2 255.255.255.0, ipv6 address 2001:DB8:ACAD:10::2/64
- ip routing, ip route 0.0.0.0 0.0.0.0 192.168.10.1
- ipv6 route ::/0 2001:db8:acad:10::1
3. RouteurCG
- ipv6 unicast-routing
- Interface with 3650: ip address 192.168.10.1 255.255.255.0, ipv6 address 2001:DB8:ACAD:10::1/64, no shutdown
- Interface with RouteurVPN (Serial): description Lien RouteurCG-RouteurVPN, ip address 10.0.0.1 255.255.255.0, ipv6 address 2001:DB8:ACAD:1001::1/64, no shutdown
- Configuration and security for SSH connection.
- ip route 192.168.110.0 255.255.255.0 10.0.0.2
- ip route 0.0.0.0 0.0.0.0 192.168.10.2
- ipv6 route ::/0 2001:db8:acad:10::2
- ipv6 route 2001:db8:acad:110::0/64 2001:db8:acad:1001::2
- interface loopback 0, ip address 192.168.200.1 255.255.255.0
4. RouteurVPN
- ipv6 unicast-routing ;
- Interface with the 2960 ClientVPN: description Lien Sous-Reseau VPN, ip address 192.168.110.254 255.255.255.0, ipv6 address 2001:db8:acad:110::254/64, no shutdown
- Interface with RouteurCG (Serial): description Lien RouteurVPN-RouteurCG, ip address 10.0.0.2 255.255.255.0, ipv6 address 2001:db8:acad:1001::2/64, no shutdown
- Configuration and security for SSH connection.
- ip route 0.0.0.0 0.0.0.0 10.0.0.1, ipv6 route ::/0 2001:db8:acad:1001::1
- interface loopback 0, ip address 192.168.200.2 255.255.255.0
5. 2960 ClientVPN
- No particular configuration.
P.S.: I may have forgotten to add the ‘no shutdown’ command in certain places in my summary.
Could you help me find the problem? I've been pulling my hair out for two days now.
My .pkt file is attached as a zip file.
Thank you in advance for taking the time to help me.
GuillaumeB
_____________________________________________________________________________________________________
Bonjour à toutes et à tous,
Je suis actuellement un cours sur OpenClassrooms :
J'ai suivi le cours jusqu'à l'étape où je dois pinger les différents périphériques terminaux.
C'est là que les choses se compliquent : tous les PC1 peuvent communiquer entre eux, le site distant VPN complet, le réseau Wifi complet et les Serveurs, mais il est impossible de pinger les PC2 et les Imprimantes. (Le problème ne se pose pas en IPv4).
J'ai remarqué que les PC2 ne pouvaient pas communiquer avec leur passerelle Ipv6. Pour les imprimantes, il est possible de pinger la passerelle, mais pas d'aller plus loin.
Plusieurs VLAN existent : 20 Direction, 21 Examen/Concours, 22 Paie/DRH, 23 Emploi, 24 Médecine, 25 Assurance, 27 Info/RGPD, 30 Serveur, 40 Impression, 50 Téléphonie, 60 Wifi et 100 Administration.
Attention, un mot de passe est requis pour la plupart des commutateurs et routeurs.
Voici le mot de passe : 1234-MetroPole:1234.
Voici la configuration en bref :
1. 2960 :
- Interfaces périphériques terminaux : mode access avec voice vlan 50, access vlan x (en fonction du réseau), mls qos trust cos
- Interface en lien avec le 3650 : switchport mode trunk, trunk native 100 et trunk allowed x,x,40,50,100.
- Paramétrage et sécurisation pour connexion en SSH.
2. 3650 :
- ipv6 unicast-routing ;
- Interfaces en lien avec les 2960 : switchport mode trunk, trunk native 100 et trunk allowed x,x,40,50,100.
- Interfaces en lien avec les Serveurs : switchport mode access, access vlan 30
- Interfaces en lien avec le Wifi : switchport mode access, access vlan 60
- Interfaces VLAN x, description Passerelle SVI x, ip address 192.168.x.254 255.255.255.0, ipv6 address 2001:db8:acad:x::254/64.
- Interface avec le RouteurCG : no switchport, ip address 192.168.10.2 255.255.255.0, ipv6 address 2001:DB8:ACAD:10::2/64
- ip routing, ip route 0.0.0.0 0.0.0.0 192.168.10.1
- ipv6 route ::/0 2001:db8:acad:10::1
3. RouteurCG
- ipv6 unicast-routing
- Interface avec le 3650 : ip address 192.168.10.1 255.255.255.0, ipv6 address 2001:DB8:ACAD:10::1/64, no shutdown
- Interface avec le RouteurVPN (Serial) : description Lien RouteurCG-RouteurVPN, ip address 10.0.0.1 255.255.255.0, ipv6 address 2001:DB8:ACAD:1001::1/64, no shutdown
- Paramétrage et sécurisation pour connexion en SSH.
- ip route 192.168.110.0 255.255.255.0 10.0.0.2
- ip route 0.0.0.0 0.0.0.0 192.168.10.2
- ipv6 route ::/0 2001:db8:acad:10::2
- ipv6 route 2001:db8:acad:110::0/64 2001:db8:acad:1001::2
- interface loopback 0, ip address 192.168.200.1 255.255.255.0
4. RouteurVPN
- ipv6 unicast-routing ;
- Interface avec le 2960 ClientVPN : description Lien Sous-Reseau VPN, ip address 192.168.110.254 255.255.255.0, ipv6 address 2001:db8:acad:110::254/64, no shutdown
- Interface avec le RouteurCG (Serial) : description Lien RouteurVPN-RouteurCG, ip address 10.0.0.2 255.255.255.0, ipv6 address 2001:db8:acad:1001::2/64, no shutdown
- Paramétrage et sécurisation pour connexion en SSH.
- ip route 0.0.0.0 0.0.0.0 10.0.0.1, ipv6 route ::/0 2001:db8:acad:1001::1
- interface loopback 0, ip address 192.168.200.2 255.255.255.0
5. 2960 ClientVPN
- Pas de configuration particulière.
P.-S. : j'ai peut-être oublié d'ajouter la commande « no shutdown » à certains endroits dans mon récapitulatif.
Pourriez-vous m'aider à trouver le problème ? Cela fait deux jours que je m'arrache les cheveux.
Vous trouverez ci-joint en .zip mon fichier .pkt.
Merci d'avance pour le temps que vous allez consacrer à mon problème.
GuillaumeB
Solved! Go to Solution.
07-16-2025 01:08 PM
Hi @GuillaumeB1497 ,
Your configuration is fine. There is a bug when running IPv6 on an SVI (vlan interface) in Cisco Packet Tracer. This bug might have been fixed, but seems to be present in the version you are running.
A work around would be to move the routing from the 3650 to the 1941. I changed the config and it worked like a charm.
Here's the working setup.
07-16-2025 01:08 PM
Hi @GuillaumeB1497 ,
Your configuration is fine. There is a bug when running IPv6 on an SVI (vlan interface) in Cisco Packet Tracer. This bug might have been fixed, but seems to be present in the version you are running.
A work around would be to move the routing from the 3650 to the 1941. I changed the config and it worked like a charm.
Here's the working setup.
07-17-2025 12:57 AM - edited 07-17-2025 12:58 AM
Hi @Harold Ritter,
Thank you for your invaluable help. I was reassured to learn that it was a bug.
Thank you for the change you have made.
I'll try to understand what you've done (I'm new to the IT sector), in case I have to run a simulation again and find myself in the same scenario.
Best regards,
GuillaumeB
07-17-2025 07:01 AM
You are very welcome @GuillaumeB1497 and thanks for the feedback. Don't hesitate to come back to the Cisco Community to ask more questions.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide