I have new service from AT&T which they state is sending untagged traffic to all my new ports.
At my central office I have a 2821 with an interface configured like this:
interface GigabitEthernet0/1/0
description (Fiber connection to HFE/
no ip address
negotiation auto
!
interface GigabitEthernet0/1/0.1
encapsulation dot1Q 20
ip address 172.16.5.1 255.255.255.0
!
interface GigabitEthernet0/1/0.2
encapsulation dot1Q 10 native
ip address 172.16.2.1 255.255.255.0
At the remote sites I've tried tagging the interface for Vlan# but it doesn't seem to matter. What does work is which ever side I set for "Native". So router2 let's say had an interface configured for 172.16.2.2 it's running along no problem.
router3 172.16.5.2 doesn't get any traffic.
I know I am missing something. Please talk to me like I am 5 because I am just a lone ranger on this one without a smartnet contract.
Thank you for the reply. If I remove the encap then it strips the ip address also. When I go to reapply the address I get :
% Configuring IP routing on a LAN subinterface is only allowed if that
subinterface is already configured as part of an IEEE 802.10, IEEE 802.1Q,
or ISL vLAN.
For the record, I am 99% this is user error.
*edit* Sorry, yes the service is basic (best effort).
Well they say it's untagged traffic. Router 2 is at one physical location and Router 3 at another. My understanding was that all traffic was available to all locations (not port based).
harbor235
opt-e-man basic is pt-2-pt only, the other service is multi-point. I would sniff the traffic and see what is coming in, tagged or untagged. If it is untagged only that means there are no additional vlans arriving via tagged frames. Are you sure you are getting multiple vlans with that service?
So, if they are untagged you do not add the encapsulation commands, it would be as if they are on the same vlan on your closet switch. All you would need to do is configure a layer3 interface and ip address. AT&T's network is a layer 2 transport network.
% Configuring IP routing on a LAN subinterface is only allowed if that
subinterface is already configured as part of an IEEE 802.10, IEEE 802.1Q,
or ISL vLAN.
For the record, I am 99% this is user error.
*edit* Sorry, yes the service is basic (best effort).