Oh god, after all the things I tried, it came down to setting the x permissions on the new tcpborphserver2 that I downloaded. Thank you all, Sam
On Wed, Aug 10, 2011 at 6:06 PM, Marc Welz <[email protected]> wrote: > Hi there > >> Cool, I dropped in this version, reducing its name to tcpborphserver2 >> (I did leave a copy of it with the original name as well). Now I can't >> connect via telnet, >> >> /home/observer/casper/tcpborphserver2-2010-04-02-tgtap >> >> I tried allowing the port through the firewall via the iptables route, >> but it claims there are no tables? > > The kernels on the roach are not built with IP tables enabled, so > there is no firewall to get in the way. > >> with the previous tcpborphserver I was able to connect. I am still >> able to ssh in as well. > > Ssh in, check that tcpborphserver is running. If not, start it > by hand. Maybe the new tcpborphserver isn't marked executable (chmod +x) ? > > Once you can connect to it (telnet roachIP 7147), issue the command > > ?progdev your-file.bof > > in the telnet sesion. (To see the available bof files, type ?listbof. > The bof files have to marked executable too... ) > > Then do a > > ?listdev > > to check if your registers are visible. > > regards > > marc >
