Dale wrote:
> Hi
>
> I have done this before.  Maybe something has changed because I can not
> get it to work now.  My main rig is called smoker.  The second rig is
> currently booted off the CD.  I plan to use my main rig to sync and get
> distfiles off of.  This is off smokers /etc/conf.d/net file:
>
>   
>> config_eth0=( "192.168.0.1 netmask 255.255.255.0 broadcast
>> 192.168.0.255" )
>>     
> More info from smoker:
>
>   
>> eth0      Link encap:Ethernet  HWaddr 00:01:53:81:00:E7
>>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:34 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:16458 (16.0 Kb)  TX bytes:5670 (5.5 Kb)
>>           Interrupt:10 Base address:0xc000
>>     
>
>   
>> [EMAIL PROTECTED] / # ping 192.168.0.2
>> PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
>> From 192.168.0.1 icmp_seq=1 Destination Host Unreachable
>> From 192.168.0.1 icmp_seq=2 Destination Host Unreachable
>> From 192.168.0.1 icmp_seq=3 Destination Host Unreachable
>>
>> --- 192.168.0.2 ping statistics ---
>> 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time
>> 4009ms
>> , pipe 3
>> [EMAIL PROTECTED] / #
>>     
>
> If it helps any, I see traffic going over the network in gkrellm.
>
>   
>> [EMAIL PROTECTED] / # route
>> Kernel IP routing table
>> Destination     Gateway         Genmask         Flags Metric Ref   
>> Use Iface
>> nas2.greenwood1 *               255.255.255.255 UH    0      0       
>> 0 ppp0
>> 192.168.0.0     *               255.255.255.0   U     0      0       
>> 0 eth0
>> loopback        *               255.0.0.0       U     0      0        0 lo
>> default         nas2.greenwood1 0.0.0.0         UG    0      0       
>> 0 ppp0
>> [EMAIL PROTECTED] / # 
>>     
> Yea, ppp0 would be that slow as crap dial-up connection I have.  < cries >
>   
>> [EMAIL PROTECTED] / # iptables -L
>> Chain INPUT (policy ACCEPT)
>> target     prot opt source               destination
>> ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:http
>> DROP       all  --  anywhere             anywhere            state
>> INVALID,NEW
>>
>> Chain FORWARD (policy ACCEPT)
>> target     prot opt source               destination
>> DROP       all  --  anywhere             anywhere            state
>> INVALID,NEW
>>
>> Chain OUTPUT (policy ACCEPT)
>> target     prot opt source               destination
>> [EMAIL PROTECTED] / #
>>     
>
> Now the info from the second rig is a bit hard to get.  I can't exactly
> copy and paste here.  Help me get this working and I'll copy and paste
> all you want.  LOL  Second rig is the same setup except it is set to
> address 192.168.0.2.  I did restart the network though, on both rigs.
>
> Route returns loopback and that is all.  Looks suspicious to me.  It
> doesn't have iptables installed on the CD.  I guess there are none.
>
> Oh, to test the cable, I set both to the same address.  When I tried to
> bring up the network, it gave me a error that the address was in use or
> something like that.  It saw it at least.
>
> Can someone tell me what I am doing wrong?  It has to be me.  It almost
> always is.
>
> Thanks for the help. 
>
> Dale
>
> :-)  :-)  :-)
>
>   

Hi, Dale

I suspect you don't have a proper module for your network card loaded
into the kernel. Is the interface of "rig-2" up? What does "ifconfig
eth0" say?

-- 
Best regards,
Daniel


-- 
[email protected] mailing list

Reply via email to