Re: local network with twisted rj45
On Sat, Feb 03, 2007 at 10:38:09AM -0800, christop wrote: > On 18 jan, 05:20, Evan <[EMAIL PROTECTED]> wrote: > > I would first change the IP address so that one workstation does not > > have a broadcast address(.0) Try a simple scheme like .1 and .2. > > > > Sorry not having answered before. > What you said is the point. > You can't use an ip address ending by .0 for yourself. Well, you can, just not when it is the broadcast address :) Also Windows really doesn't like it. But in a /23 like 192.168.0.0 -> 192.168.1.255, 192.168.0.255 and 192.168.1.0 should both be perfectly usable host addresses. -- http://bitfolk.com/ -- No-nonsense VPS hosting Encrypted mail welcome - keyid 0x604DE5DB signature.asc Description: Digital signature
Re: local network with twisted rj45
On 18 jan, 05:20, Evan <[EMAIL PROTECTED]> wrote: > I would first change the IP address so that one workstation does not > have a broadcast address(.0) Try a simple scheme like .1 and .2. > Sorry not having answered before. What you said is the point. You can't use an ip address ending by .0 for yourself. And it did work fine then. Thank you for all. Ch. > On 17 Jan 2007 19:40:48 -0800, christop <[EMAIL PROTECTED]> wrote: > > > > > Michael D. Norwick a écrit : > > > christop wrote: > > > > I would need information on how to configure > > > > a local network between two computers > > > > with only a twested rj45. > > > > > I have two ethernet cards on each of the two computers > > > > I aim to put together. > > > > < snip > > > > >http://www.aboutdebian.com/network.htm > > > I gave a glance, see it later, > > thanks. > > > Ch. > > > > michael > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED]
Re: local network with twisted rj45
On Thu, Jan 18, 2007 at 08:46:41AM +0100, Jhair Tocancipa Triana wrote: > Russell L Harris writes: > > > The nice thing about a switch or hub is that (1) it allows you to > > use common straight cables and > > Crossover cables can be easily purchased from any (good) electronics > shop. > > > (2) it has an LED which gives you a visual indication of the amount > > of traffic flowing. > > I cannot see how this can be an advantage over using a crossover cable > in the context the OP is trying to use it. because when OP decides to add another box to his growing net, then he'll either have an extra/useless cable or (as I've done on one run in my house) get *another* crossover cable to patch it together into the switch when the time comes... :) A signature.asc Description: Digital signature
Re: local network with twisted rj45
On Thu, 18 Jan 2007 22:56:58 +0200 "Nick Demou" <[EMAIL PROTECTED]> wrote: > networking two pcs with a twisted (crosslink ) cable _couldn't_ get > any easier! You just plug the cable to the PCs. That's it. > Being so simple means it's more stable also (less parts less things to > go wrong). There are only two drawback with them: they are useless > with anything more than 2 pcs and they look exactly like normal ones > (so you got to be extra cautious when picking). Lately I saw more and more NICs and switches with Auto MDIX, sometimes also called auto-crossover. As the name implys, with that hardware it doesn't really matter what cables you use. I made it a habit to look for those specifically, especially if there is no (or only minor) price difference. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
On Thu, Jan 18, 2007 at 04:36:28PM -0500, Evan wrote: > As a standard I always purchase red crossover cables. For me, this > eliminates the confusion. Many 100 Base-T and most? all? 1000 Base-T support MDI/X; ordinary cables will work to connect two network cards. http://www.iol.unh.edu/services/testing/ge/training/#Auto-Crossover_White_Paper I once bought some straight through cables that turned out to be crossover, and didn't notice until the cables were used for a non-ethernet application... -- Rob signature.asc Description: Digital signature
Re: local network with twisted rj45
As a standard I always purchase red crossover cables. For me, this eliminates the confusion. On 1/18/07, Nick Demou <[EMAIL PROTECTED]> wrote: 17 Jan 2007 19:35:08 -0800, christop <[EMAIL PROTECTED]>: > ... > Yes, but nothing is going through the line for now, and I would like > it to do something. Learning and understanding before > only buying more (if possible). > > Would it be different if it was straight with a switch? > > I would first like to ping with the devices I do have now. > > But if it is actualy harder to do it with twisted paires, networking two pcs with a twisted (crosslink ) cable _couldn't_ get any easier! You just plug the cable to the PCs. That's it. Being so simple means it's more stable also (less parts less things to go wrong). There are only two drawback with them: they are useless with anything more than 2 pcs and they look exactly like normal ones (so you got to be extra cautious when picking). Why then do people that do networking complain about them? Well the only reason is that when you use a lot of cables the fact that crosslink ones look just like normal ones means that sooner or later you will use the wrong type and you will spend some time until you notice the silly mistake. It's at this point that most people will through away the crosslink ones to save theirselves the trouble next time (and do the association crosslink = no no). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
re: local network with twisted rj45
17 Jan 2007 19:35:08 -0800, christop <[EMAIL PROTECTED]>: ... Yes, but nothing is going through the line for now, and I would like it to do something. Learning and understanding before only buying more (if possible). Would it be different if it was straight with a switch? I would first like to ping with the devices I do have now. But if it is actualy harder to do it with twisted paires, networking two pcs with a twisted (crosslink ) cable _couldn't_ get any easier! You just plug the cable to the PCs. That's it. Being so simple means it's more stable also (less parts less things to go wrong). There are only two drawback with them: they are useless with anything more than 2 pcs and they look exactly like normal ones (so you got to be extra cautious when picking). Why then do people that do networking complain about them? Well the only reason is that when you use a lot of cables the fact that crosslink ones look just like normal ones means that sooner or later you will use the wrong type and you will spend some time until you notice the silly mistake. It's at this point that most people will through away the crosslink ones to save theirselves the trouble next time (and do the association crosslink = no no). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
Russell L Harris writes: > The nice thing about a switch or hub is that (1) it allows you to > use common straight cables and Crossover cables can be easily purchased from any (good) electronics shop. > (2) it has an LED which gives you a visual indication of the amount > of traffic flowing. I cannot see how this can be an advantage over using a crossover cable in the context the OP is trying to use it. -- -- Jhair -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
My mistake. .0 is the network address. On 1/17/07, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote: I use a cross-over cable all the time between two computers. Then again, I have the cable. If you don't and you can't make one, then believe it or not an ethernet switch is often cheaper than a cross-over cable. I have in /etc/network/interfaces: computer 1: iface eth0 inet static address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 computer 2 is the same except for the address being 192.168.1.3 After you make the changes, on each computer: ifdown eth0 ifup eth0 Also put both computers in both computer's /etc/hosts 127.0.0.1 localhost 192.168.1.1 computer1 192.168.1.3 computer2 You should then be able to ping back and forth. Remember that 192.168.1.0 is the network itself. Read the debian-reference, and the relavent HOWTOs Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
I would first change the IP address so that one workstation does not have a broadcast address(.0) Try a simple scheme like .1 and .2. On 17 Jan 2007 19:40:48 -0800, christop <[EMAIL PROTECTED]> wrote: Michael D. Norwick a écrit : > christop wrote: > > I would need information on how to configure > > a local network between two computers > > with only a twested rj45. > > > > I have two ethernet cards on each of the two computers > > I aim to put together. > > > > > > > > > > > > < snip > > > http://www.aboutdebian.com/network.htm > I gave a glance, see it later, thanks. Ch. > michael > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
I use a cross-over cable all the time between two computers. Then again, I have the cable. If you don't and you can't make one, then believe it or not an ethernet switch is often cheaper than a cross-over cable. I have in /etc/network/interfaces: computer 1: iface eth0 inet static address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 computer 2 is the same except for the address being 192.168.1.3 After you make the changes, on each computer: ifdown eth0 ifup eth0 Also put both computers in both computer's /etc/hosts 127.0.0.1 localhost 192.168.1.1 computer1 192.168.1.3 computer2 You should then be able to ping back and forth. Remember that 192.168.1.0 is the network itself. Read the debian-reference, and the relavent HOWTOs Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
Michael D. Norwick a écrit : > christop wrote: > > I would need information on how to configure > > a local network between two computers > > with only a twested rj45. > > > > I have two ethernet cards on each of the two computers > > I aim to put together. > > > > > > > > > > > > < snip > > > http://www.aboutdebian.com/network.htm > I gave a glance, see it later, thanks. Ch. > michael > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
Russell L. Harris a écrit : > * Baron Christophe <[EMAIL PROTECTED]> [070117 20:56]: > > I would need information on how to configure a local network between > > two computers with only a twisted rj45. > > Why mess around with a special crossover cable? Ethernet switches Is it really more messy? I have no information about this. > have become so inexpensive that hardly anyone purchases an ethernet > hub, so you likely can find someone to give you a hub without charge. > And an ethernet switch (which can handle more traffic than can a hub) > can be purchased for US $5 to $10. > > The nice thing about a switch or hub is that (1) it allows you to use > common straight cables and (2) it has an LED which gives you a visual > indication of the amount of traffic flowing. > > RLH > Yes, but nothing is going through the line for now, and I would like it to do something. Learning and understanding before only buying more (if possible). Would it be different if it was straight with a switch? I would first like to ping with the devices I do have now. But if it is actualy harder to do it with twisted paires, I will do as you say. Until then I'll just wait for further information. And documentation. Ch.
Re: local network with twisted rj45
christop wrote: > I would need information on how to configure > a local network between two computers > with only a twested rj45. > > I have two ethernet cards on each of the two computers > I aim to put together. > > > > > < snip > http://www.aboutdebian.com/network.htm michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local network with twisted rj45
* Baron Christophe <[EMAIL PROTECTED]> [070117 20:56]: > I would need information on how to configure a local network between > two computers with only a twisted rj45. Why mess around with a special crossover cable? Ethernet switches have become so inexpensive that hardly anyone purchases an ethernet hub, so you likely can find someone to give you a hub without charge. And an ethernet switch (which can handle more traffic than can a hub) can be purchased for US $5 to $10. The nice thing about a switch or hub is that (1) it allows you to use common straight cables and (2) it has an LED which gives you a visual indication of the amount of traffic flowing. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
local network with twisted rj45
I would need information on how to configure a local network between two computers with only a twested rj45. I have two ethernet cards on each of the two computers I aim to put together. One of them is connected to a adsl via gateway. I want the others to be configured for the two computers to exchange files through ftp protocol. I did like this in my /etc/network/interfaces file: (only the part concerning the interfaces for this local network. The others are set in dhcp) #first computer allow-hotplug eth0 iface eth0 inet static address 192.168.10.0 netmask 255.255.255.0 auto eth0 #(2) second computer allow-hotplug eth0 iface eth0 inet static address 192.168.10.1 netmask 255.255.255.0 auto eth0 And then ifup -a. If I could do a ping it would be a first step. One the first computer it says: ~$ ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. >From 192.168.10.0 icmp_seq=1 Destination Host Unreachable >From 192.168.10.0 icmp_seq=2 Destination Host Unreachable --- 192.168.10.1 ping statistics --- 8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7000ms , pipe 3 And one the second it says: ~$ ping 192.168.10.0 Do you want to ping broadcast? Then -b And with -b: 100% lost. And from the first computer: ~$ ping 192.168.10.0 PING 192.168.10.0 (192.168.10.0) 56(84) bytes of data. 64 bytes from 192.168.10.0: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.10.0: icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from 192.168.10.0: icmp_seq=3 ttl=64 time=0.026 ms --- 192.168.10.0 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.026/0.029/0.033/0.005 ms Is it happy speaking with itself? The purpose of this post is to be given links, or even keywords that could lead me. Possibly reliable ones. Ch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
local network with twisted rj45
I would need information on how to configure a local network between two computers with only a twested rj45. I have two ethernet cards on each of the two computers I aim to put together. One of them is connected to a adsl via gateway. I want the others to be configured for the two computers to exchange files through ftp protocol. I did like this in my /etc/network/interfaces file: (only the part concerning the interfaces for this local network. The others are set in dhcp) #first computer allow-hotplug eth0 iface eth0 inet static address 192.168.10.0 netmask 255.255.255.0 auto eth0 #(2) second computer allow-hotplug eth0 iface eth0 inet static address 192.168.10.1 netmask 255.255.255.0 auto eth0 And then ifup -a. If I could do a ping it would be a first step. One the first computer it says: ~$ ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. >From 192.168.10.0 icmp_seq=1 Destination Host Unreachable >From 192.168.10.0 icmp_seq=2 Destination Host Unreachable --- 192.168.10.1 ping statistics --- 8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7000ms , pipe 3 And one the second it says: ~$ ping 192.168.10.0 Do you want to ping broadcast? Then -b And with -b: 100% lost. And from the first computer: ~$ ping 192.168.10.0 PING 192.168.10.0 (192.168.10.0) 56(84) bytes of data. 64 bytes from 192.168.10.0: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.10.0: icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from 192.168.10.0: icmp_seq=3 ttl=64 time=0.026 ms --- 192.168.10.0 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.026/0.029/0.033/0.005 ms Is it happy speaking with itself? The purpose of this post is to be given links, or even keywords that could lead me. Possibly reliable ones. Ch. ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
