| Home | Register | Members | Search | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
will 18 wrote:
> Evening all... clueless newbie seeks help... > I have 2 linux boxes I wish to connect as a LAN: the 'ping' output from > either box produces 'dest. host unreachable'. I am missing something > fundamental but don't know what. It seems to me that packets are being > TX'd and RX'd but the respective hosts don't recognise them (hardware > seems ok). After 3 weeks grief, RTFM (several) and lurking here I'm still > none the wiser. Perhaps less so. Apologies for the verbose post, but I > hoped to avoid having to re-post with details. > > Box A > opaline: Slackware 8.0 / 2.4.19 This is old.. way old. Still, no reason why it won't do IP. > /etc/hosts: > 127.0.0.1 localhost > 192.168.0.2 opaline.nonesuch.net opaline > 192.168.0.3 vulcan.nonesuch.net vulcan Good. > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > nonesuch.net * 255.255.255.0 U 0 0 0 eth0 > loopback * 255.0.0.0 U 0 0 0 lo You have no default route set, but in itself, this is not a problem. > /sbin/ifconfig (pre-ping): > eth0 Link encap:Ethernet HWaddr 00:00:C0:69:81:64 > inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:3 Base address:0x250 Memory:cc000-d0000 Looks good. > /sbin/ifconfig (after 'ping vulcan'): > eth0 Link encap:Ethernet HWaddr 00:00:C0:69:81:64 > inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:360 (360.0 b) Well, at least it tried  > /sbin/ifconfig (post-ping from vulcan): > eth0 Link encap:Ethernet HWaddr 00:00:C0:69:81:64 > inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:6 dropped:0 overruns:0 frame:0 And this failed - that's a definite Clue(tm) > Box B > vulcan: Slackware 10.2 / 2.4.32 > /sbin/ifconfig (post-ping from opaline): > eth0 Link encap:Ethernet HWaddr 00:15:F2:C3:BB:0E > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 3 packets received! You must be beside yourself... > I would be very grateful if anyone could tell me where I'm going wrong. Have you tried swapping out the NIC from box B with one that's known to work ? It looks like it's broken... In the first case, it doesn't return any packets, and in the second, box A receives them as errors. Also check the cable between them, since the wires from B to A may be faulty (intermittent errors tend to be more a result of cabling than hardware issues.) J. |
|
|
|
|
|||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
Moe Trin <(E-Mail Removed)> wrote:
> Newsgroups: comp.os.linux.networking > > On Sun, 15 Oct 2006, in the Usenet newsgroup comp.os.linux.networking, in > article <(E-Mail Removed)>, will 18 wrote: > <snip> >>opaline: Slackware 8.0 / 2.4.19 > > Ancient - consider replacing it. > Box is heading for retirement, but has my only net connection for now and years' worth of installed sound software and noises... replicating my req'd environment on Box B will take time. The OS actually started as Slackware '96 so has had a few upgrades > > Minor - please don't grab domain names out of mid-air. A domain-squatter > actually has registered 'nonesuch.net' > Woops - sorry - didn't think. Should I do a 'whois' on a proposed name for it or is there some recognised method ob deriving one? > <snip> > Oh, boy. Care to enlighten us as to which antique that is? Box A (Slack 8.0) wd.c:v1.10 9/23/94 Donald Becker ((E-Mail Removed)) eth0: WD80x3 at 0x240, 00 00 C0 69 81 64 WD8013, IRQ3, shared memory at 0xcc000-0xcffff I presumed this is the card referred to in the ethernet HOWTO, SMC/WD8013 in fact as I recall it's the same as the example they quote 'SMC/WD8013-EWC' - I looked for the FCC ID to try to identify it as per instructions and was surprised to find it the same. S'pose it was common at the time. <snip> > > Which one? Look at /var/log/messages and see what it says about this card > during boot. Pay attention to the mode and speed. Do the same on the other > system. via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xa000, 00:15:f2:c3:bb:0e, IRQ 23. eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link 0000. after this, interestingly, Oct 17 00:53:52 vulcan logger: /etc/rc.d/rc.inet1: eth0 is already up, skipping I don't know what's bringing the interface up, but my config info is in the /etc/rc.rc.inet1.conf read by rc.inet1. I'm using '/sbin/modprobe via-rhine' in /etc/rc.d/rc.modules to bring the card up, so 1) is this what's bringing eth0 up and 2) is it ignoring my rc.inet1 config? This has (for eth0) IPADDR[0]="192.168.0.3" NETMASK[0]="255.255.255.0" Can't find anything regarding modes or speeds. > > Not quite enough details. Which cards? How connected? > Hope I've given enough info on cards. Boxes connected with standard LAN cables with the phone-connector-type plugs (don't know what they're called) via a Mercury 5-port switch, box says 'kobian.com' and little else. Sorry for the delay, not used ngs, already failed to reply once, hope this appears; learning (slowly, sigh). > Old guy -- Will 18 GNU horizons with Linux |
|
|
|
|
|||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
will 18 wrote:
> Jeroen Geilman <(E-Mail Removed)> wrote: >> Have you tried swapping out the NIC from box B with one that's known to >> work ? >> It looks like it's broken... >> > Seems I've misread the signals. Obviously now the errors are reported at > NIC level so it's a h/w problem not s/ware config (although I can't yet > rule that out!). Yes, you can. Unless the cards aren't recognised or supported by your Linux kernel - and they obviously are, since you have working interfaces. Any problems with Tx or Rx would still be related to NIC hardware. > <snip> >> Also check the cable between them, > <snip> > Unlikely. Irrelevant It. may. be. the. cause. I've seen it happen more than I care to remember - after a time you learn to check this one *early*... since it is easy to check. > Thank you for taking time to interpret my post; I was unsure of how to > interpret the ping results. No problem; the trick is visualising what happens to Ethernet traffic - both on the wire and in your PC. In this case, it was fairly obvious that since box A was sending okay and receiving *some* of the packets from B, it was box B that has problems with sending packets. J. |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| hosts file | McHenry | Linux Networking | 2 | 06-08-2006 08:03 PM |
| hosts.deny and hosts.allow problem | dan | Linux Networking | 3 | 06-15-2005 07:26 PM |
| /etc/hosts used only sometimes | graeme.pietersz@gmail.com | Linux Networking | 2 | 03-09-2005 06:28 AM |
| Many Hosts via few Modems | Walter Harms | Linux Networking | 5 | 01-20-2004 12:05 PM |
| hosts | JW | Linux Networking | 1 | 12-20-2003 02:22 PM |
Linear Mode
