 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Journey of a Network Engineer &#187; PPPoE</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/network-engineering-journey/tag/pppoe/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey</link>
	<description></description>
	<lastBuildDate>Tue, 26 Feb 2013 11:05:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>How to Configure PPPoE?</title>
		<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey/how-to-configure-pppoe/</link>
		<comments>http://itknowledgeexchange.techtarget.com/network-engineering-journey/how-to-configure-pppoe/#comments</comments>
		<pubDate>Tue, 25 Oct 2011 06:34:05 +0000</pubDate>
		<dc:creator>Sulaiman Syed</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Configure]]></category>
		<category><![CDATA[dhcp]]></category>
		<category><![CDATA[how]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[ios]]></category>
		<category><![CDATA[PPPoE]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[virtual]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/network-engineering-journey/?p=174</guid>
		<description><![CDATA[This is one of the interesting things i have learned in past week. PPP over Ethernet (PPPoE). It is simple, yet tricky. It also has a limitation that network engineers might not know which will bring their network down. Lets see a sample configuration of how to do it. First, configure one Router to be [...]]]></description>
				<content:encoded><![CDATA[<p>This is one of the interesting things i have learned in past week. PPP over Ethernet (PPPoE). It is simple, yet tricky. It also has a limitation that network engineers might not know which will bring their network down.</p>
<p>Lets see a sample configuration of how to do it. First, configure one Router to be the client (dialer) that will ask for ip address through DHCP. We have configured Chap Authentication as well. Remember, that since we are running PPPoE, a virtual Dialer (interface) has to be configured with all the details, and lastly applied to the Ethernet interface.</p>
<blockquote><p>R4(config)#interface Dialer1</p>
<p>R4(config-if)# ip address dhcp</p>
<p>R4(config-if)# encapsulation ppp</p>
<p>R4(config-if)# dialer pool 6</p>
<p>R4(config-if)# ppp chap hostname R4</p>
<p>R4(config-if)# ppp chap password 0 cisco</p>
<p>R4(config-if)#exit</p>
<p>R4(config)#interface Ethernet0/1</p>
<p>R4(config-if)# no ip address</p>
<p>R4(config-if)# pppoe enable</p>
<p>R4(config-if)# pppoe-client dial-pool-number 6</p></blockquote>
<p>Second, we would configure the other Router with DCHP scope, and to be the server for PPPoE. We would also configure local username and password for chap authentication.</p>
<blockquote><p>R6(config)#interface Virtual-Template1</p>
<p>R6(config-if)# ip address 155.1.146.6 255.255.255.0</p>
<p>R6(config-if)# peer default ip address dhcp-pool VLAN146</p>
<p>R6(config-if)# ppp authentication chap</p>
<p>R6(config-if)# exit</p>
<p>R6(config)#ip dhcp pool VLAN146</p>
<p>R6(dhcp-config)#   network 155.1.146.0 255.255.255.0</p>
<p>R6(dhcp-config)#exit</p>
<p>R6(config)#bba-group pppoe MYPPP</p>
<p>R6(config-bba-group)# virtual-template 1</p>
<p>R6(config-bba-group)#exit</p>
<p>R6(config)#interface Ethernet0/1</p>
<p>R6(config-if)# no ip address</p>
<p>R6(config-if)# pppoe enable group MYPPP</p></blockquote>
<p>Lets try some pings</p>
<blockquote><p>R6(config)#bba-group pppoe MYPPP</p>
<p>R6(config-bba-group)# virtual-template 1</p>
<p>R6(config-bba-group)#e</p>
<p>*Sep 22 18:30:41.911: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up</p>
<p>*Sep 22 18:30:42.923: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up</p>
<p>R6(config-bba-group)#exit</p></blockquote>
<p>We notice that the ping command for size 1500 failed. Lets find out why.</p>
<p>R6#show int virtual-access 2.1</p>
<p>Virtual-Access2.1 is up, line protocol is up</p>
<p>Hardware is Virtual Access interface</p>
<p>Internet address is 155.1.146.6/24</p>
<p>MTU 1492 bytes, BW 100000 Kbit/sec, DLY 100000 usec,</p>
<p>reliability 255/255, txload 1/255, rxload 1/255</p>
<p>Encapsulation PPP, LCP Open</p>
<p>Open: IPCP</p>
<p>PPPoE vaccess, cloned from Virtual-Template1</p>
<p>Vaccess status 0&#215;0</p>
<p>Keepalive set (10 sec)</p>
<p>72 packets input, 11972 bytes</p>
<p>70 packets output, 9604 bytes</p>
<p>Last clearing of &#8220;show interface&#8221; counters never</p>
<p>While at R4 we have.</p>
<p>R4#show int dialer 1</p>
<p>Dialer1 is up, line protocol is up (spoofing)</p>
<p>Hardware is Unknown</p>
<p>Internet address is 155.1.146.2/24</p>
<p>MTU 1500 bytes, BW 56 Kbit/sec, DLY 20000 usec,</p>
<p>reliability 255/255, txload 1/255, rxload 1/255</p>
<p>Encapsulation PPP, LCP Closed, loopback not set</p>
<p>Keepalive set (10 sec)</p>
<p>DTR is pulsed for 1 seconds on reset</p>
<p>Interface is bound to Vi1</p>
<p>Last input never, output never, output hang never</p>
<p>Last clearing of &#8220;show interface&#8221; counters 00:09:56</p>
<p>Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0</p>
<p>Queueing strategy: weighted fair</p>
<p>Output queue: 0/1000/64/0 (size/max total/threshold/drops)</p>
<p>Conversations  0/0/16 (active/max active/max total)</p>
<p>Reserved Conversations 0/0 (allocated/max allocated)</p>
<p>Available Bandwidth 42 kilobits/sec</p>
<p>5 minute input rate 0 bits/sec, 0 packets/sec</p>
<p>5 minute output rate 0 bits/sec, 0 packets/sec</p>
<p>18 packets input, 8890 bytes</p>
<p>77 packets output, 27485 bytes</p>
<p>Bound to:</p>
<p>Virtual-Access1 is up, line protocol is up</p>
<p>Hardware is Virtual Access interface</p>
<p>MTU 1500 bytes, BW 56 Kbit/sec, DLY 20000 usec,</p>
<p>reliability 255/255, txload 1/255, rxload 1/255</p>
<p>Encapsulation PPP, LCP Open</p>
<p>Stopped: CDPCP</p>
<p>Open: IPCP</p>
<p>PPPoE vaccess, cloned from Dialer1</p>
<p>Vaccess status 0&#215;44, loopback not set</p>
<p>Keepalive set (10 sec)</p>
<p>DTR is pulsed for 5 seconds on reset</p>
<p>Interface is bound to Di1 (Encapsulation PPP)</p>
<p>Last input 00:00:08, output never, output hang never</p>
<p>Last clearing of &#8220;show interface&#8221; counters 00:04:29</p>
<p>Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0</p>
<p>Queueing strategy: fifo</p>
<p>Output queue: 0/40 (size/max)</p>
<p>5 minute input rate 0 bits/sec, 0 packets/sec</p>
<p>5 minute output rate 0 bits/sec, 0 packets/sec</p>
<p>76 packets input, 9688 bytes, 0 no buffer</p>
<p>Received 0 broadcasts, 0 runts, 0 giants, 0 throttles</p>
<p>0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort</p>
<p>88 packets output, 27611 bytes, 0 underruns</p>
<p>0 output errors, 0 collisions, 0 interface resets</p>
<p>It is shown that the MTU is 1492. Lets configure the MTU size at the dialer interface.</p>
<blockquote><p>R4(config)#interface Dialer1</p>
<p>R4(config-if)# ip mtu 1492</p></blockquote>
<p>Test ping again&#8230;</p>
<blockquote><p>4#ping 155.1.146.6 size 2000</p>
<p>Type escape sequence to abort.</p>
<p>Sending 5, 2000-byte ICMP Echos to 155.1.146.6, timeout is 2 seconds:</p>
<p>!!!!!</p>
<p>Success rate is 100 percent (5/5), round-trip min/avg/max = 8/12/16 ms</p>
<p>R4#</p></blockquote>
<p>And it is working. Well, this is how PPPoE is configured, i hope this will help you when you configuring it.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/network-engineering-journey/how-to-configure-pppoe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
