Trying to route between ports on the same subnet

I'm trying to a Cisco 1801 to provide a firewall for my public facing servers. I'm also trying to split the switchports into vlans, 4 ports for public servers, and 4 ports for natted devices on a local lan. The physical setup goes like this

fa0 -> speedtouch dsl modem

switchports
fa1 -> web server
fa2 -> mail server
fa3 -> vpn server
fa4
fa5-8 -> natted pc's on a local lan

I'm not using the atm interface for dsl, because my line is too unstable to support a cisco, the atm resets every 5 seconds or so. So i'm using a speedtouch dsl router to route the public ip's through to the cisco so that i can still utilise access lists etc.

I've configured fa0 with a public ip address, and this can get out to the internet no problem. When i configure a server with a public ip and plug it into vlan1 (fa1-4) it fails to even ping fa0.

Anybody got any thoughts on how to configure this and allow natted devices on vlan2 (fa5-8)?

Cheers
Paul
beplasAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robert Sutton JrSenior Network ManagerCommented:
Is your specific vlan routed?
0
beplasAuthor Commented:
no, both vlan 1 and fa0 are on the same subnet
0
beplasAuthor Commented:
VLAN1
I think i may need vlan1 un-numbered to fa0, but when i try it i get the error
point-to-point (non-multi-access) interfaces only

VLAN2
i have this line in the config
ip nat inside source list 1 interface Vlan3 overload

but when i enter 'ip nat outside' on fa0 i am unable to ping any public ip's
0
cstosgaleCommented:
The easiest solution would be to use a seperate  internal ip range for  the server vlan and use one to one nat from the external interface to vlan 1.

Therefore if you  have public IPs 82.138.231.2 - 7, use say 192.168.1.0 for your servers.

hen use .2 for the fa0 interface, and do a static one to one nat between 82.138.231.3 and 192.168.1.1 for example.

This will give you the same functionality as having public ips for your servers but simplify the routing between internal subnets.

The nat statement above is incorrect as the interface needs to be the outside interface ont the inside interface i.e. ip nat inside source list 1 interface fa0 overload

In addition, for nat to work, you need ip nat inside on any inside interfaces. This would include vlan 1.
In order to prevent the wrong traffic from being natted, make sure source list 1 only contains rules for the workstation subnet. You may find that you will need to use a route map for this as apposed to an access list.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
beplasAuthor Commented:
Worked perfectly, don't know why i didn't think of that myself (that's why YOU are the expert! :))
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.