Whenever I try to assign vlan1 an IP address that is on the same class C as fa0/0, it gives me the following error:

"% x.x.x.0 overlaps with FastEthernet0/0"

It will only accept an IP address that is on a completely separate class C, there for I need to add some static routes if I want the vlan to be able to access the fa0/0 lan and the internet.

ofcourse u cant

u cant have two routed interface with the same subnet range IPs

lets say the following example

interface vlan 1

ip address 192.168.1.1 255.255.255.0

interface fa0/0

ip address 192.168.1.50 255.255.255.0

in the above example u will get anerror same to what u are getting now

so to solve it

do

interface fa0/0

ip address 192.168.2.50 255.255.255.0

now u have put interface fa0/0 in deffrent subnet and will work normaly

good luck

if u need any more details just post here :)

please, if helpful rate

No it won't. That is what I'm doing now and the problem is that then vlan1 won't have access to fa0/0 or the internet without adding some routes to the routing table. If you read my original post you will see the problem that I'm having in adding those routes to the routing table.

Please post the entire config and, if possible, do not "X" out the addresses. If they are private addresses, you dont have to X them out.

Thanks

Victor is correct that it will be easier to resolve this if we have the complete config to look at. It would also be helpful to have the output of show ip route.

When a subnet (or network) is assigned to the VLAN interface it should show up in the routing table as a connected route. And a static route for the same prefix should not show up in the routing table. I suspect that this may be why the static route for VLAN 1 does not show up. I am quite curious about the static route for F0/0. The original post seems to imply that this static route does show up. I wonder if that is really the case.

HTH

Rick

Hello Rafe,

you had your router configured and working and then you added an etherswitch.

If you want to provide internet access to the etherswitch's ports users in vlan 1 what you need is :

a change on your NAT rules so that also source addresses of VLan1, that cannot be the same as int f0/0 as noted in previuos posts, can be translated when going to the internet

you don't need static routes on a single router to route traffic between connected interfaces

Hope to help

Giuseppe

Thanks, but I acutally got it working last yesterday. As it turns out, it was a problem with NAT. Althought the class C that I have on the vlan interface still isn't showing up in the routing table for some stange reason. But, I don't care anymore because like I said, I got it working. :)

Hello Tim,

this can be done or not depending on router platform.

int fas0/0 is a router port and expects to have an ip address.

I can put int fas0/0 and vlan 1 in the same bridge-group and then I can assign the ip address and the ip nat inside to the BVI interface (the L3 interface of bridge-group using integrated routing and bridging).

I'm not sure that is possible on a router.

In other words I suppose that:

int fas0/0

(1)switchport

(1)switchport mode access

(1) switchport access vlan 1

can be rejected by the CLI

I would suggest

bridge 1 route ip

bridge 1 protocol ieee

int fas0/0

no ip address

bridge-group 1

int vlan1

no ip address

(2) bridge-group 1

int bv1

ip address x.x.x.x 255.255.255.0

ip nat inside

but I'm afraid that (2) could be not accepted.

Solution 1) that you have suggested could work on a C870, but here is using a C2600 or more, because it has inserted an etherswitch module.

In this kind of platform I think switchport commands are accepted on etherswitch's ports only, but I may be wrong.

On the other side I used inter-vlan bridging on a C3550 and I don't know if here it is allowed (command (2) above).

So the answer is that your solution can work but it should be tested.

In theory is a good solution. In my previous post I wanted to move focus on NAT because it is that feature that allows to go to the internet.

The router routes between connected L3 interfaces without any need of static routes

Only the default route out dialer1 is needed here.

Hope to help

Giuseppe

I've had others give that exact same suggestion, but I just can't stand wasting a port on the etherswitch by doing that, but it really dosn't matter any more because I got it working the way I wanted yesterday. :)

Hello Rafe,

nice to hear you solved your issue

May I ask you what you have done to have it working ?

Best Regards

Giuseppe