Jim Roland wrote: > Have you used ifconfig? The card will not be "up" until you do a > ifconfig eth0 (ip address) > or for aliasing > ifconfig eth0:(alias) (ip address) > > i.e. ifconfig eth0 192.168.0.1 > > In a simple example, you do not necessarily need netmask and gateway > arguments for ifconfig. Your card will not be network aware until you > have added an IP address to it. The "lo" interface is for local loopback, > and will do nothing for your network. If your command outputs, there is > nothing on eth0 except for your network. Run an ifconfig without > parameters and it will tell you what interfaces are setup. If your > network card is not listed, then it is not setup. > > To tell you the truth, I have never used arp, therefore I have never seen > it necessary. I did run the arp -a on my system just a few minutes ago, > and it reflects the non-aliased other pcs on my network. Therefore, > ifconfig setup them for me. > > What I would do if you are running slackware or another dist that has the > netconfig command available to root, is run that and it will setup your > rc.d scripts for you. Reboot and it should be working. If not, manually > add the ifconfig command to the same script that your route (network) > command is in. > > ------------------------------------------------------- > Jim Roland, President > Roland Internet Services, "The host with the most" > Offering premier web, email and CGI custom programming. > Ask us about Frontpage98 Extensions! > http://www.roland.net/ [EMAIL PROTECTED] > ------------------------------------------------------- > > On Sat, 28 Nov 1998, mail wrote: > > > Date: Sat, 28 Nov 1998 18:25:55 -0500 > > From: mail <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Help please!!! Network problem; routing? or ??? > > > > Well, after about 40 hours of playing with this, I confess. I don't know > > jack about network routing. > > > > I am setting up a 2 pc network (so far). The problem is that neither PC can > > see each other, yet data "appears" to be passing to the hub. The second > > issue may be related to the first, but "arp" is showing me the the hardware > > address is not being assigned. > > > > I have debugged all of the hardware issues and don't believe there is > > anything wrong there. > > > > My server PC is set to 192.168.1.1, my second pc is 192.168.1.2 > > /etc/host file is: > > > > 192.168.1.1 pc1.mydomain.com mine > > 192.168.1.2 pc2.mydomain.com yours > > 192.168.1.3 pc3.mydomain.com theirs. > > > > /etc/networks file is: > > localhost 127.0.0 > > mydomain.com 192.168.0 > > > > > > I have DNS up and running just fine ( or so I believe. :) ) > > > > When I set my route as: > > > > ifconfig lo 127.0.0.1 > > route add 127.0.0.1 > > route add -net 192.168.1.0 netmask 255.255.255.0 eth0 > > route add default gw 192.168.1.1 > > > > At this time, I issue a 'netstat -rn' ( oops, may have been 'route') > > my route table looks incorrect. It is: > > > > Destination Gateway netmask > > metrics iface > > 192.168.1.0 * 255.255.255.0 > > U 0 eth0 > > loopback * 255.0.0.0 > > U 0 lo > > default * > > 255.255.255.255 U 0 eth0 > > > > > > DOES THIS LOOK CORRECT? > > > > I have run tcpdump and captured the output, but again, I'm not very familiar > > with it: > > 22:00:01.427518 pc1.mydoman.com > pc2.mydomain.com icmp: echo request > > 22:00:02.427518 pc1.mydoman.com > pc2.mydomain.com icmp: echo request > > 22:00:03.427518 pc1.mydoman.com > pc2.mydomain.com icmp: echo request > > and on and on. > > > > I have tried using different netmasks with my default route, none help. To > > me, it appears that the data is > > being transmitted to my network, but neither end can see each other. No, I > > have not touched the /etc/services nor the /etc/protocol files from the > > Linux Redhat 5.1 installation. > > > > > > My Second issue: #2. When I inquire into the arp table, the second PC > > which I am > > attempting to ping shows the PCs address, but no hardware address associated > > with it. I can remap the arp entry (arp -s test 00:11:22:22:33 ...) to my > > ethernet card, but I still can not ping my second box. ( yes, all of the > > blinky blinky's are going off on the back of the ethernet card and my hub. > > > > >From the second PC, not surprising, I can not ping my server. Again, the > > cards in both PCs tell me something is going on, as well as the hub. > > > > > > Thank you all very much in advance. And please, don't tell me to read of > > DNS & BIND, nor TCP/IP nor Linux Administrators book one more time. :) What > > I really would like to see is what the FULL output of the following commands > > SHOULD look like. > > > > netstat -rn > > arp > > cat /proc/net/arp > > tcpdump -c 10 (only 10 lines of a ping please. ) > > > > Thanks again. > > > > > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-net" in > > the body of a message to [EMAIL PROTECTED] > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to [EMAIL PROTECTED] OOPS!!! Well, I don't know the exact problem, but it was not Linux. My other box, Gulp, I forget to say, or was to embarrased to admit, was a Windows 95 box. Whatever it was spitting out over my network, it wasn't recognized. After reinstalling drivers,etc. everything is working fine. Thanks everyone for you help. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
