Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #69515 > unrolled thread
| Started by | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| First post | 2025-07-12 11:30 +0100 |
| Last post | 2025-07-14 00:10 -0400 |
| Articles | 20 on this page of 72 — 13 participants |
Back to article view | Back to comp.os.linux.misc
Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-12 11:30 +0100
Re: Spurious ARP entries... Robert Heller <heller@deepsoft.com> - 2025-07-12 10:36 +0000
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-12 11:52 +0100
Re: Spurious ARP entries... Andy Burns <usenet@andyburns.uk> - 2025-07-12 11:41 +0100
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-12 11:54 +0100
Re: Spurious ARP entries... Andy Burns <usenet@andyburns.uk> - 2025-07-12 12:14 +0100
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-12 13:06 +0100
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-13 01:20 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-13 00:16 -0400
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-13 12:01 +0100
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-13 22:10 +0000
Re: Spurious ARP entries... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-14 10:19 +0200
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-14 14:54 +0100
Re: Spurious ARP entries... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-15 11:58 +0200
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-15 15:20 +0100
Re: Spurious ARP entries... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-16 11:21 +0200
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-16 16:46 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-15 22:10 -0400
Re: Spurious ARP entries... Richard Kettlewell <invalid@invalid.invalid> - 2025-07-12 11:43 +0100
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-12 12:02 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-12 19:33 -0400
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-13 11:52 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-14 00:08 -0400
Re: Spurious ARP entries... Shadow <Sh@dow.br> - 2025-07-12 21:29 -0300
Re: Spurious ARP entries... Robert Heller <heller@deepsoft.com> - 2025-07-13 00:55 +0000
Re: Spurious ARP entries... Andy Burns <usenet@andyburns.uk> - 2025-07-13 06:35 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-13 02:30 -0400
Re: Spurious ARP entries... John Ames <commodorejohn@gmail.com> - 2025-07-14 08:06 -0700
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-14 22:05 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-15 22:21 -0400
Re: Spurious ARP entries... Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-07-16 15:53 +0000
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-16 19:19 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:13 -0400
Re: Spurious ARP entries... John Ames <commodorejohn@gmail.com> - 2025-07-16 08:05 -0700
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-16 16:47 +0100
Re: Spurious ARP entries... John Ames <commodorejohn@gmail.com> - 2025-07-16 09:02 -0700
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-16 19:17 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:10 -0400
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:08 -0400
Re: Spurious ARP entries... Richard Kettlewell <invalid@invalid.invalid> - 2025-07-16 19:18 +0100
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-16 19:21 +0100
Re: Spurious ARP entries... Pancho <Pancho.Jones@protonmail.com> - 2025-07-16 19:41 +0100
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-17 02:15 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:38 -0400
Re: Spurious ARP entries... Pancho <Pancho.Jones@protonmail.com> - 2025-07-17 09:29 +0100
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-17 09:46 +0100
Re: Spurious ARP entries... Pancho <Pancho.Jones@protonmail.com> - 2025-07-17 10:39 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 22:53 -0400
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-18 05:50 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-18 02:11 -0400
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 22:42 -0400
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-18 11:05 +0100
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-18 23:19 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-18 23:06 -0400
Re: Spurious ARP entries... Pancho <Pancho.Jones@protonmail.com> - 2025-07-19 10:50 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:15 -0400
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-17 09:50 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 22:48 -0400
Re: Spurious ARP entries... John Ames <commodorejohn@gmail.com> - 2025-07-18 09:02 -0700
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-18 05:48 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 03:41 -0400
Re: Spurious ARP entries... Richard Kettlewell <invalid@invalid.invalid> - 2025-07-17 11:19 +0100
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-17 22:58 -0400
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-17 02:14 +0000
Re: Spurious ARP entries... John Ames <commodorejohn@gmail.com> - 2025-07-17 07:52 -0700
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-17 19:59 +0100
Re: Spurious ARP entries... Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-07-18 05:47 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-15 22:20 -0400
Re: Spurious ARP entries... jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-07-13 13:03 -0400
Re: Spurious ARP entries... The Natural Philosopher <tnp@invalid.invalid> - 2025-07-13 21:46 +0100
Re: Spurious ARP entries... vallor <vallor@cultnix.org> - 2025-07-13 22:14 +0000
Re: Spurious ARP entries... c186282 <c186282@nnada.net> - 2025-07-14 00:10 -0400
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-12 19:33 -0400 |
| Message-ID | <9LCdnVkd__WVbO_1nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #69515 |
On 7/12/25 6:30 AM, The Natural Philosopher wrote: > > For unrelated reasons I took a look at my desktop ARP cache just now.. > > $arp -a > _gateway (192.168.0.254) at 00:1d:aa:79:78:40 [ether] on eno1 > pifi2 (192.168.0.202) at 2c:cf:67:88:c9:4b [ether] on eno1 > ? (192.168.0.248) at <incomplete> on eno1 > ? (192.168.0.2) at 1c:5a:3e:7e:37:1f [ether] on eno1 > ? (192.168.0.221) at <incomplete> on eno1 > ? (192.168.0.223) at <incomplete> on eno1 > Coriolanus (192.168.0.101) at d8:3a:dd:85:22:b1 [ether] on eno1 > ? (192.168.0.141) at <incomplete> on eno1 > ? (192.168.0.10) at <incomplete> on eno1 > ? (192.168.0.58) at <incomplete> on eno1 > ? (192.168.0.247) at <incomplete> on eno1 > heating-controller (192.168.0.201) at b8:27:eb:c3:31:3d [ether] on eno1 > ? (192.168.0.27) at <incomplete> on eno1 > ? (192.168.0.203) at <incomplete> on eno1 > ? (192.168.0.180) at <incomplete> on eno1 > ? (192.168.0.83) at <incomplete> on eno1 > cymbeline (192.168.0.100) at 08:62:66:4a:85:d8 [ether] on eno1 > ? (192.168.0.102) at 3c:a8:2a:f6:3a:c8 [ether] on eno1 > ? (192.168.0.16) at <incomplete> on eno1 > ? (192.168.0.227) at <incomplete> on eno1 > ? (192.168.0.11) at <incomplete> on eno1 > ? (192.168.0.239) at <incomplete> on eno1 > ? (192.168.0.28) at <incomplete> on eno1 > > The incomplete entries are for IP addresses I simply never have used. > > Anyone recognise this behaviour? > > After clearing, at least one is back... This could be a case of your router remembering where DHCP addresses USED to be. Even if you later set the devices to static, the old associations are't necessarily cleared. ARP may just be smelling traces of the missing devices.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-07-13 11:52 +0100 |
| Message-ID | <105035c$2n9pg$8@dont-email.me> |
| In reply to | #69527 |
On 13/07/2025 00:33, c186282 wrote:
> On 7/12/25 6:30 AM, The Natural Philosopher wrote:
>>
>> For unrelated reasons I took a look at my desktop ARP cache just now..
>>
>> $arp -a
>> _gateway (192.168.0.254) at 00:1d:aa:79:78:40 [ether] on eno1
>> pifi2 (192.168.0.202) at 2c:cf:67:88:c9:4b [ether] on eno1
>> ? (192.168.0.248) at <incomplete> on eno1
>> ? (192.168.0.2) at 1c:5a:3e:7e:37:1f [ether] on eno1
>> ? (192.168.0.221) at <incomplete> on eno1
>> ? (192.168.0.223) at <incomplete> on eno1
>> Coriolanus (192.168.0.101) at d8:3a:dd:85:22:b1 [ether] on eno1
>> ? (192.168.0.141) at <incomplete> on eno1
>> ? (192.168.0.10) at <incomplete> on eno1
>> ? (192.168.0.58) at <incomplete> on eno1
>> ? (192.168.0.247) at <incomplete> on eno1
>> heating-controller (192.168.0.201) at b8:27:eb:c3:31:3d [ether] on eno1
>> ? (192.168.0.27) at <incomplete> on eno1
>> ? (192.168.0.203) at <incomplete> on eno1
>> ? (192.168.0.180) at <incomplete> on eno1
>> ? (192.168.0.83) at <incomplete> on eno1
>> cymbeline (192.168.0.100) at 08:62:66:4a:85:d8 [ether] on eno1
>> ? (192.168.0.102) at 3c:a8:2a:f6:3a:c8 [ether] on eno1
>> ? (192.168.0.16) at <incomplete> on eno1
>> ? (192.168.0.227) at <incomplete> on eno1
>> ? (192.168.0.11) at <incomplete> on eno1
>> ? (192.168.0.239) at <incomplete> on eno1
>> ? (192.168.0.28) at <incomplete> on eno1
>>
>> The incomplete entries are for IP addresses I simply never have used.
>>
>> Anyone recognise this behaviour?
>>
>> After clearing, at least one is back...
>
> This could be a case of your router remembering
> where DHCP addresses USED to be. Even if you later
> set the devices to static, the old associations
> are't necessarily cleared. ARP may just be
> smelling traces of the missing devices.
Er no. This cache existed in the desktop computer only, not the router,
at all.
And its nothing to do with DHCP.
Its an ARP cache. Not DHCP.
--
"The most difficult subjects can be explained to the most slow witted
man if he has not formed any idea of them already; but the simplest
thing cannot be made clear to the most intelligent man if he is firmly
persuaded that he knows already, without a shadow of doubt, what is laid
before him."
- Leo Tolstoy
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-14 00:08 -0400 |
| Message-ID | <Q4ycnXosOqZTH-n1nZ2dnZfqnPudnZ2d@giganews.com> |
| In reply to | #69538 |
On 7/13/25 6:52 AM, The Natural Philosopher wrote: > On 13/07/2025 00:33, c186282 wrote: >> On 7/12/25 6:30 AM, The Natural Philosopher wrote: >>> >>> For unrelated reasons I took a look at my desktop ARP cache just now.. >>> >>> $arp -a >>> _gateway (192.168.0.254) at 00:1d:aa:79:78:40 [ether] on eno1 >>> pifi2 (192.168.0.202) at 2c:cf:67:88:c9:4b [ether] on eno1 >>> ? (192.168.0.248) at <incomplete> on eno1 >>> ? (192.168.0.2) at 1c:5a:3e:7e:37:1f [ether] on eno1 >>> ? (192.168.0.221) at <incomplete> on eno1 >>> ? (192.168.0.223) at <incomplete> on eno1 >>> Coriolanus (192.168.0.101) at d8:3a:dd:85:22:b1 [ether] on eno1 >>> ? (192.168.0.141) at <incomplete> on eno1 >>> ? (192.168.0.10) at <incomplete> on eno1 >>> ? (192.168.0.58) at <incomplete> on eno1 >>> ? (192.168.0.247) at <incomplete> on eno1 >>> heating-controller (192.168.0.201) at b8:27:eb:c3:31:3d [ether] on eno1 >>> ? (192.168.0.27) at <incomplete> on eno1 >>> ? (192.168.0.203) at <incomplete> on eno1 >>> ? (192.168.0.180) at <incomplete> on eno1 >>> ? (192.168.0.83) at <incomplete> on eno1 >>> cymbeline (192.168.0.100) at 08:62:66:4a:85:d8 [ether] on eno1 >>> ? (192.168.0.102) at 3c:a8:2a:f6:3a:c8 [ether] on eno1 >>> ? (192.168.0.16) at <incomplete> on eno1 >>> ? (192.168.0.227) at <incomplete> on eno1 >>> ? (192.168.0.11) at <incomplete> on eno1 >>> ? (192.168.0.239) at <incomplete> on eno1 >>> ? (192.168.0.28) at <incomplete> on eno1 >>> >>> The incomplete entries are for IP addresses I simply never have used. >>> >>> Anyone recognise this behaviour? >>> >>> After clearing, at least one is back... >> >> This could be a case of your router remembering >> where DHCP addresses USED to be. Even if you later >> set the devices to static, the old associations >> are't necessarily cleared. ARP may just be >> smelling traces of the missing devices. > > Er no. This cache existed in the desktop computer only, not the router, > at all. > And its nothing to do with DHCP. > > Its an ARP cache. Not DHCP. Ummm ... "cache" is the key-word. I think the OP is seeing junk associated with OLD addresses. MOST likely source is the router - but old junk CAN persist on a local PC too. In short, I don't think he's seeing anything REAL or RELEVANT. I did IT for a smallish company for 20+ years. This sort of weird stuff was NOT unusual at all. It didn't MEAN anything ... just an artifact of old caches/logs/tables. "Small-ish" was an ADVANTAGE here - the data volume/depth was NOT overwhelming ... you could have time to probe and analyze.
[toc] | [prev] | [next] | [standalone]
| From | Shadow <Sh@dow.br> |
|---|---|
| Date | 2025-07-12 21:29 -0300 |
| Message-ID | <jav57k1fv6kfgaabj6atbv7n505urkagsu@4ax.com> |
| In reply to | #69515 |
On Sat, 12 Jul 2025 11:30:26 +0100, The Natural Philosopher <tnp@invalid.invalid> wrote: > >For unrelated reasons I took a look at my desktop ARP cache just now.. > >$arp -a >_gateway (192.168.0.254) at 00:1d:aa:79:78:40 [ether] on eno1 >pifi2 (192.168.0.202) at 2c:cf:67:88:c9:4b [ether] on eno1 >? (192.168.0.248) at <incomplete> on eno1 >? (192.168.0.2) at 1c:5a:3e:7e:37:1f [ether] on eno1 >? (192.168.0.221) at <incomplete> on eno1 >? (192.168.0.223) at <incomplete> on eno1 >Coriolanus (192.168.0.101) at d8:3a:dd:85:22:b1 [ether] on eno1 >? (192.168.0.141) at <incomplete> on eno1 >? (192.168.0.10) at <incomplete> on eno1 >? (192.168.0.58) at <incomplete> on eno1 >? (192.168.0.247) at <incomplete> on eno1 >heating-controller (192.168.0.201) at b8:27:eb:c3:31:3d [ether] on eno1 >? (192.168.0.27) at <incomplete> on eno1 >? (192.168.0.203) at <incomplete> on eno1 >? (192.168.0.180) at <incomplete> on eno1 >? (192.168.0.83) at <incomplete> on eno1 >cymbeline (192.168.0.100) at 08:62:66:4a:85:d8 [ether] on eno1 >? (192.168.0.102) at 3c:a8:2a:f6:3a:c8 [ether] on eno1 >? (192.168.0.16) at <incomplete> on eno1 >? (192.168.0.227) at <incomplete> on eno1 >? (192.168.0.11) at <incomplete> on eno1 >? (192.168.0.239) at <incomplete> on eno1 >? (192.168.0.28) at <incomplete> on eno1 > >The incomplete entries are for IP addresses I simply never have used. > >Anyone recognise this behaviour? > >After clearing, at least one is back... My TV is always in my arp cache. I kind of got used to the intrusion. []'s -- Don't be evil - Google 2004 We have a new policy - Google 2012 Google Fuchsia - 2021
[toc] | [prev] | [next] | [standalone]
| From | Robert Heller <heller@deepsoft.com> |
|---|---|
| Date | 2025-07-13 00:55 +0000 |
| Message-ID | <104v06h$2dvsb$1@dont-email.me> |
| In reply to | #69528 |
At Sat, 12 Jul 2025 21:29:32 -0300 Shadow <Sh@dow.br> wrote: > > On Sat, 12 Jul 2025 11:30:26 +0100, The Natural Philosopher > <tnp@invalid.invalid> wrote: > > > > >For unrelated reasons I took a look at my desktop ARP cache just now.. > > > >$arp -a > >_gateway (192.168.0.254) at 00:1d:aa:79:78:40 [ether] on eno1 > >pifi2 (192.168.0.202) at 2c:cf:67:88:c9:4b [ether] on eno1 > >? (192.168.0.248) at <incomplete> on eno1 > >? (192.168.0.2) at 1c:5a:3e:7e:37:1f [ether] on eno1 > >? (192.168.0.221) at <incomplete> on eno1 > >? (192.168.0.223) at <incomplete> on eno1 > >Coriolanus (192.168.0.101) at d8:3a:dd:85:22:b1 [ether] on eno1 > >? (192.168.0.141) at <incomplete> on eno1 > >? (192.168.0.10) at <incomplete> on eno1 > >? (192.168.0.58) at <incomplete> on eno1 > >? (192.168.0.247) at <incomplete> on eno1 > >heating-controller (192.168.0.201) at b8:27:eb:c3:31:3d [ether] on eno1 > >? (192.168.0.27) at <incomplete> on eno1 > >? (192.168.0.203) at <incomplete> on eno1 > >? (192.168.0.180) at <incomplete> on eno1 > >? (192.168.0.83) at <incomplete> on eno1 > >cymbeline (192.168.0.100) at 08:62:66:4a:85:d8 [ether] on eno1 > >? (192.168.0.102) at 3c:a8:2a:f6:3a:c8 [ether] on eno1 > >? (192.168.0.16) at <incomplete> on eno1 > >? (192.168.0.227) at <incomplete> on eno1 > >? (192.168.0.11) at <incomplete> on eno1 > >? (192.168.0.239) at <incomplete> on eno1 > >? (192.168.0.28) at <incomplete> on eno1 > > > >The incomplete entries are for IP addresses I simply never have used. > > > >Anyone recognise this behaviour? > > > >After clearing, at least one is back... > > My TV is always in my arp cache. I kind of got used to the > intrusion. > []'s Likely it is because you have the "instant on" (whatever it may be called) feature on. I suspect this means that the TV is in "sleep" mode rather than fully powered down. The processor is "running" in some minimual state and is maintaining a minimual network connection. -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-07-13 06:35 +0100 |
| Message-ID | <mdgutuF8kjbU2@mid.individual.net> |
| In reply to | #69529 |
Robert Heller wrote: > I suspect this means that the TV is in "sleep" mode rather than > fully powered down. The processor is "running" in some minimual state and is > maintaining a minimual network connection. I've got two devices with a horrible ARP implementation, they don't send ARP replies in response to ARP requests, instead they constantly broadcast ARP replies for their own IP/MAC combination.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-13 02:30 -0400 |
| Message-ID | <AXGdnT6o4Yo1z-71nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #69533 |
On 7/13/25 1:35 AM, Andy Burns wrote: > Robert Heller wrote: > >> I suspect this means that the TV is in "sleep" mode rather than >> fully powered down. The processor is "running" in some minimual state >> and is >> maintaining a minimual network connection. > > I've got two devices with a horrible ARP implementation, they don't send > ARP replies in response to ARP requests, instead they constantly > broadcast ARP replies for their own IP/MAC combination. Old DCHP addresses tend to hang-out in routers. Change them to static later - doesn't matter. The device/IP info remains in router memory. Some utilities WILL note this, and try to send packets.
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2025-07-14 08:06 -0700 |
| Message-ID | <20250714080642.000009df@gmail.com> |
| In reply to | #69535 |
On Sun, 13 Jul 2025 02:30:11 -0400 c186282 <c186282@nnada.net> wrote: > Old DCHP addresses tend to hang-out in routers. Change them to static > later - doesn't matter. The device/IP info remains in router memory. > Some utilities WILL note this, and try to send packets. Causes no end of trouble in $DAYJOB - try to maintina a local file- share between customers' office PCs and even if Windows isn't being stubborn about NetBIOS name resolution, it's guaranteed that at some point the host machine will get a new IP and yet the same damn router that handed it out will respond to DNS requests with the old IP! (Set it to a static IP and, guaranteed, some "helpful" local IT mook will come along a couple months later and switch it back...) DHCP was a mistake, full stop.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-07-14 22:05 +0000 |
| Message-ID | <1053uuv$3kipi$6@dont-email.me> |
| In reply to | #69572 |
On Mon, 14 Jul 2025 08:06:42 -0700, John Ames wrote: > DHCP was a mistake, full stop. The Microsoft implementation of it is where the mistake lies. DHCP itself is extremely useful, and works fine across a range of systems as long as Microsoft is not involved.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-15 22:21 -0400 |
| Message-ID | <KSqdnRLcELcVker1nZ2dnZfqnPcAAAAA@giganews.com> |
| In reply to | #69583 |
On 7/14/25 6:05 PM, Lawrence D'Oliveiro wrote: > On Mon, 14 Jul 2025 08:06:42 -0700, John Ames wrote: > >> DHCP was a mistake, full stop. > > The Microsoft implementation of it is where the mistake lies. DHCP itself > is extremely useful, and works fine across a range of systems as long as > Microsoft is not involved. Everything works better when M$ is not involved ...
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2025-07-16 15:53 +0000 |
| Message-ID | <JVPdQ.495183$sKi9.6945@fx14.iad> |
| In reply to | #69600 |
On 2025-07-16, c186282 <c186282@nnada.net> wrote: > On 7/14/25 6:05 PM, Lawrence D'Oliveiro wrote: > >> On Mon, 14 Jul 2025 08:06:42 -0700, John Ames wrote: >> >>> DHCP was a mistake, full stop. >> >> The Microsoft implementation of it is where the mistake lies. DHCP itself >> is extremely useful, and works fine across a range of systems as long as >> Microsoft is not involved. > > Everything works better when M$ is not involved ... Q: Why is a computer like an air conditioner? A: It stops working when you open Windows. -- /~\ Charlie Gibbs | Growth for the sake of \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology X I'm really at ac.dekanfrus | of the cancer cell. / \ if you read it the right way. | -- Edward Abbey
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-07-16 19:19 +0100 |
| Message-ID | <1058qfm$riau$4@dont-email.me> |
| In reply to | #69622 |
On 16/07/2025 16:53, Charlie Gibbs wrote: > On 2025-07-16, c186282 <c186282@nnada.net> wrote: > >> On 7/14/25 6:05 PM, Lawrence D'Oliveiro wrote: >> >>> On Mon, 14 Jul 2025 08:06:42 -0700, John Ames wrote: >>> >>>> DHCP was a mistake, full stop. >>> >>> The Microsoft implementation of it is where the mistake lies. DHCP itself >>> is extremely useful, and works fine across a range of systems as long as >>> Microsoft is not involved. >> >> Everything works better when M$ is not involved ... > > Q: Why is a computer like an air conditioner? > A: It stops working when you open Windows. > Q:Why is a Vax computer like an erect penis? A: It will stay up as long as you don't fuck with it. -- "A point of view can be a dangerous luxury when substituted for insight and understanding". Marshall McLuhan
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-17 03:13 -0400 |
| Message-ID | <7vCdnR4tB_cyP-X1nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #69633 |
On 7/16/25 2:19 PM, The Natural Philosopher wrote: > On 16/07/2025 16:53, Charlie Gibbs wrote: >> On 2025-07-16, c186282 <c186282@nnada.net> wrote: >> >>> On 7/14/25 6:05 PM, Lawrence D'Oliveiro wrote: >>> >>>> On Mon, 14 Jul 2025 08:06:42 -0700, John Ames wrote: >>>> >>>>> DHCP was a mistake, full stop. >>>> >>>> The Microsoft implementation of it is where the mistake lies. DHCP >>>> itself >>>> is extremely useful, and works fine across a range of systems as >>>> long as >>>> Microsoft is not involved. >>> >>> Everything works better when M$ is not involved ... >> >> Q: Why is a computer like an air conditioner? >> A: It stops working when you open Windows. >> > Q:Why is a Vax computer like an erect penis? > A: It will stay up as long as you don't fuck with it. Ha - DO have some VAX/VMS experience. WISH someone would create a Neo-VMS as a Linux alt. But yea, go with the paradigm.
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2025-07-16 08:05 -0700 |
| Message-ID | <20250716080531.000065e9@gmail.com> |
| In reply to | #69583 |
On Mon, 14 Jul 2025 22:05:20 -0000 (UTC) Lawrence D'Oliveiro <ldo@nz.invalid> wrote: > > DHCP was a mistake, full stop. > > The Microsoft implementation of it is where the mistake lies. DHCP > itself is extremely useful, and works fine across a range of systems > as long as Microsoft is not involved. If it was *just* Windows it wouldn't be difficult to rig up a scheduled task to flush the DNS cache; stupid, yes, but surmountable. What really drivs *me* up the wall is when the *router* can't even keep its own records straight.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-07-16 16:47 +0100 |
| Message-ID | <1058hiv$pg5q$11@dont-email.me> |
| In reply to | #69618 |
On 16/07/2025 16:05, John Ames wrote: > On Mon, 14 Jul 2025 22:05:20 -0000 (UTC) > Lawrence D'Oliveiro <ldo@nz.invalid> wrote: > >>> DHCP was a mistake, full stop. >> >> The Microsoft implementation of it is where the mistake lies. DHCP >> itself is extremely useful, and works fine across a range of systems >> as long as Microsoft is not involved. > > If it was *just* Windows it wouldn't be difficult to rig up a scheduled > task to flush the DNS cache; stupid, yes, but surmountable. What really > drivs *me* up the wall is when the *router* can't even keep its own > records straight. > My router does impeccably. The difference between the crap mass market routers I used to have and the current Draytek, is chalk and cheese. -- “The ultimate result of shielding men from the effects of folly is to fill the world with fools.” Herbert Spencer
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2025-07-16 09:02 -0700 |
| Message-ID | <20250716090206.00005cea@gmail.com> |
| In reply to | #69620 |
On Wed, 16 Jul 2025 16:47:43 +0100 The Natural Philosopher <tnp@invalid.invalid> wrote: > My router does impeccably. > > The difference between the crap mass market routers I used to have > and the current Draytek, is chalk and cheese. For sure - but when you're dealing with penny-pinching small-business owners, it's pulling teeth to even get them to replace a *failing* router, let alone one that does stupid things which cause daily head- aches but "works just fine!" :/
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-07-16 19:17 +0100 |
| Message-ID | <1058qbv$riau$3@dont-email.me> |
| In reply to | #69625 |
On 16/07/2025 17:02, John Ames wrote: > On Wed, 16 Jul 2025 16:47:43 +0100 > The Natural Philosopher <tnp@invalid.invalid> wrote: > >> My router does impeccably. >> >> The difference between the crap mass market routers I used to have >> and the current Draytek, is chalk and cheese. > > For sure - but when you're dealing with penny-pinching small-business > owners, it's pulling teeth to even get them to replace a *failing* > router, let alone one that does stupid things which cause daily head- > aches but "works just fine!" :/ > I've got a dreadful old ADSL Netgear router acting as a Wifi Point - its ADSL capability vanished in a thunderstorm. Ive got a really good old Cisco badged SOHO router as well... -- Climate Change: Socialism wearing a lab coat.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-17 03:10 -0400 |
| Message-ID | <UxCdnRIxX5iWP-X1nZ2dnZfqn_cAAAAA@giganews.com> |
| In reply to | #69625 |
On 7/16/25 12:02 PM, John Ames wrote: > On Wed, 16 Jul 2025 16:47:43 +0100 > The Natural Philosopher <tnp@invalid.invalid> wrote: > >> My router does impeccably. >> >> The difference between the crap mass market routers I used to have >> and the current Draytek, is chalk and cheese. > > For sure - but when you're dealing with penny-pinching small-business > owners, it's pulling teeth to even get them to replace a *failing* > router, let alone one that does stupid things which cause daily head- > aches but "works just fine!" :/ Know what you mean. Basically, never TELL them you're changing routers/paradigms - just DO it. Wait for permission and NOTHING changes. BCrats live by doing NOTHING.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-07-17 03:08 -0400 |
| Message-ID | <UxCdnRMxX5joPOX1nZ2dnZfqn_ednZ2d@giganews.com> |
| In reply to | #69620 |
On 7/16/25 11:47 AM, The Natural Philosopher wrote: > On 16/07/2025 16:05, John Ames wrote: >> On Mon, 14 Jul 2025 22:05:20 -0000 (UTC) >> Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >> >>>> DHCP was a mistake, full stop. >>> >>> The Microsoft implementation of it is where the mistake lies. DHCP >>> itself is extremely useful, and works fine across a range of systems >>> as long as Microsoft is not involved. >> >> If it was *just* Windows it wouldn't be difficult to rig up a scheduled >> task to flush the DNS cache; stupid, yes, but surmountable. What really >> drivs *me* up the wall is when the *router* can't even keep its own >> records straight. >> > My router does impeccably. > > The difference between the crap mass market routers I used to have and > the current Draytek, is chalk and cheese. Proper linux-based routers are indeed the Best Way. I mostly used the "IPFire" disto - yea, funny name but fully functional - on a SuperMicro mini-box. There are a number of others. Unlike Win - these give you much finer control, and the ability to run custom scripts once you find the "in". "Sophos" is quite popular and even a bit more customizable. Downside, more complicated.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-07-16 19:18 +0100 |
| Message-ID | <wwvecugvw1p.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #69618 |
John Ames <commodorejohn@gmail.com> writes: > Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >> > DHCP was a mistake, full stop. >> >> The Microsoft implementation of it is where the mistake lies. DHCP >> itself is extremely useful, and works fine across a range of systems >> as long as Microsoft is not involved. > > If it was *just* Windows it wouldn't be difficult to rig up a scheduled > task to flush the DNS cache; stupid, yes, but surmountable. What really > drivs *me* up the wall is when the *router* can't even keep its own > records straight. That’s not a DHCP problem, that’s a useless router problem. Personally I have far too many IP endpoints for manual address assignment to be remotely attractive, and that’s before counting guests’ laptops and phones, etc. -- https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web