I have two static (public)ip addresses 80.xxx.xxx.153 255.255.255.252 and 80.xxx.xxx.154 255.255.255.252
My ISP delivered a Thomson Speedtouch router who was configurated like the drawing. I have replaced the Thomson router with the 876. The problem is that I got it to work with NAT, but I would like it not to be NATed. Bridged between Dsl interface and BVI1 or Fe0.
Yes, I know it's old but I had a similar issue this week with my new connection. I used ip unnumbered.
Hopefully this will be of use to others too.
Try something like:
This is for a connecting a Cisco 877w to BT's new FTTC service but should work on any Cisco router supporting vlans with a relatively recent IOS version.
PPPoE assigned /27 from ISP. I'm using IP unnumbered to allow the rest of the pool to be split between NAT and real addressing.
3 subnets/vlans: 1 internal wired (1), 1 wlan (5), 1 DMZ/external (87) NAT/PAT pool for some internal addresses, static NAT for others. A small /29 DMZ subnet for when NAT is undesirable. Fast Ethernet 1 runs as a trunk for all vlans except vlan 5 (wlan) Fast Ethernet 3 is connected to the VDSL modem
DHCP Server for the 3 vlans I've got some other internal routers connected and using OSPF.
!!!!This is not a complete config!!!!!! !!!!Add security etc. Before use!!!!!!!
! ! ip dhcp excluded-address 192.168.5.254 ip dhcp excluded-address a.b.c.126 ip dhcp excluded-address 192.168.6.254 ! ip dhcp pool wlan5 network 192.168.5.0 255.255.255.0 domain-name default-router 192.168.5.254 dns-server 192.168.6.133 126.96.36.199 188.8.131.52 lease 7 ! ip dhcp pool lan network 192.168.6.0 255.255.255.0 domain-name default-router 192.168.6.254 dns-server 192.168.6.133 184.108.40.206 220.127.116.11 lease 7 ! ip dhcp pool dmz network a.b.c.120 255.255.255.248 domain-name default-router a.b.c.126 dns-server 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 lease 3 ! vpdn enable ! vpdn-group 1 request-dialin protocol pppoe ! interface FastEthernet0 duplex full speed 100 ! interface FastEthernet1 switchport trunk allowed vlan 1-4,6-4094 switchport mode trunk duplex full speed 100 ! interface FastEthernet2 duplex full speed 100 ! interface FastEthernet3 switchport access vlan 87 duplex full speed 100 ! interface Dot11Radio0 ip address 192.168.5.254 255.255.255.0 ip pim sparse-dense-mode ip nat inside ip virtual-reassembly ! interface Vlan1 ip address 192.168.1.254 255.255.255.0 secondary ip address 192.168.6.254 255.255.255.0 ip pim sparse-dense-mode ip nat inside ip virtual-reassembly load-interval 30 ! interface Vlan87 description DMZ fttc WAN ip address a.b.c.126 255.255.255.224 ip nat outside ip virtual-reassembly ip tcp adjust-mss 1452 pppoe enable group global pppoe-client dial-pool-number 1 ! interface Dialer1 ip unnumbered Vlan87 ip nat outside ip virtual-reassembly encapsulation ppp ip tcp adjust-mss 1452 load-interval 30 dialer pool 1 dialer-group 1 ppp authentication chap pap callin ppp chap hostname ppp chap password 7 ppp ipcp dns request ! router ospf 1 log-adjacency-changes redistribute connected subnets redistribute static subnets network 192.168.5.0 0.0.0.255 area 0 network 192.168.6.0 0.0.0.255 area 0 default-information originate ! ip nat pool myisp a.b.c.108 a.b.c.116 prefix-length 27 ip nat inside source list nat-allow pool myisp overload ip nat inside source static 192.168.6.133 a.b.c.97 extendable ip nat inside source static tcp 192.168.6.201 22 a.b.c.98 62022 extendable ip nat inside source static tcp 192.168.5.253 80 a.b.c.98 80 extendable ! ip access-list extended nat-allow permit ip 192.168.0.0 0.0.15.255 any ! access-list 100 permit ip 192.168.0.0 0.0.15.255 any ! dialer-list 1 protocol ip list 100 ! route-map myisp permit 10 match ip address 100 match interface Dialer1 ! !
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...