[TriLUG] Off Topic: Need Cisco Router Config Help

[Matt Pusateri]

Actually I think it's more of a DNS issue.  From the looks of things, 
the cisco is serving dhcp internally but pointing them to an external 
dns server, so when internal clients do a lookup they get an external 
address.  What I would probably do is either setup a subzone for 
internal use or setup a dns server inside that can serve internal and 
external dns and then use views to control which zones files get queried 
based upon whether your inside or outside.  The outside zone could even 
possibly slave off the existing external DNS server.


Matt P.

Tarus Balog wrote:
> Gang:
>
> This is off topic, but I figure there are some Cisco gurus out there  
> who can give me a hand.
>
> We used to have a Linksys router hooked up to the Zyxel "modem" Embarq  
> gave us for the DSL line, and we started to have problems, so I bought  
> a Cisco 800 series router that could serve both purposes.
>
> Although my Cisco-fu is weak, I was able to get it working pretty  
> well ... except for one thing.
>
> When I am outside the LAN, I connect to "private.opennms.com" which is  
> NAT'd to a box in the office: 172.20.1.10. This worked fine when I was  
> using the Linksys router, but this doesn't seem to work now.  
> Connections to the "private.opennms.com" address don't seem to NAT if  
> we are coming in from the local network. For example, if I want to  
> access http://private.opennms.com from the office, it'll fail, but it  
> works fine if I do it from the internet. While in the office I have to  
> set up an /etc/hosts file entry to point private.opennms.com to  
> cartman (our internal file server).
>
> And clues?
>
> -T
>
> Here are the important bits of my config:
>
> ip subnet-zero
> ip cef
> no ip dhcp use vrf connected
> ip dhcp binding cleanup interval 600
> ip dhcp excluded-address 172.20.1.1 172.20.1.99
> !
> ip dhcp pool office
>     network 172.20.1.0 255.255.255.0
>     default-router 172.20.1.1
>     dns-server 172.20.1.10
>     domain-name internal.opennms.com
> !
> ip domain name opennms.com
> ip name-server 63.xx.yy.zz
> !
> !
> !
> bridge irb
> !
> !
> interface ATM0
>   no ip address
>   no atm ilmi-keepalive
>   pvc 8/35
>    encapsulation aal5snap
>   !
>   dsl operating-mode auto
>   bridge-group 1
> !
> interface FastEthernet0
> !
> interface FastEthernet1
> !
> interface FastEthernet2
> !
> interface FastEthernet3
> !
> interface Vlan1
>   ip address 172.20.1.1 255.255.255.0
>   ip nat inside
>   ip virtual-reassembly
> !
> interface BVI1
>   ip address 63.x.y.z 255.255.255.0
>   ip nat outside
>   ip virtual-reassembly
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 63.x.y.z
> !
> no ip http server
> no ip http secure-server
> ip nat inside source list 1 interface BVI1 overload
> ip nat inside source static tcp 172.20.1.10 80 interface BVI1 80
> !
> control-plane
> !
> bridge 1 protocol ieee
> bridge 1 route ip
>
>
>
> _______________________________________________________________________
> Tarus Balog, OpenNMS Maintainer             Main:   +1 919 533 0160
> The OpenNMS Group, Inc.                     Fax:    +1 503 961 7746
> Email: tarus at opennms.org                    URL: http://www.opennms.org
> PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C
>
>