</pre>

</pre>

You can change it to use whatever IP's you want to assign to different USB device ID's.  It's a little gross to have them hardcoded like that; it should use some stuff in /etc/conf.d instead, I suppose.  But it works for me.  The whole thing is an inelegant hack, and maybe in the future distros will make stuff like this easier by a completely different mechanism.  Maybe there is a way that /sbin/hotplug could call a script that has the USB device ID in its name, if such a script exists; but it needs to be done after the modprobe, and anyway this idea clashes with the general use of /etc/init.d scripts to do such configuration.  The problem is that AFAICT, the USB device ID that was just hotplugged is not available to the init.d script, and it really should be.  Which is why I had to write it in /tmp.

You can change it to use whatever IP's you want to assign to different USB device ID's.  It's a little gross to have them hardcoded like that; it should use some stuff in /etc/conf.d instead, I suppose.  But it works for me.  The whole thing is an inelegant hack, and maybe in the future distros will make stuff like this easier by a completely different mechanism.  Maybe there is a way that /sbin/hotplug could call a script that has the USB device ID in its name, if such a script exists; but it needs to be done after the modprobe, and anyway this idea clashes with the general use of /etc/init.d scripts to do such configuration.  The problem is that AFAICT, the USB device ID that was just hotplugged is not available to the init.d script, and it really should be.  Which is why I had to write it in /tmp.