Until a couple of days ago, I used to use Gnome network-admin’s ability of having multiple network profiles to configure my wifi card at work and at home. But yesterday, the program went crazy and started to crash without any logical reason and I decided to shift to another solution: logical network interface mapping.<\/p>\n
Interface mapping is a feature of ifupdown (\/etc\/network\/interfaces). You can define some logical interfaces and call a script in order to choose which one will be mapped to a physical interface. The \/etc\/network\/interfaces could be like this one (being HomeNET and WorkNET two existing ESSID network identifiers):<\/p>\n
auto eth1
\nmapping eth1
\nscript \/root\/WIFI\/wldetect.sh
\nmap HomeNET HomeNET
\nmap WorkNET WorkNET<\/p>\niface HomeNET inet static
\naddress 192.168.1.2
\nnetmask 255.255.255.0
\ngateway 192.168.1.1
\nwireless-essid HomeNET
\nwireless-key s:mysecretpass1 open
\ndns-nameservers 127.0.0.1 192.168.1.1<\/p>\niface WorkNET inet dhcp
\nwireless-essid WorkNET
\nwireless-key s:mysecretpass2 open
\ndns-nameservers 127.0.0.1 192.168.100.1<\/p><\/blockquote>\nI’m using resolvconf to activate the dns-nameservers directive in the interfaces file, and dnsmasq to take care of some dns issues with a couple of VPNs I use. That explains the first 127.0.0.1 entry.<\/p>\n
The script \/root\/WIFI\/wldetect.sh lists the available networks and chooses one of them being in a whitelist (HomeNET|WorkNET):<\/p>\n
#!\/bin\/sh<\/p>\n
# Config
\nWL_IFACE=`iwconfig 2>\/dev\/null | { read A _; echo $A; };`<\/p>\n# Reset the interface
\nifconfig $WL_IFACE down
\nifconfig $WL_IFACE 0.0.0.0
\nifconfig $WL_IFACE up<\/p>\n# Search networks
\nNETWORKS=`iwlist $WL_IFACE scanning | grep ESSID | sed -e ‘s\/.*”(.*)”\/1\/’`<\/p>\n# Bring down the interface
\nifconfig $WL_IFACE down<\/p>\n# Select preferred networks
\nfor NET in $NETWORKS
\ndo
\ncase $NET in
\nHomeNEt|WorkNET)
\necho $NET;
\nexit 0;
\n;;
\nesac
\ndone
\nexit 1;<\/p><\/blockquote>\nAnd that’s all! I hope that this configuration could be helpful for someone.<\/p>\n","protected":false},"excerpt":{"rendered":"
Until a couple of days ago, I used to use Gnome network-admin’s ability of having multiple network profiles to configure my wifi card at work and at home. But yesterday, the program went crazy and started to crash without any logical reason and I decided to shift to another solution: logical network interface mapping. Interface … Continue reading My own flavour of network config automatic choosing<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts\/59"}],"collection":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/comments?post=59"}],"version-history":[{"count":1,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts\/59\/revisions"}],"predecessor-version":[{"id":440,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts\/59\/revisions\/440"}],"wp:attachment":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/media?parent=59"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/categories?post=59"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/tags?post=59"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}