Hi Ramesh
Could this be a problem with routing tables? You can check with the
route tool:
http://manpages.ubuntu.com/manpages/precise/man8/route.8.html
You should see eth1 as the only route for the 192.168.2.0 network
Cheers
Danny
Ramesh Karuppusamy <mailto:[email protected]>
July 14, 2014 at 9:24 AM
Hello list,
I have a weird situation with our setup - can someone help me solve
this issue?
Our head node has two network interfaces - the first on the institute
network and the interface eth1 is assigned 192.168.2.1.
I assigned a static IP of 192.168.2.100 to our ROACH2 and eth1 above
are connected to a simple D-Link unmanaged switch. From the head node,
I can ping ROACH2 or ‘telnet 192.168.2100 7147’ to connect to
tcpborphserver. But the katcp python client simply doesn't connect to
ROACH2, as it tries to use the first interface on the head node. Is it
possible to force katcp to use the eth1 (or ip 192.168.2.1) on the
head node?
Thanks!
Cheers,
Ramesh
