Hi Dave, Jonathon Kocz pointed out exactly this just a few minutes back. As I wrote to him - I do feel super silly now - two dumb mistakes with in a span of few days doesn’t make popular person, I suppose :)
Thanks to all for the timely response. Cheers, Ramesh On 14 Jul 2014, at 20:16, David MacMahon <[email protected]> wrote: > Hi, Ramesh, > > On Jul 14, 2014, at 10:59 AM, Ramesh Karuppusamy wrote: > >> root@majestix:~# netstat -nut >> Active Internet connections (w/o servers) >> Proto Recv-Q Send-Q Local Address Foreign Address State >> tcp 0 0 192.168.2.1:35475 192.168.2.100:7147 >> ESTABLISHED >> tcp 0 0 134.104.22.254:22 134.104.30.134:49237 >> ESTABLISHED >> tcp 0 1 134.104.22.254:42604 198.168.2.100:7147 SYN_SENT >> >> >> The first entry in the list is from ‘telnet 192.168.2.100 7147’ command, >> while the last is from katcp trying to connect to ROACH2. This times out >> after a minute or so. > > Look carefully at the destination IP address of the last line. It starts > with 198 instead of 192. > >> On 14 Jul 2014, at 18:07, David MacMahon <[email protected]> wrote: >> >>> Are you sure the katcp python client is using the correct IP? > > I guess the answer is "no"! :-) > > Dave >
