* Ishwar Rattan ishwar@pali.cps.cmich.edu [20050519 17:15]:
How do I start a dhcp client?
What's the problem?
Just run:
# dhclient -i $DEVICE
or
# pump
For detected network cards a dhcp client is started automatically (except when booting via cheatcode option nodhcp).
regards, -mika-
* Michael Prokop mika@grml.org [2005-05-19 19:10]:
How do I start a dhcp client?
Just run: # dhclient -i $DEVICE or # pump
Well, you muddled the two programs: Either use
# pump -i interface or # dhclient interface
Julius
* Julius Plenz jp@cvmx.de [20050520 17:47]:
- Michael Prokop mika@grml.org [2005-05-19 19:10]:
How do I start a dhcp client?
Just run: # dhclient -i $DEVICE or # pump
Well, you muddled the two programs: Either use
# pump -i interface or # dhclient interface
*d'oh* Sure, thanks for correcting. :)
regards, -mika-
How do I establish a dialup connection in grml 0.3? I config'ed wvdial and tried to start it but but I get "/dev/ttyS0 not recognized". My modem works on other linux partitions and is on ttyS0. It is in the directory in grml under /etc/dev. Thanks for the help. Let me know if you need more details. Jeff
Hello JeffM,
* JeffM. mojaveplan@icehouse.net [2005-05-20 18:23]:
How do I establish a dialup connection in grml 0.3? I config'ed wvdial and tried to start it but but I get "/dev/ttyS0 not recognized". My modem works on other linux partitions and is on ttyS0. It is in the directory in grml under /etc/dev. Thanks for the help. Let me know if you need more details. Jeff
What does wvdialconf say? Regards Nico
I finally figured out what I was doing wrong. wvdialconf said: 'sorry can't find your modem' the wvdial.conf file i wrote had modem set to /dev/ttyS0, but, actually, no such device was listed in /dev. So I did ./MAKEDEV /ttyS0 which was wrong. 'don't know how to make /ttyS0' error returned. Then tried ./MAKEDEV ttyS0 and it worked. Then I did setserial -a /dev/ttyS0. Then wvdial works. I come from a Slackware/KDE environment and not familiar with these issues.
One question still: Isn't there a way to get back to a command line prompt once wvdial gets you connected without going to another virtual console??
Thanks for the help and pointing me in the right direction of where to start.
On Friday 20 May 2005 16:27, Nico Golde wrote:
Hello JeffM,
- JeffM. mojaveplan@icehouse.net [2005-05-20 18:23]:
How do I establish a dialup connection in grml 0.3? I config'ed wvdial and tried to start it but but I get "/dev/ttyS0 not recognized". My modem works on other linux partitions and is on ttyS0. It is in the directory in grml under /etc/dev. Thanks for the help. Let me know if you need more details. Jeff
What does wvdialconf say? Regards Nico
Hello JeffM,
* JeffM. mojaveplan@icehouse.net [2005-05-20 21:48]:
I finally figured out what I was doing wrong. wvdialconf said: 'sorry can't find your modem' the wvdial.conf file i wrote had modem set to /dev/ttyS0, but, actually, no such device was listed in /dev. So I did ./MAKEDEV /ttyS0 which was wrong. 'don't know how to make /ttyS0' error returned. Then tried ./MAKEDEV ttyS0 and it worked. Then I did setserial -a /dev/ttyS0. Then wvdial works. I come from a Slackware/KDE environment and not familiar with these issues.
One question still: Isn't there a way to get back to a command line prompt once wvdial gets you connected without going to another virtual console??
No it seems that wvdial doesn't work in the background. Regards Nico
So now ttyS0 disappears when I reboot and I have to ./MAKEDEV ttyS0 again each time. What file do I have to edit (somewhere in the boot scripts?) so that it stays or is created at bootup? Again, thanks very much for the help . Jeff (larval stage)
On Friday 20 May 2005 19:50, Nico Golde wrote:
Hello JeffM,
- JeffM. mojaveplan@icehouse.net [2005-05-20 21:48]:
I finally figured out what I was doing wrong. wvdialconf said: 'sorry can't find your modem' the wvdial.conf file i wrote had modem set to /dev/ttyS0, but, actually, no such device was listed in /dev. So I did ./MAKEDEV /ttyS0 which was wrong. 'don't know how to make /ttyS0' error returned. Then tried ./MAKEDEV ttyS0 and it worked. Then I did setserial -a /dev/ttyS0. Then wvdial works. I come from a Slackware/KDE environment and not familiar with these issues.
One question still: Isn't there a way to get back to a command line prompt once wvdial gets you connected without going to another virtual console??
No it seems that wvdial doesn't work in the background. Regards Nico
On Friday 20 May 2005 19:50, Nico Golde wrote:
Hello JeffM,
- JeffM. mojaveplan@icehouse.net [2005-05-20 21:48]:
I finally figured out what I was doing wrong. wvdialconf said: 'sorry can't find your modem' the wvdial.conf file i wrote had modem set to /dev/ttyS0, but, actually, no such device was listed in /dev. So I did ./MAKEDEV /ttyS0 which was wrong. 'don't know how to make /ttyS0' error returned. Then tried ./MAKEDEV ttyS0 and it worked. Then I did setserial -a /dev/ttyS0. Then wvdial works. I come from a Slackware/KDE environment and not familiar with these issues.
One question still: Isn't there a way to get back to a command line prompt once wvdial gets you connected without going to another virtual console??
No it seems that wvdial doesn't work in the background. Regards Nico
Any help on this issue of mine please??:
So now ttyS0 disappears when I reboot and I have to ./MAKEDEV ttyS0 again each time. What file do I have to edit (somewhere in the boot scripts?) so that it stays or is created at bootup? Again, thanks very much for the help . Jeff (larval stage)
participants (5)
-
Ishwar Rattan -
JeffM. -
Julius Plenz -
Michael Prokop -
Nico Golde