-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, I am setting a mini network using two PC's both fitted with 3Com 3c509 ISA ethernet cards attached via a null modem. bsod is a bog standard SuSE 7.0 box and tcob1 is a 2.2.20 box with 3c509 module compiled. I installed, rebooted and checked the config, everything looks okay except that I am getting a no route to host error. tcob1 is 192.168.0.1 bsod is 192.168.0.2 in both boxes eth0 is set to 3c509 (ips as above). Ifconfig showes (on tcob1): eth0 Link encap:Ethernet HWaddr 00:60:8C:CF:3C:BF inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::260:8cff:fecf:3cbf/10 Scope:Link inet6 addr: fe80::60:8ccf:3cbf/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:78 errors:0 dropped:0 overruns:0 frame:0 TX packets:723 errors:0 dropped:0 overruns:0 carrier:86 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x300 Route showes: 194.165.0.2 0.0.0.0 255.255.255.255 UH 1 0 0 tap0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 0 tap0 I am totally lost as to what maybe wrong. tcob1 is the dialup box and I want to use bsod as the work horse :) Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyg2n4ACgkQeR/L2ZZp3E+h9gCeJhgZKewFYCXyXuhh0cUMbqjF +mMAoKuY3/gwz7GmI+xyj7g9O1D1WywI =CmDf -----END PGP SIGNATURE-----
sean-dated-1017606681.1fc340@tcob1.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
I am setting a mini network using two PC's both fitted with 3Com 3c509 ISA ethernet cards attached via a null modem. bsod is a bog standard SuSE 7.0 box and tcob1 is a 2.2.20 box with 3c509 module compiled.
I installed, rebooted and checked the config, everything looks okay except that I am getting a no route to host error.
tcob1 is 192.168.0.1 bsod is 192.168.0.2
in both boxes eth0 is set to 3c509 (ips as above). Ifconfig showes (on tcob1): eth0 Link encap:Ethernet HWaddr 00:60:8C:CF:3C:BF inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
Route showes: 194.165.0.2 0.0.0.0 255.255.255.255 UH 1 0 0 tap0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 0 tap0
I am totally lost as to what maybe wrong. tcob1 is the dialup box and I want to use bsod as the work horse :)
Sean
This has me confused because it sounds like you are saying you have a null modem cable between two ethernet cards. What I assume you want to do is get the 2 computers talking through eth0. On which computer do you get the route to host error? Post the route table for bsod as well. This route seems to be correct to connect your internal lan through eth0 and using tap0 as default route although you could stand to add the gateway to your default route (assming 194.165.0.2 as the gateway). Can you get to the net through tcob1 as is? JHS
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi John!
I am setting a mini network using two PC's both fitted with 3Com 3c509 ISA ethernet cards attached via a null modem. bsod is a bog standard SuSE 7.0 box and tcob1 is a 2.2.20 box with 3c509 module compiled.
I installed, rebooted and checked the config, everything looks okay except that I am getting a no route to host error.
tcob1 is 192.168.0.1 bsod is 192.168.0.2
in both boxes eth0 is set to 3c509 (ips as above). Ifconfig showes (on tcob1): eth0 Link encap:Ethernet HWaddr 00:60:8C:CF:3C:BF inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
Route showes: 194.165.0.2 0.0.0.0 255.255.255.255 UH 1 0 0 tap0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 0 tap0
I am totally lost as to what maybe wrong. tcob1 is the dialup box and I want to use bsod as the work horse :)
Sean
This has me confused because it sounds like you are saying you have a null modem cable between two ethernet cards. What I assume you want to do is get the 2 computers talking through eth0. On which computer do you get the route to host error? Post the route table for bsod as well. This route seems to be correct to connect your internal lan through eth0 and using tap0 as default route although you could stand to add the gateway to your default route (assming 194.165.0.2 as the gateway). Can you get to the net through tcob1 as is?
Yeah, at the moment it is a null eth cable so that I can just get the two talking, once I have this done, I want to get a decent hub and link the rest. Both machines give a no route to host which makes me wonder if the cable is faulty. I can get through to the inet okay on tcob1 (this pc), I have had ethernet lans before but never this problem. Maybe I need to invest in a new null ether RJ45 cable :) Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyhkOIACgkQeR/L2ZZp3E/nOwCdFn04qPq/+U8T4WJx9JrmlQwr 23MAnA9ftxDqvD7ZlCR13oQih9Kes7ZK =RRCx -----END PGP SIGNATURE-----
networking problems are difficult to solve because there are many unknowns. Assuming that both 3com cards are working and your crossover cable it good, see if you can ping the other machine using the IP address. If you can successfully ping one machine from the other, then the issue is more of a routing /gateway issue. Your routing table in bsod should look like this. Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0 Your ifconfig does indicate that you have sent packets successfully other eth0. On 27 Mar 2002 at 9:29, Sean Rima wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi John!
I am setting a mini network using two PC's both fitted with 3Com 3c509 ISA ethernet cards attached via a null modem. bsod is a bog standard SuSE 7.0 box and tcob1 is a 2.2.20 box with 3c509 module compiled.
I installed, rebooted and checked the config, everything looks okay except that I am getting a no route to host error.
tcob1 is 192.168.0.1 bsod is 192.168.0.2
in both boxes eth0 is set to 3c509 (ips as above). Ifconfig showes (on tcob1): eth0 Link encap:Ethernet HWaddr 00:60:8C:CF:3C:BF inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
Route showes: 194.165.0.2 0.0.0.0 255.255.255.255 UH 1 0 0 tap0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 0 tap0
I am totally lost as to what maybe wrong. tcob1 is the dialup box and I want to use bsod as the work horse :)
Sean
This has me confused because it sounds like you are saying you have a null modem cable between two ethernet cards. What I assume you want to do is get the 2 computers talking through eth0. On which computer do you get the route to host error? Post the route table for bsod as well. This route seems to be correct to connect your internal lan through eth0 and using tap0 as default route although you could stand to add the gateway to your default route (assming 194.165.0.2 as the gateway). Can you get to the net through tcob1 as is?
Yeah, at the moment it is a null eth cable so that I can just get the two talking, once I have this done, I want to get a decent hub and link the rest.
Both machines give a no route to host which makes me wonder if the cable is faulty. I can get through to the inet okay on tcob1 (this pc), I have had ethernet lans before but never this problem. Maybe I need to invest in a new null ether RJ45 cable :)
Sean
- -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjyhkOIACgkQeR/L2ZZp3E/nOwCdFn04qPq/+U8T4WJx9JrmlQwr 23MAnA9ftxDqvD7ZlCR13oQih9Kes7ZK =RRCx -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jerry! On Wed, 27 Mar 2002, Jerry Feldman wrote:
networking problems are difficult to solve because there are many unknowns. Assuming that both 3com cards are working and your crossover cable it good, see if you can ping the other machine using the IP address. If you can successfully ping one machine from the other, then the issue is more of a routing /gateway issue. Your routing table in bsod should look like this. Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0
Your ifconfig does indicate that you have sent packets successfully other eth0.
I will have to do some more testing but pinging from each box results in all packets being lost. I will boot bsod up again (it has a very noisy fan) and do some work on the routing and see if that helps. Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyiFcsACgkQeR/L2ZZp3E/WuACfWk0kQ7kpXlG8ibUFP5puXMMD gFsAoIvzcAtPNsnKiSjbAus6HMoHI3YF =NDwZ -----END PGP SIGNATURE-----
Ok. BTW: On Linux you can change virtually everything without the need for a reboot. I think you need to verify first that your 2 network cards are working. Then, that your crossover cable works. Most of the network cards I have used recently are Linksys or Netgear. You also need to make sure that you have the correct drivers set up for the network cards. In the past, I've had some interesting experiences with some of the 3Com cards. On 27 Mar 2002 at 18:56, Sean Rima wrote:
I will have to do some more testing but pinging from each box results in all packets being lost. I will boot bsod up again (it has a very noisy fan) and do some work on the routing and see if that helps.
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jerry! On Wed, 27 Mar 2002, Jerry Feldman wrote:
Ok. BTW: On Linux you can change virtually everything without the need for a reboot. I think you need to verify first that your 2 network cards are working. Then, that your crossover cable works. Most of the network cards I have used recently are Linksys or Netgear. You also need to make sure that you have the correct drivers set up for the network cards. In the past, I've had some interesting experiences with some of the 3Com cards.
I have been using SuSe since 6.0. I hardly ever reboot, the only reboots around here are caused by power outages :) Console 10 does show the 3Com ethernet card as being in AIU (AUI) mode which I believe is RJ45. I had to make a freedos floppy copy the dos utils over and boot into freedos to sort any settings out :) Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyiHbQACgkQeR/L2ZZp3E+LqQCfcnJUicYYadZXAG0fAxECRidm XIkAn1+c1r0xIvLrTXXw81EAofOjnSSe =ukz1 -----END PGP SIGNATURE-----
AUI is not RJ45. AUI is the older thick wire Ethernet. BNC (or 10base2) is coax, and 10BaseT is RJ45. As I mentioned, it has been a while since I configured a 3Com. Some of their cards autoconfigure nicely, others you need to use their software to configure. My linksys 10/100 card popped in and was recognized as a Tulip card. Have zero problems. I originally had to download the driver from Donald Becker's site. On 27 Mar 2002 at 19:29, Sean Rima wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Jerry!
On Wed, 27 Mar 2002, Jerry Feldman wrote:
Ok. BTW: On Linux you can change virtually everything without the need for a reboot. I think you need to verify first that your 2 network cards are working. Then, that your crossover cable works. Most of the network cards I have used recently are Linksys or Netgear. You also need to make sure that you have the correct drivers set up for the network cards. In the past, I've had some interesting experiences with some of the 3Com cards.
I have been using SuSe since 6.0. I hardly ever reboot, the only reboots around here are caused by power outages :) Console 10 does show the 3Com ethernet card as being in AIU (AUI) mode which I believe is RJ45. I had to make a freedos floppy copy the dos utils over and boot into freedos to sort any settings out :)
Sean
- -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjyiHbQACgkQeR/L2ZZp3E+LqQCfcnJUicYYadZXAG0fAxECRidm XIkAn1+c1r0xIvLrTXXw81EAofOjnSSe =ukz1 -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
Hi I have found with some 3com cards, that I need to force the write to another, false, setup, and then force writing the correct setup, and then do a power-off deep boot, and only then I had life in those cards... This usually happened after I booted to M$... M$ does some weird stuff to those cards, and resetting them to use 10-base-T (RJ-45 cable) did required the above.... Jaska. Viestissä Keskiviikko 27. Maaliskuuta 2002 22:45, Jerry Feldman kirjoitti:
AUI is not RJ45. AUI is the older thick wire Ethernet. BNC (or 10base2) is coax, and 10BaseT is RJ45. As I mentioned, it has been a while since I configured a 3Com. Some of their cards autoconfigure nicely, others you need to use their software to configure. My linksys 10/100 card popped in and was recognized as a Tulip card. Have zero problems. I originally had to download the driver from Donald Becker's site.
On 27 Mar 2002 at 19:29, Sean Rima wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Jerry!
On Wed, 27 Mar 2002, Jerry Feldman wrote:
Ok. BTW: On Linux you can change virtually everything without the need for a reboot. I think you need to verify first that your 2 network cards are working. Then, that your crossover cable works. Most of the network cards I have used recently are Linksys or Netgear. You also need to make sure that you have the correct drivers set up for the network cards. In the past, I've had some interesting experiences with some of the 3Com cards.
I have been using SuSe since 6.0. I hardly ever reboot, the only reboots around here are caused by power outages :) Console 10 does show the 3Com ethernet card as being in AIU (AUI) mode which I believe is RJ45. I had to make a freedos floppy copy the dos utils over and boot into freedos to sort any settings out :)
Sean
- -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjyiHbQACgkQeR/L2ZZp3E+LqQCfcnJUicYYadZXAG0fAxECRidm XIkAn1+c1r0xIvLrTXXw81EAofOjnSSe =ukz1 -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
The problem with the 3Com cards are that there are so many different models and configurations as well as drivers... I have one in my daughter's PC, and did use it once to trouble shoot a problem. I worked for a company that was deploying Debian and Solaris based platforms with 3Com cards. Not one of the worked OOB. Once we got them configured and tested, they worked fine. On 27 Mar 2002 at 22:52, jaakko tamminen wrote:
Hi
I have found with some 3com cards, that I need to force the write to another, false, setup, and then force writing the correct setup, and then do a power-off deep boot, and only then I had life in those cards...
This usually happened after I booted to M$... M$ does some weird stuff to those cards, and resetting them to use 10-base-T (RJ-45 cable) did required the above....
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
Refresh my memory, this is an old ISA PNP-Combo card, right? I think you need to boot to dos and run the setup program to reprogram the EPROM (probably available from 3com's driver download). Make sure that PNP is turned OFF and set the interface manually to 10baseT, or whatever's appropriate. That should be it, really. I'd power down my system and check the settings, but I'm at work. And besides, it's the gateway to my cable modem and two internal segments (yes two), one 10baseT and one 10base2 for my ancient MicroVAX. ;) It's been running SuSE 6.3 faithfully without a crash (with the exception of a few power outages and a single disk crash) for several years. Just because the distribution has no support doesn't mean it's broken. Good luck, -- John Ross Hunt
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jerry! On Wed, 27 Mar 2002, Jerry Feldman wrote:
AUI is not RJ45. AUI is the older thick wire Ethernet. BNC (or 10base2) is coax, and 10BaseT is RJ45. As I mentioned, it has been a while since I configured a 3Com. Some of their cards autoconfigure nicely, others you need to use their software to configure. My linksys 10/100 card popped in and was recognized as a Tulip card. Have zero problems. I originally had to download the driver from Donald Becker's site.
I need to reboot this PC and stick the floppy in and reconfigure the card and will see what happens, no wonder there was no route to host :) Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyiOxwACgkQeR/L2ZZp3E8jEQCfc/BFmTAYPAdmVR9baSUSxfi4 rKMAoMrOrVMKgIYcuD6R8Z7yLpsGM6lq =mPjD -----END PGP SIGNATURE-----
That is why I don't buy 3Com cards. Most are very good and stable once you get them set up. On 27 Mar 2002 at 21:35, Sean Rima wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Jerry!
On Wed, 27 Mar 2002, Jerry Feldman wrote:
AUI is not RJ45. AUI is the older thick wire Ethernet. BNC (or 10base2) is coax, and 10BaseT is RJ45. As I mentioned, it has been a while since I configured a 3Com. Some of their cards autoconfigure nicely, others you need to use their software to configure. My linksys 10/100 card popped in and was recognized as a Tulip card. Have zero problems. I originally had to download the driver from Donald Becker's site.
I need to reboot this PC and stick the floppy in and reconfigure the card and will see what happens, no wonder there was no route to host :)
Sean
- -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjyiOxwACgkQeR/L2ZZp3E8jEQCfc/BFmTAYPAdmVR9baSUSxfi4 rKMAoMrOrVMKgIYcuD6R8Z7yLpsGM6lq =mPjD -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jerry! On Wed, 27 Mar 2002, Jerry Feldman wrote:
That is why I don't buy 3Com cards. Most are very good and stable once you get them set up.
Thanks for all the help, I sorted the problem, by mistake I hit aut config in the 3Com dos tools and found that there was an IRQ conflict that was not showing up anywhere else :( I reconfigured the card in bsod (This is an old NT machine hence the name) and hey presto it works. I cannot complain as I got half a dozen free :) Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: tcobone@jabber.org THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyiSoQACgkQeR/L2ZZp3E8GOwCg4ozZjES+eBRr9Hl7zSn3jZrF yT0AnR8XRkKXEldcitqqBca/c9tKqFqF =X91o -----END PGP SIGNATURE-----
participants (10)
-
jaakko tamminen -
Jerry Feldman -
John Ross Hunt -
John Scott -
Sean Rima -
Sean Rima -
Sean Rima -
Sean Rima -
Sean Rima -
Sean Rima