<div>Thanks to all!</div>
<div> </div>
<div>I'll give a try on the suggested solutions and will advise of the outcome.</div>
<div> </div>
<div>cheers,</div>
<div>Patrick<br><br></div>
<div class="gmail_quote">On Wed, Jan 14, 2009 at 3:49 AM, Frank Bulk <span dir="ltr"><<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Brian is basically suggesting that the service provider route the /29 via<br>the IP address the PPPoE client obtains. That means the customer has an<br>
outside (PPPoE) and inside (/29) interface.<br><br>I haven't tried bridging, but I would think it's possible to have the<br>service provider's RADIUS server hand out an IP address from the /29 block<br>to the PPPoE client, and then bridge the other IPs in the /29.<br>
<br>I think it would be much more straight forward if you could have bridged<br>connection or do what Brian recommended.<br><font color="#888888"><br>Frank<br></font>
<div class="Ih2E3d"><br>-----Original Message-----<br>From: <a href="mailto:cisco-bba-bounces@puck.nether.net">cisco-bba-bounces@puck.nether.net</a><br></div>
<div class="Ih2E3d">[mailto:<a href="mailto:cisco-bba-bounces@puck.nether.net">cisco-bba-bounces@puck.nether.net</a>] On Behalf Of Brian Raaen<br>Sent: Monday, January 12, 2009 6:21 PM<br>To: <a href="mailto:cisco-bba@puck.nether.net">cisco-bba@puck.nether.net</a><br>
Subject: Re: [cisco-bba] PPPoE with Routed Subnet<br><br></div>
<div>
<div></div>
<div class="Wj3C7c">Patrick,<br> If this is like most of the PPPoE setups I have worked with (I work<br>on the<br>service provider side of things) you would have a static that is assigned to<br>the wan of your router using ipip, and the /29 is routed to that<br>
address(think - ip route $subnet 255.255.255.248 $static). When that subnet<br>hits your router you can do pretty much anything you want to with it. We<br>usually suggest that customers assign the first usable to the lan of their<br>
router (usually ala linksys variety) and make sure that nat(or gateway mode)<br>is turned off. They would set up their internal host using an ip out of the<br>subnet with the router internal as their gateway. Some customers even add a<br>
second router for NATing (if you are using lo end soho routers that may be<br>your only option). Since you are using a IOS powered cisco you can look<br>into<br>using something like 1:1 nat to allow you to use all 8 addresses in the<br>
subnet if you want to make sure to use one for pat (i.e. standard nat) if<br>you<br>need to.<br><br><br>----------------------<br><br>Brian Raaen<br>Network Engineer<br><a href="mailto:braaen@zcorum.com">braaen@zcorum.com</a><br>
<br>On Sunday 11 January 2009, Patrick Wu wrote:<br>> Hi Everyone,<br>><br>> I have a DSL connection running PPPoE with a routed subnet, the service<br>> provider indicated that it will use the 1st IP address of the routed<br>
subnet<br>> for the router (WAN?), and the rest of the IPs of the subnet can be<br>assigned<br>> to the hosts behind the router.<br>><br>> What I want to know is whether I need a bridged interface between the WAN<br>
> and LAN side of the router (Cisco877), and what configuration will help me<br>> achieve this?<br>><br>> Thanks to all!<br>><br>> What I have so far (was doing NAT before, but probably will remove it<br>
> later):<br>><br>> interface ATM0<br>> no ip address<br>> no atm ilmi-keepalive<br>> dsl operating-mode auto<br>> service-policy output SIP-priority<br>> !<br>> interface ATM0.1 point-to-point<br>
> description $FW_OUTSIDE$$ES_WAN$<br>> pvc 8/35<br>> pppoe-client dial-pool-number 1<br>> !<br>> !<br>> interface FastEthernet0<br>> !<br>> interface FastEthernet1<br>> !<br>> interface FastEthernet2<br>
> !<br>> interface FastEthernet3<br>> !<br>> interface Vlan1<br>> description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$$ES_LAN$$FW_INSIDE$<br>> ip address 192.168.0.1 255.255.255.0<br>> ip nat inside<br>
> ip virtual-reassembly<br>> ip tcp adjust-mss 1412<br>> !<br>> interface Dialer0<br>> description $FW_OUTSIDE$<br>> ip address negotiated<br>> ip mtu 1452<br>> ip nat outside<br>> ip virtual-reassembly<br>
> encapsulation ppp<br>> dialer pool 1<br>> dialer-group 1<br>> no cdp enable<br>> ppp authentication pap callin<br>> ppp pap sent-username xxxx@xxxx password 7 xxxx<br>> !<br>> ip forward-protocol nd<br>
> ip route 0.0.0.0 0.0.0.0 Dialer0<br>> !<br>> ip nat translation udp-timeout never<br>> ip nat inside source list 1 interface Dialer0 overload<br>><br><br><br>_______________________________________________<br>
cisco-bba mailing list<br><a href="mailto:cisco-bba@puck.nether.net">cisco-bba@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-bba" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-bba</a><br>
<br>_______________________________________________<br>cisco-bba mailing list<br><a href="mailto:cisco-bba@puck.nether.net">cisco-bba@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-bba" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-bba</a><br>
</div></div></blockquote></div><br>