(no subject)

[Brian J. McGovern]

> On the switch side of things I'm using a Cisco 3550 runing layer3
> code, I've had this working before with a em driver (on another box)
> but my setup was a little different then so I'm pretty sure the switch
> isnt at fault?

Is the vr interface capable of sending > 1500 byte MTUs? Its not in the vlan(4)
man page. This could be one area to look at, or, if its one of the other causes 
below, you may have issues with big packets.

> My rc.conf looks like:
> 
> cloned_interfaces="vlan100 vlan200 vlan233"
> ifconfig_vr0="up"
> ifconfig_vlan100="inet 192.168.100.1 netmask 255.255.255.0 vlan 100 vlandev vr0"
> ifconfig_vlan200="inet 192.168.200.1 netmask 255.255.255.0 vlan 200 vlandev vr0"
> ifconfig_vlan233="inet 10.233.233.1 netmask 255.255.255.0 vlan 233 vlandev vr0"
> ifconfig_vr0="inet 10.254.254.252 netmask 255.255.255.0 media100baseTX mediaopt full-duplex"
> defaultrouter="10.254.254.254"

This looks reasonable. However, your first ifconfig_vr0 line will get 
overridden by the second, and is therefore redundant. Does "ifconfig -a"
confirm that everything gets set up ok?

> and my switch config looks like this:
> 
> interface FastEthernet0/12
>   switchport access vlan 254
>   switchport trunk encapsulation dot1q
>   switchport trunk allowed vlan 100,200,233
>   switchport mode trunk
>  logging event trunk-status
>  duplex full
>  speed 100
> end

The "switchport access vlan 254" looks suspect. A trunking port shouldn't
have access port parameters. You're also missing vlan 1. See below...

> I'm getting to the point that the vlan interfaces (100,200,233) can
> talk to machines on their subnet but I cannot seem to ping anything on
> the 10.254.254.0/24 subnet (ip address applied to vr0 interface) or
> anythnig via the default route.

Well, if you can't ping anything on the subnet, that would assume you can't
reach the default gateway, and therefore, its not surprising you can't
ping anything further upstream :)

>From what I see here, you never allow vlan1 to travel on your trunk. vr0, as an "unvlan'ed" 
interface, will default to vlan1 with dot1q.

> If anyone can assist me I'd appreciate it, please contact me off list
> as I am not subscribed to -questions.
> 
> Cheers,
> 
> Will