Am Freitag, 17. Januar 2020, 11:12:07 CET schrieb Curt:
> On 2020-01-16, Rainer Dorsch wrote:
> > Am Mittwoch, 15. Januar 2020, 00:09:16 CET schrieb Pascal Hambourg:
> >> Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
> >> > prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
On 2020-01-16, Rainer Dorsch wrote:
> Am Mittwoch, 15. Januar 2020, 00:09:16 CET schrieb Pascal Hambourg:
>> Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
>> > prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>> >
>> > avoids the error message, but has no visible effect I c
Am Mittwoch, 15. Januar 2020, 00:09:16 CET schrieb Pascal Hambourg:
> Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
> > prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
> >
> > avoids the error message, but has no visible effect I can see. The IPv6
> > DNS
> > servers still
On Tue, Jan 14, 2020 at 01:18:01PM -0500, Greg Wooledge wrote:
> On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> > Just edit the file /etc/resolv.conf and make it immutable (chattr +i
[...]
> That is one of the options given on the wiki page.
>
> https://wiki.debian.org/resolv.conf
Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
avoids the error message, but has no visible effect I can see. The IPv6 DNS
servers still do not show in resolv.conf.
You may receive IPv6 DNS information from IPv6 Router Adv
Am Dienstag, 14. Januar 2020, 21:14:26 CET schrieben Sie:
> Am Dienstag, 14. Januar 2020, 19:18:01 CET schrieb Greg Wooledge:
> > On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> > > Just edit the file /etc/resolv.conf and make it immutable (chattr +i
> > > /etc/resolv.conf). At least
Am Dienstag, 14. Januar 2020, 19:18:01 CET schrieb Greg Wooledge:
> On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> > Just edit the file /etc/resolv.conf and make it immutable (chattr +i
> > /etc/resolv.conf). At least you will know what is in the file and that it
> > can't be change
On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> Just edit the file /etc/resolv.conf and make it immutable (chattr +i
> /etc/resolv.conf). At least you will know what is in the file and that it
> can't be changed (mistakes and all). I use this to keep chrome from
> changing the googl
Meanwhile, there are a few different ways to keep your resolv.conf
file untouched, rather than relying on isc-dhcp-client to continually
rewrite it in the form you want. The wiki page describes some of
those ways.
Personally, I do not understand the appeal of the "put lines in
configuration fi
On Tue, Jan 14, 2020 at 03:00:50PM +, Curt wrote:
> On 2020-01-14, Greg Wooledge wrote:
> > On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
> >> I tried to switch to other servers, e.g. Google, but this does not work,
> >> since
> >>
> >> /etc/resolv.conf gets overwritten wit
On 2020-01-14, Greg Wooledge wrote:
> On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
>> I tried to switch to other servers, e.g. Google, but this does not work,
>> since
>>
>> /etc/resolv.conf gets overwritten with a high frequency
>
> https://wiki.debian.org/resolv.conf
Actual
On 2020-01-14, Rainer Dorsch wrote:
>
> https://developers.google.com/speed/public-dns/docs/using
>
> and add to /etc/dhcp/dhclient.conf
>
> prepend domain-name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
> dhclient becomes unhappy (during an ifup eth0.1)
>
> /etc/dhcp/dhclient.conf lin
On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
> I tried to switch to other servers, e.g. Google, but this does not work, since
>
> /etc/resolv.conf gets overwritten with a high frequency
https://wiki.debian.org/resolv.conf
On 14/01/20 9:37 pm, Rainer Dorsch wrote:
> /etc/dhcp/dhclient.conf does not accept ipv6 addresses like, since if I
> use the instructions from
>
>
>
> https://developers.google.com/speed/public-dns/docs/using
>
>
>
> and add to /etc/dhcp/dhclient.conf
>
>
>
> prependdomain-name-server
On Monday, 10 July 2017 11:28:12 CEST Franz Angeli wrote:
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
I had a similar issue due to a missing firmware. I think it was on a broadcom
card.
Please check the kernel logs (journalctl -k
On Mon, Jul 10, 2017 at 12:55:53PM +0200, Dejan Jocic wrote:
> On 10-07-17, Franz Angeli wrote:
> > Hi,
> >
> > i have a problem with dhclient:
> >
> > for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> > BCM5719 Gigabit Ethernet PCIe (rev 01) :
> >
> > root@:~# dhclient
On 10-07-17, Franz Angeli wrote:
> Hi,
>
> i have a problem with dhclient:
>
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016
On Jo, 03 iul 14, 02:52:04, Bob Proulx wrote:
>
> That is the same as the Raspberry Pi. On the Pi they use a clever
> hack. At shutdown a file holds the timestamp of the time when the
> system shutdown. On boot the timestamp is used to set the current
> time for the system. That way the time d
Rainer Dorsch wrote:
> Another non-standard behavior might be that the system (Cubox-i) has no RTC,
> i.e. when the system boots, it always thinks it is in Jan 1st, 1970.
That is the same as the Raspberry Pi. On the Pi they use a clever
hack. At shutdown a file holds the timestamp of the time w
Hi Bob,
thanks for your response.
On Monday 23 June 2014 01:58:33 Bob Proulx wrote:
> Rainer Dorsch wrote:
> > my fritz.box is a DSL router from AVM, which unfortunately does not give
> > me
> > access to syslog.
>
> Oh. I didn't realize that. The way you talked about it I thought it
> was ano
Rainer Dorsch wrote:
> my fritz.box is a DSL router from AVM, which unfortunately does not give me
> access to syslog.
Oh. I didn't realize that. The way you talked about it I thought it
was another Debian system.
> What I noticed is that 192.168.178.87 shows up without MAC address
> in the li
On Sun, 22 Jun 2014 23:16:32 +0200
Rainer Dorsch wrote:
> I think I will try first to get support from AVM on that topic. If
> that is not successful, I will look in more detail into the
> tcpdumps (although since I have to take that on the client side,
> that might be difficult during the startu
Hi Bob,
my fritz.box is a DSL router from AVM, which unfortunately does not give me
access to syslog.
What I noticed is that 192.168.178.87 shows up without MAC address in the list
of network devices of the fritz.box
I think I will try first to get support from AVM on that topic. If that is n
Rainer Dorsch wrote:
> Hello,
>
> I have a system which comes up with one IP address 192.168.178.87 via
> dhclient, then after one day it gets eventually a different address
> 192.168.178.88 from my fritz.box, which runs the dhcp server:
>
> Any hint what is going on here or how to debug this is
Rainer Dorsch wrote:
> I have a system which comes up with one IP address 192.168.178.87 via
> dhclient, then after one day it gets eventually a different address
> 192.168.178.88 from my fritz.box, which runs the dhcp server:
On your fritz.box what does the dhcpd log to the syslog?
grep dhcp
On Fri, 20 Jun 2014 20:07:19 +0200
Rainer Dorsch wrote:
On the DHCP svr, what is in
/var/lib/dhcp/dhclient.leases & dhcpd.leases
before the lease renewing and after (the bad one)?
--
dylan : what do you think about abortion?
spidersnow : leave the choice to the kid.
signature.asc
Description:
On 8/7/2013 4:53 PM, Sean Alexandre wrote:
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote:
is your network like this, please:
-
|ISP|
-
|
|
Sean Alexandre wrote:
> OK, thanks, that's where I was headed, but was hoping it was
> something more obvious. I can get a tcpdump, but don't know DHCP
> very well. I'll take a look, though, and see what I can figure out.
The 'dhcpdump' package is useful for debugging dhcp issues. Easier
than wir
Dňa 07.08.2013 22:50 Sean Alexandre wrote / napísal(a):
> Aug 7 06:28:25 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255
> port 67 interval 3
> Aug 7 06:28:28 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255
> port 67 interval 6
> Aug 7 06:28:28 moose kernel: [ 211.3690
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote:
> is your network like this, please:
>
>-
>|ISP|
>-
> |
> |
>-
>
On Wed, Aug 07, 2013 at 08:29:53PM +0100, Klaus wrote:
> On 07/08/13 20:19, Sean Alexandre wrote:
> >On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
> >>On 07/08/13 18:24, Andy Hawkins wrote:
> >>>In article <20130807164822.GA7727@tuzo>,
> >>>Sean Alexandre wrote:
> No, unfortunately. I
Dňa 07.08.2013 21:19 Sean Alexandre wrote / napísal(a):
> On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
>> On 07/08/13 18:24, Andy Hawkins wrote:
>>> In article <20130807164822.GA7727@tuzo>,
>>> Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-
On 07/08/13 20:19, Sean Alexandre wrote:
On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
On 07/08/13 18:24, Andy Hawkins wrote:
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
router and the Debi
On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
> On 07/08/13 18:24, Andy Hawkins wrote:
> >In article <20130807164822.GA7727@tuzo>,
> > Sean Alexandre wrote:
> >>No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> >>router and the Debian Wheezy machine that works
On Wed, Aug 07, 2013 at 05:24:57PM +, Andy Hawkins wrote:
> In article <20130807164822.GA7727@tuzo>,
> Sean Alexandre wrote:
> > No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> > router and the Debian Wheezy machine that works get DHCP leases without any
> > probl
On 07/08/13 18:24, Andy Hawkins wrote:
Hi,
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
router and the Debian Wheezy machine that works get DHCP leases without any
problems, and have diffe
Hi,
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
> No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> router and the Debian Wheezy machine that works get DHCP leases without any
> problems, and have different MAC addresses.
>
> I also asked
On Wed, Aug 07, 2013 at 02:57:58PM +, Andy Hawkins wrote:
> Sean Alexandre wrote:
> > I've got two Debian Wheezy machines. One can connect to my cable modem fine,
> > and gets an IP address. The other can't. They're both configured the same.
> > Any
> > ideas why this might be?
>
> Apologies
Hi,
In article <20130807133856.GA6733@tuzo>,
Sean Alexandre wrote:
> I've got two Debian Wheezy machines. One can connect to my cable modem fine,
> and gets an IP address. The other can't. They're both configured the same. Any
> ideas why this might be?
Apologies for suggesting somethi
On Sun, 03 Jun 2012 13:34:41 -0700, Paul Zimmerman wrote:
> Camaleón wrote:
>>Put the logs here or better yet, upload them to www.pastebin.com
>>(remember to hide/remove any sensitive data contained at the logs).
>>>Also, as you are using WICD, it could be that there is a configuration
>>file tha
Camaleón wrote:
>Put the logs here or better yet, upload them to
>www.pastebin.com (remember to hide/remove any
>sensitive data contained at the logs). >Also, as you are using WICD, it could
>be that
>there is a configuration file that you to edit
>for this purpose... how about the "/etc/wicd
On Fri, 01 Jun 2012 14:29:29 -0700, Paul Zimmerman wrote:
> Tom H writes:
>>For the record, this works for squeeze without NM or WICD - for me.
>
>>Check how well or badly dhclient's behaving by changing "RUN=no" to
>>"RUN=yes" in "/etc/dhcp/dhclient-enter-hooks.d/debug", restarting your
>>netwo
Tom H writes:
>For the record, this works for squeeze without NM or WICD - for me.
>Check how well or badly dhclient's behaving by changing "RUN=no" to
>"RUN=yes" in "/etc/dhcp/dhclient-enter-hooks.d/debug", restarting
>your network (in your case, I assume that "service wicd restart" will
>do i
On Fri, May 25, 2012 at 11:47 AM, Camaleón wrote:
> On Thu, 24 May 2012 15:13:13 -0700, Paul Zimmerman wrote:
>> Camaleón wrote:
>>>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
dhclient in Squeeze pays no attention to the config file
at/etc/dhcp/dhclient.conf
On Thu, 24 May 2012 15:13:13 -0700, Paul Zimmerman wrote:
> Camaleón wrote:
>
>>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>
>>> dhclient in Squeeze pays no attention to the config file
>>> at/etc/dhcp/dhclient.conf
>
>>How does the file look like? Also, did you restart dhclient
On Thu, May 24, 2012 at 03:13:13PM -0700, Paul Zimmerman wrote:
> References: <1337870001.52679.yahoomail...@web162602.mail.bf1.yahoo.com>,
>
>
> Camaleón wrote:
>
> >On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>
> >> All I need it to do is prepend the local host to resolv.con
References: <1337870001.52679.yahoomail...@web162602.mail.bf1.yahoo.com>,
Camaleón wrote:
>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>> dhclient in Squeeze pays no attention to the config file
>> at/etc/dhcp/dhclient.conf
>How does the file look like? Also, did you restar
Hi
On Thu, May 24, 2012 at 03:33:21PM +0100, Paul Zimmerman wrote:
> dhclient in Squeeze pays no attention to the config file at
> /etc/dhcp/dhclient.conf
How about /etc/dhcp3/dhclient.conf ?
--
Karl E. Jorgensen
IT Operations
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.or
On Mon, 30 Apr 2012 20:23:52 +, Bonno Bloksma wrote:
> I have a server with several NICs, most of them have fixes addresses.
> One has an address assigned via DHCP as is it the cable internet
> connection. I now have a problem with that connection and want to
> reconnect by forcing a DHCP rene
Bonno Bloksma writes:
> Hi,
>
> I have a server with several NICs, most of them have fixes addresses. One has
> an address assigned via DHCP as is it the cable internet connection.
> I now have a problem with that connection and want to reconnect by forcing a
> DHCP renewal, but... how?
>
> As o
hvw59601 wrote:
hvw59601 wrote:
Camaleón wrote:
And there you see IMO where those renewals of 57 secs. come from:
'[renewtime] = 60'
Now I have to find a way to change that :-)
But whenever I try to change that value of '60', I get:
Error : Unable to configure LAN_private
Any hints?
hvw59601 wrote:
Camaleón wrote:
> On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:
>
> (...)
>
>> And from man page I can't see an option which you can configure from
the
>> client side to define a renewal interval... hum.
>
> Hugo... let's go debugging.
>
> Open a console and type
Camaleón wrote:
> On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:
>
> (...)
>
>> And from man page I can't see an option which you can configure from the
>> client side to define a renewal interval... hum.
>
> Hugo... let's go debugging.
>
> Open a console and type:
>
> telnet 192.168.0.190
>
On Sun, 08 Jan 2012 16:43:24 +, Camaleón wrote:
(...)
> And from man page I can't see an option which you can configure from the
> client side to define a renewal interval... hum.
Hugo... let's go debugging.
Open a console and type:
telnet 192.168.0.190
username: 1234 (type yours)
passwor
On Sun, 08 Jan 2012 09:29:44 -0600, hvw59601 wrote:
> Camaleón wrote:
>> Did you configure your "dhclient" to request a lease every 12 hours?
>>
>>
> I set /etc/dhcp/dhcp.conf (on Jan. 08 09:20) to:
>
> lease {
>interface "eth0";
>fixed-address 192.168.1.190;
>option subnet-mask 25
Camaleón wrote:
On Sat, 07 Jan 2012 17:25:42 -0600, hvw59601 wrote:
(...)
That's all commented out. Let me play with it. My feeling is that the
short lease times for both devices have to do with the external IP
changes.
And also the changes in leasetime occurred when the router changed, so
On Sat, 07 Jan 2012 17:25:42 -0600, hvw59601 wrote:
(...)
>>> That's all commented out. Let me play with it. My feeling is that the
>>> short lease times for both devices have to do with the external IP
>>> changes.
>>>
>>>
>> And also the changes in leasetime occurred when the router changed, so
On Sat, 07 Jan 2012 12:57:34 -0600, hvw59601 wrote:
> Camaleón wrote:
(...)
>> Mmm, since when "192.168.1.x" is an external IP? :-)
>>
>>
> No, that is internal. My external IP is changed every hour or so:
>
> Jan 7 09:18:41 HDBB ddclient[1730]: SUCCESS: updating
> esquipulas-index.dyndns.
Please trim your postings to just the parts you are referring to.
Your quoted parts are waaay tooo large. Thank you.
hvw59601 wrote:
> hvw59601 wrote:
> >hvw59601 wrote:
> >>Since I got on around 8AM, it is now 1PM, 5 hours, 4 changes.
That is a lot of chagnes. An unusually large number.
> >>
hvw59601 wrote:
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
The 2wire router from ISP Telmex Infinitum (Mexico) went on the
blink
so they gave a new one. It's a Tho
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
so they gave a new one. It's a Thomson TG585V8.
Hey
Camaleón wrote:
On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
so they gave a new one. It's a Thomson TG585V8.
Hey, we've got a bun
On Sat, 07 Jan 2012 12:22:55 -0600, hvw59601 wrote:
> hvw59601 wrote:
>> Camaleón wrote:
>>> On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
>>>
The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink
so they gave a new one. It's a Thomson TG585V8.
>>>
>>> Hey, we've go
hvw59601 wrote:
Camaleón wrote:
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
they gave a new one. It's a Thomson TG585V8.
Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)
One thing that I noticed is that
Camaleón wrote:
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
they gave a new one. It's a Thomson TG585V8.
Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)
One thing that I noticed is that the external IP n
On Sat, 07 Jan 2012 10:19:58 -0600, hvw59601 wrote:
> The 2wire router from ISP Telmex Infinitum (Mexico) went on the blink so
> they gave a new one. It's a Thomson TG585V8.
Hey, we've got a bunch of TG585v7 (for ISDN lines) :-)
> One thing that I noticed is that the external IP now changes abou
On Ma, 21 iun 11, 16:34:24, Ross Boylan wrote:
>
> I speculate that my previous efforts failed because I had not changed
> the (correct) dhclient.conf before reboot. Presumably before upgrade
> there was only one such file (under dhcp3/).
My guess is your previous attempts failed because you did
On Mi, 22 iun 11, 01:54:58, William Hopkins wrote:
> On 06/21/11 at 04:34pm, Ross Boylan wrote:
> > NetworkManager, not ifupdown, is managing my network connection.
>
> As noted many times elsewhere, it is not recommended to use networkmanager.
> Why
> it is still included in Debian default insta
On 06/21/11 at 04:34pm, Ross Boylan wrote:
> NetworkManager, not ifupdown, is managing my network connection.
As noted many times elsewhere, it is not recommended to use networkmanager. Why
it is still included in Debian default install is a mystery.
I will also suggest you look into KVMs serial
On Tue, 2011-06-21 at 12:59 -0700, Ross Boylan wrote:
> I have a kvm virtual machine whose disk was initially a copy of another
> virtual machine. The original machine's hostname was vm-lenny00. I
> changed the new machine to vm-migrate07
> in /etc/hostname, /etc/hosts, /etc/dhcp3/dhclient.conf (s
On Aug 17, 2010, at 12:30 PM, Boyd Stephen Smith Jr. wrote:
> In <84960162-4435-43b2-a07b-3361f8bda...@halblog.com>, Hal Vaughan wrote:
>> 2) It will only run bash scripts. I tried putting a Perl script in that
>> directory and it wouldn't work, so I had to put a bash script in that
>> directory
In <84960162-4435-43b2-a07b-3361f8bda...@halblog.com>, Hal Vaughan wrote:
>2) It will only run bash scripts. I tried putting a Perl script in that
>directory and it wouldn't work, so I had to put a bash script in that
>directory to run my Perl script.
This seems wrong. Did your perl script have
On Aug 15, 2010, at 5:41 PM, Hal Vaughan wrote:
> I've been reading the man pages for dhclient, but I'm stuck with one key
> question I've missed.
>
> I have an exit script set up to notify me of the IP address of a particular
> system (on a LAN) whenever the IP address changes. For now I'm t
On Aug 15, 2010, at 6:37 PM, Boyd Stephen Smith Jr. wrote:
> In <1af890a5-5bf9-46c9-8c4b-b709170dd...@halblog.com>, Hal Vaughan wrote:
>> I've been reading the man pages for dhclient, but I'm stuck with one key
>> question I've missed.
>>
>> I have an exit script set up to notify me of the IP ad
In <1af890a5-5bf9-46c9-8c4b-b709170dd...@halblog.com>, Hal Vaughan wrote:
>I've been reading the man pages for dhclient, but I'm stuck with one key
>question I've missed.
>
>I have an exit script set up to notify me of the IP address of a particular
>system (on a LAN) whenever the IP address change
On Thu, 10 Jun 2010 19:32:22 +0300
David Baron wrote:
> My logs are filling up with:
> Jun 10 15:16:14 dovidhalevi dhclient: send_packet: Operation not permitted
>
> I did not what is doing this, started happening after recent update of Sid
> but
> I did not notice exactly when. Network is bei
On Wed, 30 Sep 2009, Michael Pobega wrote:
> I get this problem on some networks; it seems to me that some routers just
> don't play nicely with dhclient. I've tried multiple times to find the source,
> but I've yet to have any luck.
Well, we'd need packet dumps (*full* packet dumps) from tcpdump
Hello List,
Michael Pobega wrote:
On 0, Jerome BENOIT wrote:
Hello List,
on my Lenny box, the message
dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
is printed continuously on the syslog file.
[...]
Thanks in advance,
Jerome
I get this problem on some networks; it seems to me that s
On 0, Jerome BENOIT wrote:
> Hello List,
>
> on my Lenny box, the message
>
> dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
>
> is printed continuously on the syslog file.
>
> [...]
>
> Thanks in advance,
> Jerome
>
I get this problem on some networks; it seems to me that some routers just
do
Hi Again,
Jerome BENOIT wrote:
Hello,
thanks for the reply.
Andrei Popescu wrote:
On Tue,29.Sep.09, 11:17:29, Jerome BENOIT wrote:
Hello List,
on my Lenny box, the message
dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
is printed continuously on the syslog file.
and suddenly the req
Hello,
thanks for the reply.
Andrei Popescu wrote:
On Tue,29.Sep.09, 11:17:29, Jerome BENOIT wrote:
Hello List,
on my Lenny box, the message
dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
is printed continuously on the syslog file.
Using tcpdump, it appears that dhclient sends something,
On Tue,29.Sep.09, 11:17:29, Jerome BENOIT wrote:
> Hello List,
>
> on my Lenny box, the message
>
> dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
>
> is printed continuously on the syslog file.
>
> Using tcpdump, it appears that dhclient sends something,
> but apparently gets no feed back.
>
Stefan Monnier writes:
>
> I recommend you install resolvconf (maybe it's installed already) and
> then you can place a script in /etc/resolvconf/update-libc.d which
> will be run whenever your resolv.conf file is modified (by getting
> some data from DHCP typically). I use this to automatically
> The script to switch to wireless is (run as root):
> --8<---cut here---start->8---
> #! /bin/bash
> cd /etc/exim4/
> rm /etc/exim4/update-exim4.conf.conf
> ln -s sympatico.conf.conf update-exim4.conf.conf
> dpkg-reconfigure -u exim4-config
> --8<-
Hello,
> In accordance with other people who also have the same laptop, the
> driver which should be used is the "sky2" (SysKonnect Yukon2).
I had the same problem as I said and other people also recommended the
ndiswrapper module for my computer and I didn't find why it don't work
even throug
Hi,
> Mind saying what module, exactly and where you got it from?
Sorry, I have a broadcom 4311 rev 1 and from an old install I was
using the ndiswrapper module, I've switched to b43 from the debian/
testing repository (I'm gently switching from unstable to testing).
Antonio Diaz,
Maybe could you
On Monday 04 August 2008 23:57, Antegallya wrote:
> Hi,
>
> > Could be a problem with the network adapter or the module. Try a
> > different adapter in the box?
>
> for me using an alternative module solved the problem.
Mind saying what module, exactly and where you got it from?
--
Shachar Or |
Hi,
> Could be a problem with the network adapter or the module. Try a
> different adapter in the box?
for me using an alternative module solved the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Monday 04 August 2008 22:25, Antonio Diaz wrote:
> Ok, I should have written a bit more. Maybe these points are helpful:
>
> * I've also installed Windows XP on my laptop and it works fine so I'm
> sure that the problem has to do with my linux configuration.
>
> * I've tested different kernel
Ok, I should have written a bit more. Maybe these points are helpful:
* I've also installed Windows XP on my laptop and it works fine so I'm
sure that the problem has to do with my linux configuration.
* I've tested different kernel versions (three of them).
* "dmesg" seems to say that the in
Hi,
I'm using Debian Sid too, and I have the same problem but for me it
is on wlan0 interface and I don't have any problem with eth0.
The problem appears on several wireless access points with or without
encryption, strangely, on some access points it "works better" than on
others (another machine
On Monday 04 August 2008 00:56, Antonio Diaz wrote:
>Hi
>
>I'm using Debian Sid (kernel 2.6.26). I need to configure the eth0 so
> it uses the dhcp. In my case the "dhclient" never gets response at boot
> time. Later, I have to restart the service "/etc/init.d/networking" to
> get a IP. Som
On Sun, Nov 11, 2007 at 11:22:14PM -0300, gusti wrote:
> Douglas A. Tutty wrote:
> >On Sun, Nov 11, 2007 at 07:37:57PM -0300, gusti wrote:
> >
> >>I'm using debian stable and kernel 2.6.18-5-686, and after some minutes
> >>I lost the network connection.
> >>I'm using the binary 'dhclient', see b
I have all my packages up to date. Can you send me please a link to the
security announcement that you are talking about.
Thank you.
Gustavo
Douglas A. Tutty wrote:
On Sun, Nov 11, 2007 at 07:37:57PM -0300, gusti wrote:
I'm using debian stable and kernel 2.6.18-5-686, and after some minu
On Sun, Nov 11, 2007 at 07:37:57PM -0300, gusti wrote:
>
> I'm using debian stable and kernel 2.6.18-5-686, and after some minutes
> I lost the network connection.
> I'm using the binary 'dhclient', see below, any ideas about the problem.
I've never needed dhcp. However, I remember that there
On Tue, May 02, 2006 at 07:23:57AM -0400, Tom Allison wrote:
> Mumia W wrote:
> >Tom Allison wrote:
> >
> >>I have a problem with my dhclient on my debian box.
> >>
> >>It keeps picking up an IP address and then losing it in a few seconds.
> >>[...]
> >
> >
> >Could it be that you accidentally inst
Florian Kulzer wrote:
>
> apt-cache --installed rdepends zeroconf
>
> will tell you which packages on your system have listed zeroconf in
> their "depends", "recommends" or "suggests" fields. Zeroconf often
> sneaks in via kdenetwork --depends--> kdnssd --depends--> libnss-mdns
> --recommends-->
On Tue, May 02, 2006 at 07:23:57 -0400, Tom Allison wrote:
> Mumia W wrote:
> >Tom Allison wrote:
> >
> >>I have a problem with my dhclient on my debian box.
> >>
> >>It keeps picking up an IP address and then losing it in a few seconds.
> >>[...]
> >
> >
> >Could it be that you accidentally instal
Mumia W wrote:
Tom Allison wrote:
I have a problem with my dhclient on my debian box.
It keeps picking up an IP address and then losing it in a few seconds.
[...]
Could it be that you accidentally installed the zeroconf package?
I did install zeroconf, it was brought in as a Add-in base
Tom Allison wrote:
I have a problem with my dhclient on my debian box.
It keeps picking up an IP address and then losing it in a few seconds.
[...]
Could it be that you accidentally installed the zeroconf package?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
1 - 100 of 151 matches
Mail list logo
