Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196409 > unrolled thread

self identifying computer

Back to article view | Back to linux.debian.user

Contents

  self identifying computer mick crane <mick.crane@gmail.com> - 2018-06-05 01:00 +0200
    Re: self identifying computer Ben Caradoc-Davies <ben@transient.nz> - 2018-06-05 03:40 +0200
    Re: self identifying computer john doe <johndoe65534@mail.com> - 2018-06-05 09:00 +0200
      Re: self identifying computer mick crane <mick.crane@gmail.com> - 2018-06-05 12:30 +0200
        Re: self identifying computer john doe <johndoe65534@mail.com> - 2018-06-05 18:10 +0200
    Re: self identifying computer Joe <joe@jretrading.com> - 2018-06-05 09:50 +0200

#196409 — self identifying computer

I changed the domain name for couple of home computers from "local" to 
"home"
one of them is win 10 PC.
I have ipfire box doing hopefully firewall and DNS and so while I 
changed domain I let all get address from its DHCP and gave them fixed 
leases.
I have 2 debian PCs
I try to find IP address of a cheap IP cctv camera I just bought with no 
instructions.
I do "nmap -sn 10.0.0.0/16" to see if camera shows up
oddly finds PCs but gets "I'm here" from the windows PC but on the old 
IP address I had previously given it in windows networking thingamyjig.

any idea where this identification might be hanging about ?
everything works but it just doesn't look very tidy.

I should point out I don't really know what I'm doing.

mick



-- 
Key ID    4BFEBB31

[toc] | [next] | [standalone]

#196413

On 05/06/18 10:56, mick crane wrote:
> I changed the domain name for couple of home computers from "local" to 
> "home"
> one of them is win 10 PC.
> I have ipfire box doing hopefully firewall and DNS and so while I 
> changed domain I let all get address from its DHCP and gave them fixed 
> leases.
> I have 2 debian PCs
> I try to find IP address of a cheap IP cctv camera I just bought with no 
> instructions.
> I do "nmap -sn 10.0.0.0/16" to see if camera shows up
> oddly finds PCs but gets "I'm here" from the windows PC but on the old 
> IP address I had previously given it in windows networking thingamyjig.
> any idea where this identification might be hanging about ?
> everything works but it just doesn't look very tidy.
> I should point out I don't really know what I'm doing.
> mick

Your Windows PC will likely continue to use the static IP address set 
under Windows, as you told it to. If you want it to use a fixed IP 
address assigned for its MAC via DHCP, remove the IP address setting in 
Windows and let it use the address assigned via DHCP. Consumer-grade 
routers do not enforce IP address assignment so DHCP leases are just a 
suggestion (but like TCAS suggestions should be followed to avoid 
collisions).

The IP cctv camera might be getting its address from DHCP. You could try 
looking in your router DHCP lease table and eliminating known devices to 
deduce the IP and MAC address of the IP cctv camera. If you have no 
instructions or interface, I assume you have connected it over ethernet.

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]

#196417

On 6/5/2018 12:56 AM, mick crane wrote:
> I changed the domain name for couple of home computers from "local" to 
> "home"
> one of them is win 10 PC.
> I have ipfire box doing hopefully firewall and DNS and so while I 
> changed domain I let all get address from its DHCP and gave them fixed 
> leases.
> I have 2 debian PCs
> I try to find IP address of a cheap IP cctv camera I just bought with no 
> instructions.
> I do "nmap -sn 10.0.0.0/16" to see if camera shows up
> oddly finds PCs but gets "I'm here" from the windows PC but on the old 
> IP address I had previously given it in windows networking thingamyjig.
> 
> any idea where this identification might be hanging about ?
> everything works but it just doesn't look very tidy.
> 
> I should point out I don't really know what I'm doing.
> 

Welcome to the club, we've all been there!!! :)

You should look on the device on which you change the TLDS (local > 
home) for the dhcp leases and the log.

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#196422

On 2018-06-05 07:57, john doe wrote:
> On 6/5/2018 12:56 AM, mick crane wrote:
>> I changed the domain name for couple of home computers from "local" to 
>> "home"
>> one of them is win 10 PC.
>> I have ipfire box doing hopefully firewall and DNS and so while I 
>> changed domain I let all get address from its DHCP and gave them fixed 
>> leases.
>> I have 2 debian PCs
>> I try to find IP address of a cheap IP cctv camera I just bought with 
>> no instructions.
>> I do "nmap -sn 10.0.0.0/16" to see if camera shows up
>> oddly finds PCs but gets "I'm here" from the windows PC but on the old 
>> IP address I had previously given it in windows networking 
>> thingamyjig.
>> 
>> any idea where this identification might be hanging about ?
>> everything works but it just doesn't look very tidy.
>> 
>> I should point out I don't really know what I'm doing.
>> 
> 
> Welcome to the club, we've all been there!!! :)
> 
> You should look on the device on which you change the TLDS (local >
> home) for the dhcp leases and the log.
dear all,

