<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: [CCNA] Desafio 1 da Semana 5 - Agosto de 2009</title>
	<link>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/</link>
	<description>Blog focado no mercado e nas certificações de T.I.</description>
	<pubDate>Sat, 11 Feb 2012 00:18:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: lucaspedro1</title>
		<link>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-13124</link>
		<author>lucaspedro1</author>
		<pubDate>Fri, 05 Mar 2010 13:58:58 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-13124</guid>
		<description>Falta configurar 2 subinterface na F0a/1 com o endereço 192.168.3.0 e outra para rede 192.168.2.0 para q o router possa rotear as duas redes 
um abraço...</description>
		<content:encoded><![CDATA[<p>Falta configurar 2 subinterface na F0a/1 com o endereço 192.168.3.0 e outra para rede 192.168.2.0 para q o router possa rotear as duas redes<br />
um abraço&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gustavo.ivo</title>
		<link>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11468</link>
		<author>gustavo.ivo</author>
		<pubDate>Sat, 05 Sep 2009 17:38:10 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11468</guid>
		<description>configurar a porta fa0/1 em modo trunk
ativar encapsulamento dot1q no router r1

confiurar gateway na maquinas com endereços das subinterfaces do router r1
no shutdown na interface fisica f0/0</description>
		<content:encoded><![CDATA[<p>configurar a porta fa0/1 em modo trunk<br />
ativar encapsulamento dot1q no router r1</p>
<p>confiurar gateway na maquinas com endereços das subinterfaces do router r1<br />
no shutdown na interface fisica f0/0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gabrielsouzafatec</title>
		<link>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11464</link>
		<author>gabrielsouzafatec</author>
		<pubDate>Sat, 05 Sep 2009 00:19:03 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11464</guid>
		<description>Falta a configuração no R1 para que a hosts de vlans diferentes possam se comunicar, incluindo a 192.168.3.0 na sub-interface fast0/1.3 do router R1.</description>
		<content:encoded><![CDATA[<p>Falta a configuração no R1 para que a hosts de vlans diferentes possam se comunicar, incluindo a 192.168.3.0 na sub-interface fast0/1.3 do router R1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fabio_candido</title>
		<link>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11454</link>
		<author>fabio_candido</author>
		<pubDate>Thu, 03 Sep 2009 00:32:46 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/08/24/ccna-desafio-1-da-semana-5-agosto-de-2009/#comment-11454</guid>
		<description>faltou criar a sub interface no router R1 referente a rede 192.168.3.0. para haver comunicacao entre vlan diferentes tem que haver um equipamento de nivel 3, no caso o router, para rotear os pacotes afinal sao de redes diferentes

interface FastEthernet0/1
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/1.1
 encapsulation dot1Q 1 native
 ip address 192.168.1.1 255.255.255.0
!
interface FastEthernet0/1.2
 encapsulation dot1Q 2
 ip address 192.168.2.1 255.255.255.0
!
interface FastEthernet0/1.3
 encapsulation dot1Q 3
 ip address 192.168.3.1 255.255.255.0
!


Router 1#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

C    192.168.1.0/24 is directly connected, FastEthernet0/1.1
C    192.168.2.0/24 is directly connected, FastEthernet0/1.2
C    192.168.3.0/24 is directly connected, FastEthernet0/1.3
Router 1#</description>
		<content:encoded><![CDATA[<p>faltou criar a sub interface no router R1 referente a rede 192.168.3.0. para haver comunicacao entre vlan diferentes tem que haver um equipamento de nivel 3, no caso o router, para rotear os pacotes afinal sao de redes diferentes</p>
<p>interface FastEthernet0/1<br />
 no ip address<br />
 duplex auto<br />
 speed auto<br />
!<br />
interface FastEthernet0/1.1<br />
 encapsulation dot1Q 1 native<br />
 ip address 192.168.1.1 255.255.255.0<br />
!<br />
interface FastEthernet0/1.2<br />
 encapsulation dot1Q 2<br />
 ip address 192.168.2.1 255.255.255.0<br />
!<br />
interface FastEthernet0/1.3<br />
 encapsulation dot1Q 3<br />
 ip address 192.168.3.1 255.255.255.0<br />
!</p>
<p>Router 1#sh ip route<br />
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP<br />
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area<br />
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2<br />
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP<br />
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area<br />
       * - candidate default, U - per-user static route, o - ODR<br />
       P - periodic downloaded static route</p>
<p>Gateway of last resort is not set</p>
<p>C    192.168.1.0/24 is directly connected, FastEthernet0/1.1<br />
C    192.168.2.0/24 is directly connected, FastEthernet0/1.2<br />
C    192.168.3.0/24 is directly connected, FastEthernet0/1.3<br />
Router 1#</p>
]]></content:encoded>
	</item>
</channel>
</rss>

