john doe writes:
[...]
>>
>
> You might be better off asking this on the appropriate mailing list! :)
I asked:
https://lists.freedesktop.org/archives/systemd-devel/2022-May/047889.html
My impressions:
1. Scripts called by dhcp client are "BAD THING" (according to sys
network setup.
But in my case udhcpc seems to be the only DHCP client that will talk to
the LTE module in my router, others just balk and whine.
On 2022-05-08 11:19:33 +0800, Jeremy Ardley wrote:
> Of note: Using systemd-networkd you should not use NetworkManager or
> networking services. I think both use the ISC dhcp client
And what about NetworkManager users?
Note: it has its own internal DHCP client, but it is not robust on
On 5/8/2022 6:33 PM, Kamil Jońca wrote:
Kamil Jońca writes:
[...]
But systemd-networkd also has a huge number of configuration options
that may do what you want anyway
https://www.freedesktop.org/software/systemd/man/systemd.network.html
Hm. Can you create bridge without ports with systemd
Kamil Jońca writes:
[...]
>>
>> But systemd-networkd also has a huge number of configuration options
>> that may do what you want anyway
>>
>> https://www.freedesktop.org/software/systemd/man/systemd.network.html
>
> Hm. Can you create bridge without ports with systemd-networkd?
> i.e.
>
Another
On Sun, May 08, 2022 at 04:09:27PM +0200, Oliver Schoede wrote:
Alternatively there's dhcpcd5,
Be careful with this one unless you have a simple network
configuration--by default it will attempt to get addresses on all
interfaces that don't have them, not only ones you set to dhcp in
/etc/ne
On Sun, 8 May 2022 09:20:25 -0400
Dan Ritter wrote:
> Stefan Monnier wrote:
> > Rick Thomas [2022-05-07 19:47:57] wrote:
> > > According to the ISC webpage:
> > >> ISC has ended development on the ISC DHCP client as of early
> > >> 2022. This client
Stefan Monnier wrote:
> Rick Thomas [2022-05-07 19:47:57] wrote:
> > According to the ISC webpage:
> >> ISC has ended development on the ISC DHCP client as of early 2022.
> >> This client implementation is no longer maintained and should not be
> >> used in pr
On 2022-05-08 at 07:06, Rick Thomas wrote:
> On Sat, May 7, 2022, at 7:47 PM, Rick Thomas wrote:
>
>> According to the ISC webpage:
>>
>>> ISC has ended development on the ISC DHCP client as of early
>>> 2022. This client implementation is no longer main
On Sat, May 7, 2022, at 7:47 PM, Rick Thomas wrote:
> According to the ISC webpage:
>
>> ISC has ended development on the ISC DHCP client as of early 2022.
>> This client implementation is no longer maintained and should not be
>> used in production any longer.
>
>
e.com/questions/469716/systemd-networkd-run-script-after-dhcp-client-aqcuires-new-address
You mean:
"I couldn't get networkd-dispatcher to respond to dhcp changes on Ubuntu
Server 20.04, but[...] " :) ?
Yes. I know that this is two year old, but I did not found anything
newer with answe
On 8/5/22 2:27 pm, Rick Thomas wrote:
Thanks!
Rick
PS: I'll also do the IPv6 part, because I'm interested in that too.
One word of caution moving away from ISC dhcp client is that any
possibility of it being started by the networking daemon will result in
very bad behaviour i
On 8/5/22 3:19 pm, Kamil Jońca wrote:
I cannot see if systemd-networkd can run scripts[1] after change in
lease. Am I missing something?
The top answer below is a partial answer to your question.
https://unix.stackexchange.com/questions/469716/systemd-networkd-run-script-after-dhcp-client
Jeremy Ardley writes:
[...]
>
> You can just use systemd-networkd as an IPv4 dhcp client.
I cannot see if systemd-networkd can run scripts[1] after change in
lease. Am I missing something?
KJ
[1] similar to /etc/dhcp/dhclient*hooks.d
--
http://wolnelektury.pl/wesprzyj/teraz/
On 5/8/2022 5:24 AM, Rick Thomas wrote:
On Sat, May 7, 2022, at 8:14 PM, Jeremy Ardley wrote:
On 8/5/22 10:47 am, Rick Thomas wrote:
ISC has ended development on the ISC DHCP client as of early 2022.
This client implementation is no longer maintained and should not be
used in production any
On Sat, May 7, 2022, at 9:37 PM, Jeremy Ardley wrote:
> On 8/5/22 11:27 am, Rick Thomas wrote:
>> Thanks for the heads up!
>> Can you describe in detail what one needs to do in order to switch over?
>> I.e. what to remove, what to install? What to configure?
>
> This is a recent blogpost of min
On 8/5/22 11:27 am, Rick Thomas wrote:
Thanks for the heads up!
Can you describe in detail what one needs to do in order to switch over? I.e.
what to remove, what to install? What to configure?
This is a recent blogpost of mine showing a more complex installation
including IPv6 delegati
On Sat, May 7, 2022, at 8:19 PM, Jeremy Ardley wrote:
> On 8/5/22 11:14 am, Jeremy Ardley wrote:
>>
>>
>> You can just use systemd-networkd as an IPv4 dhcp client.
>>
>>
>
> Of note: Using systemd-networkd you should not use NetworkManager or
> networki
On Sat, May 7, 2022, at 8:14 PM, Jeremy Ardley wrote:
> On 8/5/22 10:47 am, Rick Thomas wrote:
>> ISC has ended development on the ISC DHCP client as of early 2022.
>>> This client implementation is no longer maintained and should not be
>>> used in production any longe
On 8/5/22 11:14 am, Jeremy Ardley wrote:
You can just use systemd-networkd as an IPv4 dhcp client.
Of note: Using systemd-networkd you should not use NetworkManager or
networking services. I think both use the ISC dhcp client
Of further note, I moved to systemd-networkd precisely
On 8/5/22 10:47 am, Rick Thomas wrote:
ISC has ended development on the ISC DHCP client as of early 2022.
This client implementation is no longer maintained and should not be
used in production any longer.
Can anybody recommend a good replacement?
I presently use systemd-networkd which
According to the ISC webpage:
> ISC has ended development on the ISC DHCP client as of early 2022.
> This client implementation is no longer maintained and should not be
> used in production any longer.
Can anybody recommend a good replacement?
Does anybody know what the Debian PTBs are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jaime T wrote:
> It works (almost) perfectly! For ages I've been baffled by why my dhcp
> server never responds to clients' first DHCPDISCOVER messages, but a
> quick look at the log shows why:
> [...]
>
> 22:58:05 dhclient[2830]: DHCPDISCOVER on wlo
Hi all. I'm running a freshly-installed minimal stretch box. It
connects wirelessly to my lan and it's a dhcp client, so
/etc/network/interfaces contains:
iface myInterface inet dhcp
wpa-ssid mySsid
wpa-psk myPsk
It works (almost) perfectly! For ages I've been baffled by why
On 7/17/14, rajiv chavan wrote:
> Thu, 17 Jul 2014 13:21:19 +0530
>
> Mett:
>
> Modem has ports 23,80,5431. Ssh may not be an option.
>
>
>
> On 7/15/14, mett wrote:
>> On Mon, 14 Jul 2014 22:33:11 +0530
>> rajiv chavan wrote:
>>
>>> On Mon, 14 Jul 2014 07:53:06 +0530
>>> - Hide quoted text -
>>
Thu, 17 Jul 2014 13:21:19 +0530
Mett:
Modem has ports 23,80,5431. Ssh may not be an option.
On 7/15/14, mett wrote:
> On Mon, 14 Jul 2014 22:33:11 +0530
> rajiv chavan wrote:
>
>> On Mon, 14 Jul 2014 07:53:06 +0530
>> - Hide quoted text -
>> rajiv chavan wrote:
>>
>> > Mon, 14 Jul 2014 07:2
On Mon, 14 Jul 2014 22:33:11 +0530
rajiv chavan wrote:
> On Mon, 14 Jul 2014 07:53:06 +0530
> - Hide quoted text -
> rajiv chavan wrote:
>
> > Mon, 14 Jul 2014 07:26:20 +0530
> >
> > Thank you Mett.
> > Traceroute packets from another host dropped by ISP netwoek at
> > 218.248.0.0
> >
> > >nets
On Mon, 14 Jul 2014 07:53:06 +0530
- Hide quoted text -
rajiv chavan wrote:
> Mon, 14 Jul 2014 07:26:20 +0530
>
> Thank you Mett.
> Traceroute packets from another host dropped by ISP netwoek at
> 218.248.0.0
>
> >netstat -rn
>
> Destination Gateway Genmask Flags MSS Window
On Mon, 14 Jul 2014 07:53:06 +0530
rajiv chavan wrote:
> Mon, 14 Jul 2014 07:26:20 +0530
>
> Thank you Mett.
> Traceroute packets from another host dropped by ISP netwoek at
> 218.248.0.0
>
> >netstat -rn
>
> Destination Gateway Genmask Flags MSS Window
> irtt Iface 0.0.0
On Mon, 14 Jul 2014 00:31:43 +0530
rajiv chavan wrote:
> Sun, 13 Jul 2014 23:34:41 +0530
>
> ip a output on an adsl+ (pppoe) client:
> =snip=
> 2: eth0: mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
> 3: ppp0: mtu 1
Sun, 13 Jul 2014 23:34:41 +0530
ip a output on an adsl+ (pppoe) client:
=snip=
2: eth0: mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
3: ppp0: mtu 1460 qdisc
pfifo_fast state UNKNOWN group default qlen 3
link/ppp
On Wed, Jul 9, 2014 at 2:01 PM, Sven Joachim wrote:
> On 2014-07-09 19:43 +0200, Tom H wrote:
>> On Wed, Jul 9, 2014 at 12:41 PM, Sven Joachim wrote:
>>> On 2014-07-09 08:59 +0200, Tom H wrote:
This one was against 2.02~beta2-7 in experimental.
>>>
>>> In unstable, not in experimental.
>>
>>
On Wed, 9 Jul 2014 15:41:31 -0400
Stephen Allen wrote:
> On Wed, Jul 09, 2014 at 06:41:08PM +0200, Sven Joachim wrote:
> > On 2014-07-09 08:59 +0200, Tom H wrote:
> >
> > > On Tue, Jul 8, 2014 at 9:07 PM, Stephen Allen
> > > wrote:
> > >>
> > >> For some time these bugs have existed in SID:
> >
On Wed, Jul 09, 2014 at 06:41:08PM +0200, Sven Joachim wrote:
> On 2014-07-09 08:59 +0200, Tom H wrote:
>
> > On Tue, Jul 8, 2014 at 9:07 PM, Stephen Allen
> > wrote:
> >>
> >> For some time these bugs have existed in SID:
> >>
> >> critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
> >> #7
On 2014-07-09 19:43 +0200, Tom H wrote:
> On Wed, Jul 9, 2014 at 12:41 PM, Sven Joachim wrote:
>> On 2014-07-09 08:59 +0200, Tom H wrote:
>>> This one was against 2.02~beta2-7 in experimental.
>>
>> In unstable, not in experimental.
>
> I was just looking at the changelog:
>
> grub2 (2.02~beta2-8
On Wed, Jul 9, 2014 at 12:41 PM, Sven Joachim wrote:
> On 2014-07-09 08:59 +0200, Tom H wrote:
>> On Tue, Jul 8, 2014 at 9:07 PM, Stephen Allen
>> wrote:
>>>
>>> For some time these bugs have existed in SID:
>>>
>>> critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
>>> #741464 - grub-pc-bi
On 2014-07-09 08:59 +0200, Tom H wrote:
> On Tue, Jul 8, 2014 at 9:07 PM, Stephen Allen
> wrote:
>>
>> For some time these bugs have existed in SID:
>>
>> critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
>> #741464 - grub-pc-bin: hangs after displaying boot menu
>
> This one was against 2
On Tue, Jul 08, 2014 at 09:07:44PM -0400, Stephen Allen wrote:
> For some time these bugs have existed in SID:
>
> critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
> #741464 - grub-pc-bin: hangs after displaying boot menu
> grave bugs of isc-dhcp-client (4.2.4-7
On Tue, Jul 8, 2014 at 9:07 PM, Stephen Allen
wrote:
>
> For some time these bugs have existed in SID:
>
> critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
> #741464 - grub-pc-bin: hangs after displaying boot menu
This one was against 2.02~beta2-7 in experimental.
You should let the deve
For some time these bugs have existed in SID:
critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-10)
#741464 - grub-pc-bin: hangs after displaying boot menu
grave bugs of isc-dhcp-client (4.2.4-7 → 4.3.0+dfsg-1)
#749410 - isc-dhcp-client: shutdown/reboot hangs after K03rsyslog
Any idea when
Hello
-- --
>> $ apt-cache policy isc-dhcp-client
>> isc-dhcp-client:
>> Installed: 4.2.2.dfsg.1-5+deb70u5
>> Candidate: 4.2.2.dfsg.1-5+deb70u5
>> Version table:
>> *** 4.2.2.dfsg.1-5+deb70u5 0
>> 100 /var/lib/dpkg/status
>>
Hello Slavko,
Excerpt from Slavko:
-- --
>> $ apt-cache policy isc-dhcp-client
>> isc-dhcp-client:
>> Installed: 4.2.2.dfsg.1-5+deb70u5
>> Candidate: 4.2.2.dfsg.1-5+deb70u5
>> Version table:
>> *** 4.2.2.dfsg.1-5+deb70u5 0
>> 100 /
Hi,
Dňa 12.05.2013 22:08 Thilo Six wrote / napísal(a):
>> By the package's QA page
>> (http://packages.qa.debian.org/i/isc-dhcp.html), the
>> 4.2.2.dfsg.1-5+deb70u5 package is in testing-proposed-updates repo.
>
> $ apt-cache policy isc-dhcp-client
> isc-dhcp-cli
Hello Slavko,
Excerpt from Slavko:
> Dňa 12.05.2013 18:27 Thilo Six wrote / napísal(a):
>> Hello
>>
>>
>> does somebody know what happened to "isc-dhcp-client 4.2.2.dfsg.1-5+deb70u5"?
>> It seems is has been droped from the archive. Currently i
Dňa 12.05.2013 18:27 Thilo Six wrote / napísal(a):
> Hello
>
>
> does somebody know what happened to "isc-dhcp-client 4.2.2.dfsg.1-5+deb70u5"?
> It seems is has been droped from the archive. Currently in wheezy is only
> "4.2.2.dfsg.1-5+deb70u3" avai
Hello
does somebody know what happened to "isc-dhcp-client 4.2.2.dfsg.1-5+deb70u5"?
It seems is has been droped from the archive. Currently in wheezy is only
"4.2.2.dfsg.1-5+deb70u3" available.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0
I don't know where to look or what to do about this newly arrived problem. I
have it on good authority that isc-dhcp-client and isc-dhcp-common have not
created problems for others and indeed I've not seen any post related to these
packages. It would appear they are part of the dhcp4 u
kj writes:
> Either ways vim.tiny to me is as frustrating as nvi, It's the first
> thing I remove after an install and replace with vim.basic
No need to remove vim-tiny. Whatever vi clone you have most recently
installed will be linked to /usr/bin/vi (you can change the link with
the update-alter
In <4a82e547.3050...@koffiejunkie.za.net>, kj wrote:
>Anyway, my post was not meant to be a debate about vi - just an example
>of something I'd like more information on.
Smaller, fewer dependencies. Both factors make the basic install faster and
make replacing the default take less time for user
Teemu Likonen wrote:
I don't know about your system but Vim has been the default since Debian
Etch.
Since I don't have it on my system anymore, I couldn't check :) John
Hasler corrected me: vim.tiny, not nvi. Either ways vim.tiny to me is
as frustrating as nvi, It's the first thing I remove
On 2009-08-12 13:11 (+0100), kj wrote:
> I don't know and there are many other choices I wonder about. It would
> be nice if there was a page somewhere discussing the choices of
> default packages, and reasons thereof. For example, why old vi (nvi?)
> over vim.
I don't know about your system but V
kj wrote:
> I don't know and there are many other choices I wonder about. It
> would be nice if there was a page somewhere discussing the choices of
> default packages, and reasons thereof. For example, why old vi (nvi?)
> over vim.
In Sid vim-tiny is "Priority: important" which I assume is what
kj wrote:
I don't know and there are many other choices I wonder about. It would
be nice if there was a page somewhere discussing the choices of default
packages, and reasons thereof. For example, why old vi (nvi?) over vim.
--kj
Agree.. the vi-vim gizzy would go on forever however.. lol
I don't know and there are many other choices I wonder about. It would
be nice if there was a page somewhere discussing the choices of default
packages, and reasons thereof. For example, why old vi (nvi?) over vim.
--kj
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oli D wrote:
> In short, I'm wondering why dhclient is still the default considering this
> bug/caveat and possibly if it possible to use dhcpcd as the default DHCP
> client
> on a Debian [Lenny] machine?
Just install dhcpcd (an
Hi,
As the title says, is there any reason why Debian uses dhclient as its default
DHCP client rather than dhcpcd? Are there any issue with dhcpcd I'm unaware of?
I'd really like to know, because as of now I'm having troubles with dhclient as
it refuses to register its hostname to
On Tuesday 20 November 2007, Andrei Popescu wrote:
> On Tue, Nov 20, 2007 at 09:03:17PM -0500, Hal Vaughan wrote:
> > Would that be a setting on their router or on their Windows server?
> > My guess is it depends on whether my system is behind uses NAT.
>
> Whatever they use as the DHCP server. Th
On Tue, Nov 20, 2007 at 09:03:17PM -0500, Hal Vaughan wrote:
> Would that be a setting on their router or on their Windows server? My
> guess is it depends on whether my system is behind uses NAT.
Whatever they use as the DHCP server. They could also be using some
managed switches and you are
On Tuesday 20 November 2007, you wrote:
> On 21/11/2007, Hal Vaughan <[EMAIL PROTECTED]> wrote:
> > I have a default Sarge installation that I had to move to a new
> > network. It had been getting the address through DHCP with no
> > problem. Now, on the new network, it tries to connect to a DHCP
On 21/11/2007, Hal Vaughan <[EMAIL PROTECTED]> wrote:
> I have a default Sarge installation that I had to move to a new network.
> It had been getting the address through DHCP with no problem. Now, on
> the new network, it tries to connect to a DHCP server, but there's no
> connection. I was not
On Tue, Nov 20, 2007 at 05:53:40PM -0500, Hal Vaughan wrote:
> I have a default Sarge installation that I had to move to a new network.
> It had been getting the address through DHCP with no problem. Now, on
> the new network, it tries to connect to a DHCP server, but there's no
> connection.
I have a default Sarge installation that I had to move to a new network.
It had been getting the address through DHCP with no problem. Now, on
the new network, it tries to connect to a DHCP server, but there's no
connection. I was not able to copy down the messages because the
business was c
gusti <[EMAIL PROTECTED]>:
>
> I have all the packages up-to-date, I'm using official kernel 2.6.18
> for debian stable. I already tried 'dhclient' from the packages
> 'dhcp-client' and 'dhcp3-client' and 'pump' from the pack
Hello
My network die after few minutes all the time.
I have all the packages up-to-date, I'm using official kernel 2.6.18
for debian stable. I already tried 'dhclient' from the packages
'dhcp-client' and 'dhcp3-client' and 'pump' from the package &
Kevin Veroneau <[EMAIL PROTECTED]> writes:
> My current set-up is, my ISP's cable modem connects to my debian
> sarge router/gateway. My other systems connect from that. My other
> systems run debian testing, when I connect the RJ-45 jack from my
> cable modem directly to my debian testing box,
Hello all,
I am new to this Mailing-list, but not to Debian GNU/Linux. I have been
using Debian for about 4 years now.
I am sending this regarding the dhcp client upgrade in debian sarge. I have
been having some troubles with keeping the connection with my ISP with newest
dhcp-client
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
Hello
I am using Debian Sarge. Whenever I boot the machine, the DHCP client
assigns an IP address, and just waits. Booting continues only when I
press Ctrl + C . Howver, the network works fine. Could you suggest some
remedy.
I had this
There's a config file which on Debian Sarge is at /etc/dhclient.conf I
think with a timeout variable. Just adjust that.
Thanks, Tom
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
> Hello
> I am using Debian Sarge. Whenever I boot the machine, the DHCP client
> assigns an I
On Tue, 2006-03-07 at 21:12 +0530, Aravind. R wrote:
> Hello
> I am using Debian Sarge. Whenever I boot the machine, the DHCP client
> assigns an IP address, and just waits. Booting continues only when I
> press Ctrl + C . Howver, the network works fine. Could you suggest s
Hello
I am using Debian Sarge. Whenever I boot the machine, the DHCP client
assigns an IP address, and just waits. Booting continues only when I
press Ctrl + C . Howver, the network works fine. Could you suggest some
remedy.
I'm not on the list. PLz CC replies.
Thanks & Regards
--
On Tuesday, 27 December 2005 at 15:34:19 +0100, Florian Kulzer wrote:
> Richard Lyons wrote:
>
> [...]
>
> >I found that too, and tried "modprobe ieee80211_crypt_wep" The module
> >loaded but the connection still obstinately failed. I found two other
> >modules in /lib/modules/2.6.14-2-686/kerne
Richard Lyons wrote:
[...]
I found that too, and tried "modprobe ieee80211_crypt_wep" The module
loaded but the connection still obstinately failed. I found two other
modules in /lib/modules/2.6.14-2-686/kernel/net/ieee80211/, namely
ieee80211_crypt_ccmp and ieee80211_crypt_tkip, so I modprobe
On Tuesday, 27 December 2005 at 2:13:22 +0100, Florian Kulzer wrote:
> Richard Lyons wrote:
>
> [...]
>
> >Nearly! You were right that the modules were not loaded. I tried
> >'modprobe ieee80211' and 'ifup eth0' and also rebooting after editing
> >/etc/modules. It now loads two modules ieee802
Richard Lyons wrote:
[...]
Nearly! You were right that the modules were not loaded. I tried
'modprobe ieee80211' and 'ifup eth0' and also rebooting after editing
/etc/modules. It now loads two modules ieee80211 and ieee80211_crypt.
I assume that is the expected outcome.
It still does not asso
Associated
>
> I think that is the cause of your problem: Your interface does not
> associate with the access point even after you set the ESSID
> and the KEY. (Otherwise we should see "Access Point: XX:XX:XX:XX:XX:XX"
> with the X's being the MAC address of y
On Sat, 24 Dec 2005 19:29:30 +
Richard Lyons <[EMAIL PROTECTED]> wrote:
> I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
> wifi card talks to the Netgear DG834G router when security is disabled,
> but when I turn WEP on it doesn't connect.
>
> /etc/network/interface
Hi again,
Richard Lyons wrote:
On Sunday, 25 December 2005 at 1:12:53 +0100, Florian Kulzer wrote:
Maybe you can first try to find out if you have a problem with the
interface itself or with the dhcp-client. To configure the interface
directly you can use the iwconfig command (as root)
I
On Saturday, 24 December 2005 at 23:37:45 -0500, jlquinn wrote:
> Richard Lyons wrote:
[...]
> >
> >Exiting.
> >
> >Failed to bring up eth0.
> >
> >Which tells me I left something out. But what?
>
> Chances are with a thinkpad that you have onboard ethernet. eth0 will
> correspond to th
> Maybe you can first try to find out if you have a problem with the
> interface itself or with the dhcp-client. To configure the interface
> directly you can use the iwconfig command (as root)
I did say that it connects perfectly when the router is not requiring
WEP security. So the hard
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coig
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coigxxx
received.
No working leases in persistent database.
Exiting.
Failed to bring up eth0.
Maybe you can first try to find out if you have a problem with the
interface itself or with the dhcp-client. To configure the interface
directly you can use the iwconfig command (as root)
iwconfig eth0
Richard Lyons wrote:
On Saturday, 24 December 2005 at 13:21:04 -0800, Andrew Sackville-West wrote:
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it d
Richard Lyons wrote:
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coigx
I am obviously missing the obvious here. An IBM Thinkpad, sid, orinoco
wifi card talks to the Netgear DG834G router when security is disabled,
but when I turn WEP on it doesn't connect.
/etc/network/interfaces has
iface eth0 inet dhcp
wireless-essid Coig
wireless-key -
Ron, I have reconfigured discover (that actually is discover1, : ) )
but it didnt create the symbolic links, so ive created manually the
mountpoints and disable discover to manage this mountpoints, and the
problem is now resolved.
If the machine doesnt have udev installed, is it necessary to hav
On Sunday 14 November 2004 02:05, "Sergio Cuéllar" wrote:
> Thanks, i ve already fixed the problem with dhcp-client , but i havent
> found the man pages of devfsd or udev. Ive also tried a dpkg -l |
> grep devfsd and it seems i dont have this packages installed.
>
> Which
On Sun, 2004-11-14 at 00:30 +, Alan Chandler wrote:
> On Saturday 13 November 2004 23:15, "Sergio Cuéllar" wrote:
> > Hi everybody, I am new to Debian and i find its a great Operating
> > System, I decided to use Debian Sarge, i made a netinstall and
> > everything work fine, just a few things
Thanks, i ve already fixed the problem with dhcp-client , but i havent
found the man pages of devfsd or udev. Ive also tried a dpkg -l |
grep devfsd and it seems i dont have this packages installed.
Which package do you recommend me to install ?
On Sun, 14 Nov 2004 00:30:05 +, Alan
t reboot (when it build all the devices again). You need to
checkout the appropriate man pages for the correct package which tells you
how to set up your own links automatically in the configuration file.
>
> The other question is about dhcp-client. I get my ip with dhcp and the
>
loppy0
drwxr-xr-x 2 root root 48 2004-10-28 13:13 floppy0
And it really doesnt exist, so i created cdrom0 and cdrom 1, but after
rebooting the directories disappeared. How can i create the mount
points for the cdroms and avoid that they are deleted after rebooting?
The other question is abou
Icebiker wrote:
- Original Message - From: "Alan Chandler"
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 11, 2004 15:37
Subject: Re: How does a linux dhcp client know it's name?
On Monday 11 October 2004 14:59, Icebiker wrote:
/etc/hostn
On Monday 11 October 2004 14:59, Icebiker wrote:
>
> /etc/hostname said "flipper". I tried pasting the local domain name on (my
> DLink router has a field for local domain name), but that didn't seem to do
> anything.
>
> I can't figure out how:
>
> - the resolver gets the host name from /etc/host
- Original Message -
From: "Rob Ellis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 10, 2004 00:45
Subject: Re: How does a linux dhcp client know it's name?
icebiker wrote:
Hi,
:
snip original post
:
What is in /etc/hostname ? Usu
icebiker wrote:
Hi,
I've got a sarge system connected to a DLink D604 router. I'm using
the router's dhcp server to assign IP addresses to the system. The
network configuration is what the debian installer gave me.
Some applications seem to have trouble understanding the network
configuration
Alec Berryman wrote:
begin quotation of icebiker on 2004-10-09 18:24:56 -0400:
[EMAIL PROTECTED]:/etc$ hostname -i
hostname: Unknown host
This (along with its omission in your email) leads me to believe
you've overlooked /etc/hosts. 'man hosts' for more information.
Sorry, I had looked
begin quotation of icebiker on 2004-10-09 18:24:56 -0400:
> [EMAIL PROTECTED]:/etc$ hostname -i
> hostname: Unknown host
This (along with its omission in your email) leads me to believe
you've overlooked /etc/hosts. 'man hosts' for more information.
signature.asc
Description: Digital signat
Hi,
I've got a sarge system connected to a DLink D604 router. I'm using the
router's dhcp server to assign IP addresses to the system. The network
configuration is what the debian installer gave me.
Some applications seem to have trouble understanding the network
configuration. For example, su
Please keep your replies on list and not to me privately unless it is
personal.
Kamaraju Kusumanchi wrote:
> Bob Proulx wrote:
> > What are you needing to configure?
>
> Thanks for the reply. I have the following lines in /etc/resolv.conf on
> the machine using dhcp-
Kamaraju Kusumanchi wrote:
> thanks all for the replies. Looks like dhcp-client is relatively easy to
> configure (compared to dhcp3-client) . I am able to get dhcp-client up
> and running. I will probably try pump during the weekend and get back to
> you.
Since dhcp3-client is ju
1 - 100 of 246 matches
Mail list logo