I hold my hand up there was an entry in "hosts" GUI of ipfire PC about 
the old domain/ipaddress of windows PC but I swear I cleared out ipfire 
/etc/hosts so I dunno where that came from.

I think it might be something to do with arp cache on all the PCs  going
"I know about that"
Still no funny entries in nmap results now except windows PC doesn't 
show up at all but guess that is windows firewalling.

regards the CCTV camera is another thing. It's there but is not 
streaming on the ethernet, just the WIFI and appears to connect to cloud 
servers ( I'll leave that for another day ). my suspicion is that the 
Chinese are selling these off cheap to have a peek at European domestic 
habits.

mick





-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#196426

On 6/5/2018 12:20 PM, mick crane wrote:
> On 2018-06-05 07:57, john doe wrote:
>> On 6/5/2018 12:56 AM, mick crane wrote:
>>> I changed the domain name for couple of home computers from "local" 
>>> to "home"
>>> one of them is win 10 PC.
>>> I have ipfire box doing hopefully firewall and DNS and so while I 
>>> changed domain I let all get address from its DHCP and gave them 
>>> fixed leases.
>>> I have 2 debian PCs
>>> I try to find IP address of a cheap IP cctv camera I just bought with 
>>> no instructions.
>>> I do "nmap -sn 10.0.0.0/16" to see if camera shows up
>>> oddly finds PCs but gets "I'm here" from the windows PC but on the 
>>> old IP address I had previously given it in windows networking 
>>> thingamyjig.
>>>
>>> any idea where this identification might be hanging about ?
>>> everything works but it just doesn't look very tidy.
>>>
>>> I should point out I don't really know what I'm doing.
>>>
>>
>> Welcome to the club, we've all been there!!! :)
>>
>> You should look on the device on which you change the TLDS (local >
>> home) for the dhcp leases and the log.
> dear all,
> 
> I hold my hand up there was an entry in "hosts" GUI of ipfire PC about 
> the old domain/ipaddress of windows PC but I swear I cleared out ipfire 
> /etc/hosts so I dunno where that came from.

I would also look for advice on the IPFire forum:

https://www.ipfire.org/get-support

- Maybe restarting from scratch?
- Changing the TLDS could have consequences (mDNS)

> 
> I think it might be something to do with arp cache on all the PCs  going
> "I know about that"
> Still no funny entries in nmap results now except windows PC doesn't 
> show up at all but guess that is windows firewalling.
> 

For testing purposes, is it working with windows firewalling disable?

> regards the CCTV camera is another thing. It's there but is not 
> streaming on the ethernet, just the WIFI and appears to connect to cloud 
> servers ( I'll leave that for another day ). 
> 

Unlikely but the CCTV might not support dhcp.

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#196418

On Mon, 04 Jun 2018 23:56:21 +0100
mick crane <mick.crane@gmail.com> wrote:

> I changed the domain name for couple of home computers from "local"
> to "home"
> one of them is win 10 PC.
> I have ipfire box doing hopefully firewall and DNS and so while I 
> changed domain I let all get address from its DHCP and gave them
> fixed leases.
> I have 2 debian PCs
> I try to find IP address of a cheap IP cctv camera I just bought with
> no instructions.
> I do "nmap -sn 10.0.0.0/16" to see if camera shows up
> oddly finds PCs but gets "I'm here" from the windows PC but on the
> old IP address I had previously given it in windows networking
> thingamyjig.
> 
> any idea where this identification might be hanging about ?
> everything works but it just doesn't look very tidy.
> 
> I should point out I don't really know what I'm doing.
> 

Who does? Presumably you can find your way into Windows network
configuration, not that it helps much. I've never seen Win10, but I've
had 8 for a few years, and it's a pain to do network troubleshooting
with. It needs a real kicking to do what it's told. At the slightest
provocation, it will pick up an APIPA address, the one method
absolutely guaranteed to cut off all network communication. Windows 95
needed the installation CD in order to change IP address, but at least
it did what you told it to do.

So tick the boxes for getting network address and DNS automatically,
and to be on the safe side, also give it a fixed address in the network
outside the DHCP range, and flip over the page and do the same with the
alternate address. That will probably do the job, but reboot anyway,
it's Windows...

-- 
Joe

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web