On 10/06/2015 12:15 PM, Gordon Messmer wrote:
On 10/06/2015 09:13 AM, Robert Nichols wrote:
It's highly likely that it will simply use its only interface as
a default route, at least that's the way it worked for the two IP
cameras I set up that also had an initial IP address of 1.1.1.1.
That's not generally how IPv4 works. In the simple, most common
configuration, a device has an address and a netmask. For a device that
defaults to 1.1.1.1, that's probably either /8 or /24. In that case,
the device will be able to respond to addresses prefixed with 1.anything
or 1.1.1.anything, respectively.
It's technically possible that the device could have a 0.0.0.0/0 direct
route on its network interface, but it's extremely unlikely. I've never
seen a device configured that way by default. (Such a device would try
to resolve all addresses via ARP.) If a device were configured that
way, users probably wouldn't be instructed to use 1.1.1.2 as their own
address, as Bob was. And that's really the point: Bob stated the
requirement that he use 1.1.1.2 as his address, and adding a direct
route doesn't accomplish that.
I don't know that Bob actually said he HAD to use 1.1.1.2. My guess
(without knowing what the mysterious "device" is) is that the device
used 1.1.1.1/24 and it suggested he use 1.1.1.2 as his address. If that
was the case, than any 1.1.1.0/24 address (other than 1.1.1.1) would
work.
I think the proper way to do handle this (if this reset thing is going
to be ongoing) would be to:
1. Create a udev rule that uses the MAC addr of the NIC to tie
the device to a standardized name (e.g. "eth0"). I absolutely
detest this damned renaming of devices based on when they got
scanned by the kernel. It is a spectacularly idiotic idea and
the fact you can rename it in udev hints that the kernel
developers tacitly agree.
2. Create create an alias to that new name (e.g. "eth0:0").
3. Stick a permanent 1.1.1.2/24 address on that alias.
That way he can always get to 1.1.1.1 (with or without a gateway) since
the aliased NIC and the reset device will be on the same network.
The best solution is to set up the device so it is on the same network
as his machine and figure out why he has to reset it to factory
defaults all the time. I could possibly live with resets to a saved
configuration although I'd be rather annoyed. Having to reset to
factory defaults constantly would indicate the thing should be junked
because of a really poor design. Heaven knows what other nefarious
things it's doing (I sure hope this is all behind a firewall and you
monitor all network connections with something like snort).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Working with Linux is like wrestling with a worthy opponent. -
- Working with Windows is like picking on an annoyed child with a -
- loaded handgun. -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
