#cisco
02 January 2008
Total 19 pages. You are browsing page 5/19.
First :: Prev :: [...] [3] [4] [5] [6] [7] [...] :: Next :: Last
11:10 <****> for file transfers
11:11 <****> some isp's do that, but not the commodity (residential) types.
11:11 <****> yep, that's why I pointed at the big ones i.e., comcast, rr, ool
11:11 <****> some us business cable/dsl isp's have special rate limits when the transfer will stay on-net, but not au isp's because of the last-mile issues.
11:11 <****> swbell
11:12 <****> Yep, I know about AU speed conditions. I'v talked about it. Its become a point of discussion when going for voting in AU elections
11:13 <****> most eu isp's have no last mile issues, so they more often would be the same answer as for the us.
11:14 <****> the key is, do they have sufficient reason to have a special on-net rate limit. most do not.
11:16 <****> some small (or very small) isp's do, in that they specifically market such packages.
11:17 <****> hey ppls, sup
11:18 <****> aha
11:18 <****> I think in that case, I can refer to one of our ISPs to increase the data rate for file transfers within the ISP's own network
11:18 <****> Their routers would support it
11:18 <****> They have 7xxx and some 12xxx routers there
11:21 <****> you can always request stuff. whether you should expect it, or "worse" expect it for free, is something else.
11:22 <****> free?
11:22 <****> I bought a 1 Mbps adsl connection from them for over $80
11:22 <****> ./month
11:22 <****> where I work, I have 2 more connections from them
11:25 <****> *shrug*
11:25 <****> meaningless.
11:26 <****> is cisco security agent available freely for linux because i'm going to job corps and I want to have it set up for linux.
11:26 <****> wanting on-net at high speed is asking for something beyond what you already have. if you would like that without paying more you want something for nothing. whether they believe it has a zero (or near zero) cost would be integral to their decision.
11:49 <****> dombre: Yes, i believe it is
11:49 <****> On the server side more than the desktop side I think and probably only supported on Red Hat
11:49 <****> Perhaps SuSE Enterprise... but most likely not your latest Ubuntu release
11:50 <****> FrFluffyBottom: what is the problem to run on every distro I guess its only ur not going to receive a tech support
11:51 <****> the main problem is that it is binary only, and so run-time linking issues exist.
11:52 <****> koriobg|off: Exactly that
11:52 <****> You no doubt could get it to work on other systems
11:52 <****> But if you're of that mentality, then a Cisco product is probably not what you want, as you probably will get equal functionality from some other personal IDS
11:52 <****> Where Cisco shines is support
11:57 <****> hey any of you guys know how intensive voicexml tends to be? just wanna get an idea as to how powerful of a router would be needed to use it pretty extensively
12:12 <****> FrFluffyBottom: well cisco offers end-to-end solution
12:13 <****> FrFluffyBottom: and if this will be deployed in corporate env i will go supported linux distro such as sles or rhes
12:14 <****>
13:00 * FrFluffyBottom agrees
13:00 <****> with ? :|
13:01 <****> FrFluffyBottom: any experience with VPN concentrator ?
13:10 <****> do we get a network topology in the ccie rs lab exam, or do we have to draw it based on interface connection tables that we are given?
13:38 <****> good morning folks and happy new year for the 423589723598nd time :)
13:54 <****> wow Sebastian, yer old! :)
14:18 <****> WOO!!!! its friking Morning and -28C out there !!!
14:21 * xnyx looks around...
14:23 <****> It's -1 here
14:24 <****> -2 here
14:25 <****> I've been up since 3am doing changes.
14:25 <****> It was much colder earlier :)
14:25 <****> where are you porkchop?
14:25 <****> whois porkchop
14:25 <****> oops
14:25 <****> poughkeepsie
14:25 <****> lqtm
14:27 <****> poughkeepsie, new york
14:28 <****> yeah
14:28 <****> the college
14:28 <****> :)
14:28 <****> yeah, I was gonna type more but someone walked in the office
14:28 <****> I was surprised.
14:28 <****> -1? its like 40 here
14:28 <****> I didn't know anyone else was here.
14:28 <****> -1 C
14:28 <****> he was talking C
14:28 <****> Everyone else was talking C, I thought it appropiate to do the same.
14:30 <****> morning
14:30 <****> -2 here
14:30 <****> "The metric system is the tool of the devil. My car gets fourty rods to the hogs head and that's the way I likes it"
14:30 <****> -2 c
14:30 <****> any one worked on VPN concentrator ?
14:31 <****> sadly, yes
14:31 <****> tabularasa: man i am stuck with a strange issue
14:31 <****> i have a LAN to LAN VPN with client
14:32 <****> I was just notified that if one of our staffers doesn't show up, as sometimes happens to him after holidays, I'm giving his presentation to the 80-person department. I've never seen his presentation and only vaguely know what its about. I was expressly forbidden from seeing him give the dry-run presentation to our CIO.
14:32 <****> the ACLs only permit 10.10.10.x to 192.168.168.x but i have local staff accessing the 192.168.168.x subnets from 10.10.11.x too
14:32 <****> i am still trying to figure out - how come VPn concentrator allow this as the subnet is not in LOCAL ACL
14:32 <****> subnet correct?
14:32 <****> er, mask
14:32 <****> thats good
14:33 <****> ive never seen that issue.
14:33 <****> Dump the ACLs to the pastebin. There could be a few different things going on
14:34 <****> its a concentrator
14:34 <****>sessions first
14:34 <****> ipsec sa
14:34 <****> concentrators have acls too. Unless you're talking about like a 3000 series.
14:35 <****> err, printable acls
14:35 <****> porkchop: its 3000
14:35 <****> what other kind of concentrator is there?
14:35 <****> dang.
14:35 <****> einval: i see more traffic towards NAT-T
14:35 <****> ?
14:35 <****> ASAs, PIXs, some routers will perform those duties and could still be called concentrators.
14:36 <****> how is this related to NAT-T?
14:36 <****> porkchop: this is the #Cisco channel.. the product called a "concentrator" is a 3000 series.....
14:36 <****> sigh.
14:36 <****> einval: i mean protocol mostly used is IPSec/NAT-T
14:37 <****> and in sessions protocol is IPSec/LAN-to-LAN
14:37 <****> yeah, but look at the tunnel details for the specific L2L tunnel and see if the negotiated subnets for the IPSec SA are really what you want
14:37 <****> and are not too generic
14:39 <****> einval: interestingly it doesn't have any client address who are actually accessing it
14:39 <****> tunnel is a simple 10.10.10.0/24 & 192.168.168.0/24
Total 19 pages. You are browsing page 5/19.
First :: Prev :: [...] [3] [4] [5] [6] [7] [...] :: Next :: Last