I will have to agree with Jarrod's reasoning on this one. But you do need to ask what you will be using these lines for?
If this was a business situation or you were pumping lots of stuff down the pipe then I would run seperate lines. Takes no extra time and costs nothing extra to run two lines instead of one. If it was for home use or low data throughout I can't see any problems with it. If you have the time and resources, do a small test run with both scenarios and see what your line testing brings up (i.e. dropped packets, etc.). Try it at different data loads and different times of day, etc and if all goes well, then you have your answer. One thing you could look at is some sort of data shaping. Basically allocating certain types of traffic certain levels of service and bandwiodth to take up. Packeteer is probably one of the best known "appliance packet shapers" out there and there equipment is pretty cool. I have some information on them from my days of working with it. But I am sure there are some FLOSS projects out there that will do the same thing. I would be interested to hear what you discover and finally decide on. Cameron > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Jarrod Major > Sent: Thursday, June 09, 2005 10:32 PM > To: 'CLUG General' > Subject: RE: [clug-talk] voice & data on cat5 > > > A Pro would be that your regular 100BaseT Ethernet users two pairs out of > the four so theoretically you could use the extra two pair to do > voice. I'm > not sure if telephone cabling and Ethernet cabling would suffer from being > run in the same housing. Anyone with network cabling want to comment on > this? > > I know that for my DSL at home, rather than use filters, I have one line > from the demarc that has the off pair of wires being used for the DSL from > the POTS splitter. The other pair has plain old telephone on it > and as such > it doesn't appear to have any degradation from proximity. > > _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
