Re: Network configuration

[Raj Kiran Grandhi <grajkiran@gmail.com>]

Dan H wrote:
> Hello folks,
>
> I'm trying to control an external instrument via Ethernet. I've installed an additional networking card in my Debian box and connected the thing via a crossover cable.
>
> NOTE: I've booted Windows on the same machine and was able to talk to the instrument using a supplied demo program (LabView). So, physically the connection is correct, but when I try tp PING the instrument from within Linux, I get no reply.
>
> I don't really know where to start all this, so I'd like to know if at least my network settings are correct. I've set the address of the secondary interface to 192.168.0.1, the instrument has 192.168.0.2. Does my box automatically know to use the other card when I try to connect to an 192.168.... address?
>
> Thanks,
> --D.
>
> Here's the output of ifconfig. What does "Link encap:UNSPEC" mean? Is that a problem?
>
> eth0      Link encap:UNSPEC  HWaddr 00-00-10-DC-00-38-3E-C6-00-00-00-00-00-00-00-00  
>           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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> eth1      Link encap:Ethernet  HWaddr 00:0C:76:54:FE:B1  
>          .....
>          (my "outside" network connection)
>          .........

Please post your /etc/network/interfaces and the output of "route -n"

Does your outside network share the same network number? I think if you 
define a static route to your device through eth0, you may be able to 
access it. For eg:

# route add 192.168.0.2 dev eth0

--
Raj Kiran Grandhi