2014-08-13 23:32 GMT+04:00 patrick keshishian <[email protected]>: > Hi, > > Since you did ask for input. > > On Wed, Aug 13, 2014 at 07:06:23PM +0400, Vadim Zhukov wrote: >> Hello all. >> >> I won't describe the problem, you all new it: when you switch between >> hotspots, your network interface doesn't follow you. Also, you >> probably want to have some sort of fallback configuration. >> >> Maybe you have a bunch of shell scripts, or whatever, - all this stuff >> that rely on ifconfig(8) output, and thus tend to break on crazy > > I did when I worked for a company and my laptop went to work > and came back home. They were simple scripts, did not do any > auto-anything. I would simply do: > > $ sh workwifi.sh # at employer > $ sh homewifi.sh # at home > $ sh momdadwifi.sh # at my parents' home > > You can get fancier than this if you really need to be. > All the necessary tools exist on the base OS. > >> network names. Sometimes you probably asked yourself, why there is no >> NetworkManager analog in OpenBSD? - So here is a try of constructing >> an answer to ths question. > > No, never. In fact, the opposite. Every time I come across > a daemon/"manager" I wonder "is this really necessary?"
For whom how. For example, I want it to try _known_ networks automatically, and I want to have immediate indication in case of network failure. You can twiddle with ifstated(8) or whatever for this, but it will be unreliable and ugly. > To me, the elegance of OpenBSD has always been in its > simplicity. It provides all necessary tools to its users. > The users are free to build the more sophisticated tools > (e.g., ones found in ports/packages). > > This leaves OpenBSD uncluttered. Unlike some other OSes, > e.g., MacOS X, inundated with countless processes, busy > doing ... something, I'm sure. And what and why in the > world are "those two" sending and receiving over my network? > > Every time I take a look at the process list on my MBP > I get this depressed, grossed-out, disgusted feeling. FYI: the current implementation will be reworked eventually (hope this will be soon, but don't hold your breath) - I got input from many people, including other developers, and have a lot of things to do now. And autonetd won't do anything without your explicit request. So don't worry, it's not worse than ifstated(8). ;) >> The internal logic is simple: scan networks, find known one and try to >> run ifconfig(8) (and, probably, dhclient(8) and/or route(8)) on it. I >> tried to avoid creating another rich parser syntax - all of the lines >> you set up in configuration file became command-line arguments of >> corresponding utilities. >> >> I invite you to look at the current source code here: >> >> cvs -d [email protected]:/cvs checkout autonetd >> >> Maybe this will evolve into backend of some GUI, or whatever. Maybe >> not. But at least it works much better than what I've had before. >> >> Any input is highly appreciated. Thank you for your time! -- WBR, Vadim Zhukov
