Hi all, I propose two configuration files for the following purposes: a) a blacklist file for wifi sources users do not want to connect to automatically b) a device mapping file to allow users of uncommon hardware configurations use networking devices other than wlan0 and eth0.
a) would take the form: myfirsthorridessid mrmiserymiseressid b) would take the form: wlanX=1 ethX=2 Edward On 15/09/2015, Edward Bartolo <edb...@gmail.com> wrote: > Hi all, > > Obviously, the major disadvantage of using my proposed 'solution', is > users must decide which physical network interfaces to use and stick > with their decision afterwards. > > Edward > > On 15/09/2015, Edward Bartolo <edb...@gmail.com> wrote: >> Hi all, >> >> Although at the moment I am occupied with other commitments, I would >> to discuss how support for uncommon systems with more than one wifi >> adaptor and/or with more than one wired network adaptor. >> >> The main drawback supporting such systems is that the GUI has to >> account for them and this makes it more complicated for the end user >> who almost seldom will be faced by the situation of having to deal >> with more than one wifi card and/or more than one wired connector on >> the same system. >> >> I am assuming these type of unfortunate users should already be >> comfortable tweaking there system, so I am suggesting that the backend >> would be made behave differently in extraordinary situations like >> these. Instead of defaulting on wlan0 and eth0, power users would opt >> to use wlan1 or eth1. For this, a simple text configuration file >> mapping wlanX to wlan1 and ethX to eth1 should provide a simple and >> yet neat solution without editing too much of the already working >> code. >> >> This is my first concept of how support for uncommon systems can be >> added without too much disruption of the already working code. >> >> Edward >> > _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng