Start A Network Connection From The Command Line

[BarrySamuels]

I take it there is no log of dhcpcd's progress?

Good guess.  

Look for logs in /tmp/ and in /var/log/ when you are actually online with kismet.

The only relevant logs appear to be for Kismet and that's only wireless network information.

Please paste in your results...whether you meant "shows the details for /bin/ps" or "shows a symlink pointing to /bin/ps" is not clear without me eyeballing your output.

-rwxrwxr-x   1  root  root  89312  Apr 5  2005  /bin/ps

I don't know what Skype does.

You what? I thought everybody knew of Skype. It's one of those Internet telephone type thingies - if I might use the technical term - talk to someone on the other side of the world for free.  

I'll try and get round to providing what other information I can a little later on.

[sdjf]

I confess I'd heard of Skype but it wasn't something I committed to memory...things get filed in my brain according to importance and must have run out of room.

Your ls of ps looks perfect...when you can, give me an md5sum...I'm wondering if we have the same file...my ls looks similar:

-rwxrwxr-x    1 root     root         89312 Apr 12 17:00 /bin/ps

602103a27e13b84221a56532d27f8ecb  /bin/ps

[sdjf]

Hey, I just found instructions for how to enable the log for dhcpcd in, of all places, the man page!

To catch dhcpcd debugging output add the
 following line to /etc/syslog.conf file:
    local0.*     /var/log/dhcpcd.log
 and then refresh syslogd daemon:
     kill -1 `cat /var/run/syslogd.pid`

It should help in debugging networking problems.

sdjf

[sdjf]

Barry and I have ripped copies of "ps" off of our Sharp ROMs, so that those of you wanting to use a more fully-featured ps who only have the BusyBox versions, can install a better version.

I have written up installation instructions, and also given examples of how much more efficient script-writing can be when using it, at:

http://www.sdjf.esmartdesign.com/commands/ps.html

Unlike the BusyBox ps, it shows you what tty each process is using, unless that information is hidden from ps.  And can sometimes provide additional help in identifying processes that may be interfering with getting online.

sdjf

[BarrySamuels]

Hey, I just found instructions for how to enable the log for dhcpcd in, of all places, the man page!

I have only just realised something ( I am slow sometimes    ) I can't enable logging for my dhcp server 'cause I'm using the one in my router.  

Your ls of ps looks perfect...when you can, give me an md5sum...I'm wondering if we have the same file...my ls looks similar:

-rwxrwxr-x 1 root root 89312 Apr 12 17:00 /bin/ps

602103a27e13b84221a56532d27f8ecb  ps

[sdjf]

Oh dear.   I do not understand.  The one in your router?  Does that mean that dhcpcd is not on your zaurus?  Then how come it shows in the ps listing on the Z? [EDIT:  it's logging on the dhcpcd client side I am talking about, not the server side, although I suppose that could be helpful, but isn't necessary.]

I actually started another topic yesterday specifically asking for info on dhcpcd logs:

https://www.oesf.org/forums/index.php?showtopic=23784

This is above my head at this point.  Ugh.

Maybe we should move the log issue to that thread.  I did ask for some more info there that'd be helpful.

There's gotta be some way to log what's happening with dhcpcd and the router or whatever, or how can anybody do any debugging?  Yikes!!

Also, your ps is obviously  the same as mine...and Antikx tried it out on his C1000 with a pdaXii rom and it seemed okay, so it looks like it's pretty generic...thank you.

sdjf

EDIT:  Here's another thought.  Can you post your file that qtopia uses as a cfg file for your connection (of course garbling any sensitive or passwd info)?  I think it was:

/home/root/Applications/Network/modules/WLAN0.conf

[sdjf]

Barry,
One of the reasons I am so insistent about a dhcpcd log is that, at least for pppd logs, the presence or absence of that log is an important clue about whether it is appropriate to use qstop http://www.sdjf.esmartdesign.com/scripts/qstop.html and cardctl commands.  If your kismet script checks that, and there is no log even though dhcpcd is not supposed to be running, you're gonna know something is definitely wrong, that some process has erased the log without actually running.  At least that's my hunch.

So, hope to see you at the "dhcpcd logs" thread for any questions on implementing the log. https://www.oesf.org/forums/index.php?showtopic=23784

I haven't yet written up the final details, but did find out how to fix /etc/pcmcia/network and /etc/pcmcia/network.opts to implement debugging.  Progress!

sdjf