where is 192.168.7.2 ip address defined?

GoogleGroups
1

I am testing Beagle Black with several distros. Each time I change distro, my host ssl client complains that remote host key changed,
and refuses to let me log in, even though I specified no StrictHostKeyChecking in my .ssh/config file. I have to use ssh-agent
to remove the previous key.

I could possibly solve the problem by changing the target keys to the same values in all distros, but it might be simpler
just to change the ip addresses to be unique.

I tried changing the ip value to 192.168.7.3 in the target’s /etc/udhcp.conf file, but it had no effect.
Where else is the value defined?

BTW, can I turn off the target’s udhcpd if I am not using USB gadget? My Linux Mint host is preferring the wired connection to Beagle,
which does not see the Internet, to my wireless connection, which does.

2

Each install will change the machine name.
To make your machine forget the previous time you connected you can remove the known hosts file

rm ~/.ssh/knownhosts

However, this will remove all your known hosts and start fresh.

3

I found the place, it is set in /etc/udev/rules.d/udhcpd.rules

But to clarify the problem, what I wanted was to have each of several distros I test have a different IP address so that they
would appear to my desktop SSH system to be different machines, in the hope it would stop complaining about the remote
key having changed after I switch.

4

The usb0 configuration is set up in /opt/scripts/boot/am335x_evm.sh, which is called from the initd generic-boot-script.sh. The udhcpd server is started and reads configuration from /etc/udhcpd.conf. Change the netmask in udhcpd.conf and restart udhcpd. Then manually set the usb0 ip (for example): sudo ifconfig usb0 192.168.7.11 netmask 255.255.255.192 to select the IP from a larger range.

Or you can just hack am335x_evm.sh each time and reboot…

5

I found the place, it is set in /etc/udev/rules.d/udhcpd.rules

But to clarify the problem, what I wanted was to have each of several
distros I test have a different IP address so that they
would appear to my desktop SSH system to be different machines, in the
hope it would stop complaining about the remote
key having changed after I switch.

I am testing Beagle Black with several distros. Each time I change
distro, my host ssl client complains that remote host key changed,
and refuses to let me log in, even though I specified no
StrictHostKeyChecking in my .ssh/config file. I have to use ssh-agent
to remove the previous key.

I've found that 'StrictHostKeyChecking=no' is not sufficient, you need to
also use 'UserKnownHostsFile=/dev/null' in your config file. This works for
me on linux systems running openssh and logging into systems that regularly
change keys (e.g. reimaging during debug/dev cycles).

Ted Roth