Search results for query: *

or lets just make this one step easer and drop the whole mask...ill just repost what i put before... just modified to a simpler method. access-list 100 permit tcp host 192.70.101.230 eq smtp any access-list 100 permit tcp host 192.70.101.231 eq smtp any access-list 100 permit tcp host...

access-list 100 permit tcp 192.70.101.230 255.255.255.0 eq smtp any access-list 100 permit tcp 192.70.101.231 255.255.255.0 eq smtp any access-list 100 permit tcp 192.70.101.232 255.255.255.0 eq smtp any access-list 100 permit tcp 192.70.101.233 255.255.255.0 eq smtp any and so on... im not...

perhaps he has it more of a triangle.... R1-----R3 \ / \ / R2

if i were you... i would console in rather than telnet... because you are going to be messing with the inerface that you are going to change.

You dont have to have it as far as i know. However, it is a good idea to set it up that way. in either case when its all said and done you wont have to worry about whats on what vlan except when it comes to the switch... then you are really only worried about 2 vlans... your wired vlan and...

the ip address is fine... its still a private address so you should not have any problems there. if you want you can make it: ip add 10.110.0.1 255.255.255.0

ok as far as your current fastethernet0 interface... you will want to do this first... router#conf t router(config)#default int fa0 that will return the interface back to its defaults(that command should work on that series of router) as far as your "VLAN 1=10.10.1.0/24 (NOT SURE ABOUT THIS)...

looks ok to me

ok if your wired clients are in a vlan 10 and you configured the subinterface for vlan 10 on the router to have and ip address of 10.81.0.1 then that would be the gateway for those wired clients... just like if you configured the sub interface for vlan 20 for your wireless clients to have an ip...

your base interface e0 itself wont have an ip address. the sub interfaces will have the addresses that apply to each of the networks that the vlans represent

ok as far as the kentrox... it is using EFS for the line type, B8ZS for the line coding(which is what the telco wanted us to use and is what is working on all our other t1 connections), and standard ppp for the encapsulation.... which is exactly what i set the cisco router to do, and as far as i...

ok i tested putting a kentrox router from another location in place of the cisco router and it came right up so i know that the line is fine its something with the config on the cisco router or something is just incompatible... has anyone out there configured a t1 conneciton on a cisco router...

it is down/down ... it doesnt come up if the clocking is internal or from the line

the telco just got done testing the link and they say that it is up. however that serial interface is still down. probably going to check on the kentrox, but i wont be able to do that until later.

here is as much of it as i can remember as i cannot connect to it at the moment encapsulation ppp esf b8zs 192.168.250.18 255.255.255.252 loop timing

yes i have... and yes they are default... what isnt default is: service-module t1 clock source internal service-module t1 timeslots 1-24

the off brand router is a kentrox and its defauts are ppp encapsulation, esf and b8zs. I tried using all defauts on the interface and only putting the ip address and of course the no shut command but in show int s0/0 it still says Serial 0/0 is down, line protocol is down. On the WIC itself...

had the telco put in a t1 line between two of our locations. put the t1 WIC in the cisco router and put an off brand t1 router at the remote location. configured the t1 interface as best as i could but it still wont come up here is my config as far as the serial interface is concerned...