Openwrt Setting Wi-Fi access points. Install Openwrt
Step-by-step instructions for the firmware and initial adjustment of the OpenWrt access point using the example of TP-Link TL-WA901ND V2
Manufacturers such as ASUS, D-LINK, TP-LINK and others produce firmware for their products a limited amount of time. This means that vulnerabilities and bugs remain in their place for years. over, your native firmware of your device can work poorly.
I have at the disposal of 5 points of access to TP-LINK models TL-WA901ND V2. The last firmware for her was 23.03.2012. This firmware works unstable. In the English version of the site there is a beta-interrogation dating 1.eleven.2013, Changelog indicates “Fixed the Wireless Instabide and Hang Issue”. this is not true, with this firmware the point is still unstable.
OpenWrt. access point configuration (TL-WR740N)
But the points are purchased and they must work. What to do? Put back and buy unifi to grind OpenWRT and hopes that with it they will stably serve customers.
The DD-WRT project also has a firmware for this point, but I do not recommend it to put it. There is a problem with the work of Ethernet port.
And so, the OpenWrt project about once a year produces stable firmware issues. At the moment, the last issue of Barrier Breaker 14.07 I went out in October 2014.
In order to flash our point on the website https: // openwrt.Org in the catalog https: // downloads.Openwrt.org/barrier_breaker/14.07/AR71XX/GENERIC/Find a point model and download the Factory postfix file
We go to the point through the web-intake. System Tools \ Firmware Upgrade select a downloaded file with extension.bin and click upgrade
After some time, the point will reboot and Openwrt will be ready to work. To get access to the command line TD, we need to connect the point and computer integration. On the computer integration, the address from the subnet 192 should be statically set.168.one.0/24 and mask /24, for example 192.168.one. 2 ⁄24
Now we connect to the point using Telnet: Telnet 192.168.one.one
To be able to control the access point, you need to set the password for the superpower. Command Passwd, enter the password and confirm it.

Now you need to change the config network: VI /etc /network. We use a DHCP server and Network will find the following view:
LOOPBACK Inte Weopback Inte Weep. Let’s leave it unchanged
From the LAN integration, we need to get the network settings from the DHCP server and work in the bridge mode.
Now you should restart the LAN Inte Wee and leave the Telnet session. The easiest way to do this is to send a point to rebooting Reboot.
Now you need to connect an access point to the working network and go to it by ssh. On the DHCP server, tie the MAC address TD to a specific IP address, for the convenience of further work. For example, we will highlight the Wi-Fi guest network of a separate VLAN and hang on it a network 192.168.5.0/24. And place access points at the end of the target pool. Our point on the DHCP server will set the address 192.168.5.250
We go to our point on SSH: on the Unix-like OS command in the terminal: ssh root@192.168.5.250. Windows will require Putty for this. Root login, password given earlier.
In the standard firmware version 14.07 for TL-WA901ND V2 in the firmware, the Luci web-intese is already included. Settings can be carried out through it: http: // 192.168.5.250
To Russify the web-intake, you need to install the Luci-I18N-RUSSIAN package:
OPKG Update. upgrade the list of packages in the OpenWrt repository. If the update does not work, check if the device has access to the global network.
OPKG Instal Luci-I18n-Russian-Rusifier installation
It can also be done through a web-integer.
The following described the method of configuration through the command line with the correction of configs manually. The web-integer is disabled.
We want to get very little from our point: so that Wi-Fi worked and be open so that TD time is synchronized with the NTP server and that our guests from 192.168.5.0/24 The subnets did not have access to the command line of our point.
Continue. The wireless network settings are stored in/etc/config/wireless and gain the following view:
Option Channel. Channel number on which TD will work
Option Hwmode. TD operating mode. For a public point, it is better to leave the 11ng mode.
Country. the country in which the TD is located.
Option Disabled 1-Wi-Fi work ban right in the config. To resolve Wi-Fi, you need to delete / make this line.
Option Ssid. SSID of our network

Option Encryption. choice of TD encryption method. In our example, the access point is open
System settings are stored in/etc/config/system
Option Hostname. set the network name of our device
Option Zonename. set a time zone
Option Timezone. Novosibirsk today GMT 6
Config Timeserver ‘Ntp’ spells out time servers that will synchronize time
Option Enabled. Turn on (1) Turn off (0) NTP client
Option Enable_Server. Turn on (1) Turn off (0) NTP server. t.e. When this parameter is turned on, the NTP server becomes
Firewall setting. We do not need anything special from him, because all the restrictions for 192.168.5.0/24 set on the router. We will only add to the config/etc/config/firewall one rule that blocks access to port 22 of our TD:
Option Name. Name of Rules
Option Proto. Protocol with which it works
Option SRC. Source. Here you can put a zone, intese. Asterisk means “any”
Option SRC_IP. IP source address. We have all this subnet of guest wi-fi.
Option Dest_ip. IP appointment address. The address of our point

Option Dest_Port. Port destination. We need to close access through SSH, the port by default 22.
Option Target. the action “What to do?””. Reject. clearly makes it clear to our guest that there is no access. You can put Drop and get an atmosphere of mystery.
Gentoo on the Laptop
Today we will talk about the guest Wi-Fi network. First, let’s figure out what it is. On any Wi-Fi router (C OpenWRT), whether it is one- or two-band you can create several Wi-Fi networks. This is often done in order to protect part of the users connected over the network from the intracity, but to provide Internet access. We will set up a similar network today for the example of the TrUNC version of OpenWRT “Chaos Claimer”.
To begin with, let’s go to the “Network” tab. “Wi-Fi” and click “Add” near the intense for which we are going to create a network. In my case, it is “Radio1”.
Now go to the “Network” tab. “Inteys” and click “Add a new Inte Week”. Next, we give him the name “guest” and tie it to the guest Wi-Fi network. Click “Apply”.
Now in the “Protocol” field we select a “static address”, then click the “Change the Protocol” button and see the list of settings. We indicate as IPV4 addresses 192.168.2.one. Here you can indicate something more than the same, but the already involved addresses of addresses should be avoided, such as, for example, as 192.168.one.x or ten.0.0.x (can be involved for OpenVPN). As a mask of the network, I used 255.255.255.0.
Now let’s set DHCP server. Click on the “Request DHCP” button “.
Configure Firewall. Let’s go to the Network tab. “Interspective screen” and in the section “Zones” we click “add”. We write the name “Guest”, after which we will choose to “reject” for the option of the traffic redirect, and for the incoming and outgoing. “accept”. Below we note the “redirection between the zones”: “Allow redirecting to the destination: WAN”.
Now let’s configure Firewall for the normal operation of DHCP and DNS services in our network. To do this, go to the “Rules for Traffic” tab and choose “open ports on the router”. Next, select 53 port for TCP/UDP protocols and sign it “guest dns”. Near the new entry, click “Edit”. Install the “Source Zone”: “Guest”, “Washer Zone”: “device (input)”.
Openwrt Accesspoint / Wi-Fi Configuration Tutorial
Openwrt is Currently the Best Operating System for Running High-Throughput, Open-Source Wi-Fi Access Points. It has a Full 802.11a/b/g/n/ac Support Out of the Box.
PFSENSE and OPNSENSE DONIT SUPPORT The 802.11ac mode yet. IPFire Supports 802.11ac Only Partially, with Much Worse Performance.
IF You Want to Run a Reliable and High-Permancation Wi-Fi Access Point, Openwrt is the Best Solution.
Install Hostapd and Firmware Drivers for Your Network Card (S)
In the Web Interface, Go to System-Software and Search for “Hostapd”.
In the Same Manner, Install Drivers and Firmware for Your Network Cards.

IF YOU HAVE WLE200NX, You Will Need the Following Packages:
IF YOU HAVE WLE600VX OR WLE900VX YOU Will NEED THESE PACKAGES:
Once Packages are Installed, Reboot Your Router.
Now You Shoup Be Able to See a New Menu item in Network. Wireless.
Here’s OUR Configuration for wle600vx and wle900vx.
- Operating Frequency AC Mode, Channel 36, Width: 80MHz
- Transmit Power: 23 DBM (199mw)
- Essid: Teklagorac
- Wireless Security: WPA2-PSK
- Key: Teklager123
- Country Code: Se (Make Sure to Set it, Otherwise The Cards May Show “Wireless is Disabled”)
Openwrt Allows The User To Choose Many Different Channels for Wireless Networks. Most of these Channels are A Bad Choice Becake They Overlap on Two Or Standard Channels.
For 80mhz width, The Good Channels Are: 36, 52, 100, 116, 132, 149.
For 40MHZ WIDTH, We have Twice as Many “Good” Channels: 36, 44, 52, 60, 100, 108, 116, 124, 132, 140, 149, 157.
Make Sure to Set the Country Code to Your Country. SOME of the ABOVE CHANNELS MAY NOT Be Permited in Your Country.
This configured the card in the Full 802.11AC Mode with A Full 80MHZ Channel.
Theoretically, You Shoup Be Able to get 867mbit/s on this Connection.
In OUR TESTS, We Get 520Mbit/S Which is the Highest Throughput We Have Seen Ony Commercial Or Open-Source Device. OUR Test Was Performed BetWeen APU3 with wle600vx and Samsung Galaxy S7 Smartphone. Perhaps Even Higher Throughput Can Be Achieved with A Different Device.
Half-Gigabit Wi-Fi Throughput Is Truly Amazing. Kudos to the Openwrt Team!
Openwrt Wi-Fi: How to install and configure on a router
Hi all! Congratulations on the successful firmware of your old router. Let me remind you that OpenWRT is an additional firmware that opens wider opportunities for some routers. Today I will tell you about the usual OpenWRT configuration through the Luci Web-Inteatheis. If you have not yet installed this firmware, then we look at the first chapter of this article.
We go to the official page. Next, you will see a table with all supported devices. We find your own router according to the model. you can clarify the model by looking at the label, which is closed at the bottom of the body of the apparatus. Next, we need a column “Firmware Openwrt Install URL”. a link to download the firmware file will be stored there there. The file will have an extension “Bin” or “IMG”.
Next, you need to go to the route of the router. Most often, it is enough to enter the IP address to the address line of any browser for this. At the same time, you must be connected to the router.
If you do not know how to enter the settings of the router read this instruction.
Next, you need to find the section “System”, where it is updated for the apparatus. On the same TP-LINK, this is done in the “System Tools” section-“Built-in Poe Update”-Next, click “Select the file”, click on our file and update the system.
All routers are done in the same way, but if you get confused, then we look at this instruction.
Internet and Wi-Fi Internet setting
To enter the Inte we use the standard IP address:
After that you will be asked to enter a password. By default, “Root” will be as a login. There is no need to introduce anything in the Password field, just click on the Login button.
I advise you to immediately change the administrator’s password. we move to System. “Administrator Password”, enter a new value twice and click on the Submit button. Let me remind you that the main login:
Not “admin” as on standard firmware.
Now we are going to configure the Internet: “Network”. “Interface”. “WAN”. in the “Protocol” field, select the type of connection used by the provider. Next, we enter additional information below for authorization on the provider network. All these data can be found in the technical support of the provider, as well as in the contract.
NOTE! If there is no information in the contract, then most likely your provider uses a dynamic IP. we put “DHCP”
If the Internet works, then we go to configure Wi-Fi. We go to the first “Radio: 0”.
In the “Device Configuration” section, set Channel in the Auto mode, but if you know a free channel, you can set it manually. In the line “Transmit Power” we set the maximum power of the transmitter. Let me remind you that you should not always put power to the maximum. Radio waves, like any other waves, love to reflect and create interference. therefore, in a small apartment this value can be reduced.
On the Basic Settings tab, we install Mode. these are the modes that will be supported by the router. We install the channel below, it is better to leave the default “20MHz”. Also establish the country so that the router establishes the threshold of amplification of the antennas.
Now we go to the Interface Configuration section and install the name of your wireless network on the General tab. You can also hide the network by installing the Hide Essid check. By default, it costs “Mode” as “Access Point” (access points).
Now go to the Wireless Security tab. By default, there will be no password to install it, indicate in the “Encryption” field “WPA2-PSK” encryption mode and enter the key below.
As you can see, the OpenWRT setup is made similarly as on other firmware. If you have questions, then ask them in the Комментарии и мнения владельцев.
Openwrt Setting Wi-Fi access points
If you sewed your device with Openwrt firmware after a rebut, you need to configure it to work on your network for this, edit the facet Network VI ETC/Config/Network
Copy the given settings at the editor window. Perform ESC.- : wq Let’s restart the network with new settings /etc/init.D/Network Restart
Determine for viewing
Config DHCP LAN Option Interface Lan Option Start 100 Option Limit 150 Option Leasetime 12h
Config Zone Option Name Lan Option Network ‘Lan’ Option Input Accep Output AcCCEPT Option Forward Reject
Config Zone Option Name Wan Option Network ‘Wan’ Option Input Reject Output Accept Forward Reject Option Masq 1 Option Mtu_fix 1
Config Forwarding Option SRC Lan Option Dest Wan
# We Need to Accept UDP Packets on Port 68, # See https: // DEV.Openwrt.org/Ticket/Ticket/4108 Config Rule Option Name Allow-DHCP-RENEW OPTION SRC Wan Option Proto UDP Option Dest_Port 68 Option Target Accept Option Famile IPV4
# Allow IPV4 Ping Config Rule Option Name Allow-Ping Option SRC Wan Option Proto ICMP OPTYPE ECHO-RECET OPTION FAMILY IPV4 Option Target Accepts
# Allow DHCPV6 Replies # See https: // DEV.Openwrt.org/ticket/10381 config rule option name Allow-DHCPv6 option src wan option proto udp option src_ip fe80::/10 option src_port 547 option dest_ip fe80::/10 option dest_port 546 option family ipv6 option target ACCEPT
# Allow essential incoming IPv6 ICMP traffic config rule option name Allow-ICMPv6-Input option src wan option proto icmp list icmp_type Echo-request list icmp_type Echo-reply list icmp_type destination-unreachable list icmp_type packet-too-big list icmp_type time-exceeded list icmp_type bad-header list icmp_type unknown-header-type list icmp_type router-solicitation list icmp_type neighbour-solicitation list icmp_type router-advertisement list icmp_type neighbour-advertisement option limit 1000/sec option family ipv6 option target ACCEPT
# Allow essential forwarded IPv6 ICMP traffic config rule option name Allow-ICMPv6-Forward option src wan option dest option proto icmp list icmp_type Echo-request list icmp_type Echo-reply list icmp_type destination-unreachable list icmp_type packet-too-big list icmp_type time- ExcEEDEDEDED ICMP_TYPE BAD-HeADER LIST ICMP_TYPE Unknown-Header-Type Option Limit 1000/SEC Option Family IPV6 Option Target Accept
# Include a File with Users Custom Iptables Rules Config Include Option Path /etc /Firewall.user
### Example Config Section # Do Not Allow a Specific IP to Access Wan #Config Rule # Option SRC LAN # Option Src_ip 192.168.45.2 # Option Dest Wan # Option Proto TCP # Option Target Reject
# BLOCK A SPECIC MAC on Wan #Config Rule #Cation Dest Wan # option SRC_MAC 00: 11: 22: 33: 44: 66 # Option Target Reject
# Block Incoming ICMP Traffic on a Zone #Config Rule # Option SRC LAN # Option Proto ICMP # Option Target Dropet
# Port REDIRECT PORT COMING in LAN #Config Redirect # Option SRC Wan # Option SRC_DPORT 80 # Option Dest Lan # Option Dest_ip 192.168.16.235 # Option Dest_Port 80 # Option Proto TCP
# Port Redirect of Remapped SSH Port (22001) on Wan #Config Redirect # Option SRC Wan # Option SRC_DPORT 22001 # Option Dest Lan # Option Dest_Port 22 # Option Proto TCP
# Allow IPSEC/ESP and ISAKMP PASSTHROUGH #CONFIG RULE # OPTION SRC Wan # Option Dest Lan # Option Protocol ESP # Option Target Accept
#Config Rule # Option SRC Wan # Option Dest Lan # Option SRC_Port 500 # Option Dest_Port 500 # Option Proto UDP # Option Target Accept
### Full Config Section #Config Rule # Option SRC LAN # Option SRC_IP 192.168.45.2 # Option SRC_MAC 00: 11: 22: 33: 44: 55 # Option SRC_Port 80 # Option Dest Wan # Option Dest_ip 194.25.2.129 # Option Dest_Port 120 # Option Proto TCP # Option Target Reject
Openwrt Setting Wi-Fi access points
If you sewed your device with Openwrt firmware after a rebut, you need to configure it to work on your network for this, edit the facet Network VI ETC/Config/Network
Copy the given settings at the editor window. Perform ESC.- : wq Let’s restart the network with new settings /etc/init.D/Network Restart
Determine for viewing
Config DHCP LAN Option Interface Lan Option Start 100 Option Limit 150 Option Leasetime 12h
Config Zone Option Name Lan Option Network ‘Lan’ Option Input Accep Output AcCCEPT Option Forward Reject
Config Zone Option Name Wan Option Network ‘Wan’ Option Input Reject Output Accept Forward Reject Option Masq 1 Option Mtu_fix 1
Config Forwarding Option SRC Lan Option Dest Wan
# We Need to Accept UDP Packets on Port 68, # See https: // DEV.Openwrt.org/Ticket/Ticket/4108 Config Rule Option Name Allow-DHCP-RENEW OPTION SRC Wan Option Proto UDP Option Dest_Port 68 Option Target Accept Option Famile IPV4
# Allow IPV4 Ping Config Rule Option Name Allow-Ping Option SRC Wan Option Proto ICMP OPTYPE ECHO-RECET OPTION FAMILY IPV4 Option Target Accepts
# Allow DHCPV6 Replies # See https: // DEV.Openwrt.org/ticket/10381 config rule option name Allow-DHCPv6 option src wan option proto udp option src_ip fe80::/10 option src_port 547 option dest_ip fe80::/10 option dest_port 546 option family ipv6 option target ACCEPT
# Allow essential incoming IPv6 ICMP traffic config rule option name Allow-ICMPv6-Input option src wan option proto icmp list icmp_type Echo-request list icmp_type Echo-reply list icmp_type destination-unreachable list icmp_type packet-too-big list icmp_type time-exceeded list icmp_type bad-header list icmp_type unknown-header-type list icmp_type router-solicitation list icmp_type neighbour-solicitation list icmp_type router-advertisement list icmp_type neighbour-advertisement option limit 1000/sec option family ipv6 option target ACCEPT
# Allow essential forwarded IPv6 ICMP traffic config rule option name Allow-ICMPv6-Forward option src wan option dest option proto icmp list icmp_type Echo-request list icmp_type Echo-reply list icmp_type destination-unreachable list icmp_type packet-too-big list icmp_type time- ExcEEDEDEDED ICMP_TYPE BAD-HeADER LIST ICMP_TYPE Unknown-Header-Type Option Limit 1000/SEC Option Family IPV6 Option Target Accept
# Include a File with Users Custom Iptables Rules Config Include Option Path /etc /Firewall.user
### Example Config Section # Do Not Allow a Specific IP to Access Wan #Config Rule # Option SRC LAN # Option Src_ip 192.168.45.2 # Option Dest Wan # Option Proto TCP # Option Target Reject
# BLOCK A SPECIC MAC on Wan #Config Rule #Cation Dest Wan # option SRC_MAC 00: 11: 22: 33: 44: 66 # Option Target Reject
# Block Incoming ICMP Traffic on a Zone #Config Rule # Option SRC LAN # Option Proto ICMP # Option Target Dropet
# Port REDIRECT PORT COMING in LAN #Config Redirect # Option SRC Wan # Option SRC_DPORT 80 # Option Dest Lan # Option Dest_ip 192.168.16.235 # Option Dest_Port 80 # Option Proto TCP
# Port Redirect of Remapped SSH Port (22001) on Wan #Config Redirect # Option SRC Wan # Option SRC_DPORT 22001 # Option Dest Lan # Option Dest_Port 22 # Option Proto TCP
# Allow IPSEC/ESP and ISAKMP PASSTHROUGH #CONFIG RULE # OPTION SRC Wan # Option Dest Lan # Option Protocol ESP # Option Target Accept
#Config Rule # Option SRC Wan # Option Dest Lan # Option SRC_Port 500 # Option Dest_Port 500 # Option Proto UDP # Option Target Accept
### Full Config Section #Config Rule # Option SRC LAN # Option SRC_IP 192.168.45.2 # Option SRC_MAC 00: 11: 22: 33: 44: 55 # Option SRC_Port 80 # Option Dest Wan # Option Dest_ip 194.25.2.129 # Option Dest_Port 120 # Option Proto TCP # Option Target Reject
Fast roaming (802.11r) in Wi-Fi networks based on LEDE (AKA Openwrt)
Hi all. I decided to fix the result by writing an article. And this result is a unification of several Wi-Fi access points into a network into one inextricable network, it is also called seamless. The meaning of this action was that my “local” home network grew to several Wi-Fi points due to its (network) of large area and the inability to achieve proper quality with only one point.
SETUP WIFI IN OPENWRT
The first and frontal solution was to put a few more Wi-Fi AP with the same BSSID and it seemed to work in appearance, but as it turned out not everything. For example, my Android Based phone normally digested this situation by jumping from point to point when the signal was lost and the signal is detected from the other, but users of the wonderful Yafon had a problem with this, this devices completely refused to disconnect from the radius of the point of action and connect to a new, albeit with a more fat signal. Well, as the contingent relies (no hostility. just dry facts) the stench began that everything around. My wonderful telephone cannot work with this junk. And I began to look for methods for combating this.
My search led me to the standard 802.11r. In which we are promised complete transparency for Wi-Fi network devices of their several APs. And even Apple confirms that he knows how.
Well, for the sake of the calm of our souls and lovers of apples, we will master the new discipline. A fluent study of theory and practice showed that Hostapd seems to be able to this miracle. All my routers have long been on LEDE (who is not in the know, this is the former OpenwRT), and no matter how in this connection the setting should not have created problems. But as always, not everything is so simple, or I’m tight 🙂
To begin with, the default LEDE set the WPAD-Mini package, it contains the main support of the Wi-Fi AP with a minimum of possible, so that it works so that it works. This alignment does not suit me. Therefore, it is necessary to replace the package with WPAD.
In the simplest case, you need to execute the command:
The package will attract everything you need and replace WPAD-Mini. In the ideal version, it is not bad just to move the image of the firmware by Imagebuilder firmware.
After installing the package, you need to configure it. If you use the Luci Inte Wee, then in the Wi-Fi network settings in the Wireless Security section, a checkmark will appear Enables Fast Roaming Among Access Points that Belong to the Same Mobility Domain.
Having turned on which we are provided with a bunch of fields to configure roaming function between AP. If you do not have Luci or you prefer to configure the piece of iron by changing the coffigs, then this is done by a line:
In the section Config Wi-Fi-Giface configuration file /etc/config/wireless. I hope you do not need to explain that this must be done on all AP participants in roaming.
It was the simplest. But then the fun began.
To explain to all points that they should somehow set up this business in one roaming. All the manuals that I managed to find stubbornly boil down to setting up this whole case using radius authorization. But I don’t have Radius and I don’t need it, as I think, most of us. Therefore, I had to examine.
Let’s go through the fields that we are offering to fill in Luci:
NAS ID. As I understand it, the identifier of the current access point in the Radius server. And it is not necessary in the absence of the latter, but Luci does not allow to save the settings if this field is not filled. Well, we will fill. Usually everyone recommends entering the MAC address of the device without separators there.
Mobility Domain. identifier specifically for your network. There should be one points involved in roaming. It is a 16.bit number in a hexadecetiric form (HEX).
External R0 Key Holder List. here they will participate NAS ID, And they said only for Radius. Or this function does not participate without Radius? Explain who is in the know? Here I added as many lines as I have access points to the network. In format: MAC address, NAS-ID, 128-bit key in the form of HEX line For example: 12: Fe: ED: 6D: EA, 12FED6DBFEA, 8A7FC966ED0691FF2809E1F38C16996 and so several times with each access point, I used the same key. Too, if anyone is in the know how right?
External R1 Key Holder List-an analogue of the previous section, only instead of NAS-ID R1KH.ID.
I filled it out like this: 12: Fe: Ed: 6D: BF: EA, 12: Fe: Ed: 6D: BF: EA, 8A7FC96691FF2809E1F38C169996
Preserving and rebooting all the devices not the first glance continued to work. On my phone with Android, nothing has changed. IPhone owners are still satisfied. we will observe. Wi-Fi analyzer sees my network as before several points, but in addition to WPA-PSK authorization, FT-PSK was added.
I wrote an article, so as not to lose the found myself and to get criticism and help in the understanding of what was done 🙂 I will be grateful for any Комментарии и мнения владельцев.
Create a script of auto starting.
Launch scripts should lie in the /etc /init folder.D/. Create a file /etc /init.D/CJDNS:
Start and STOP determine the sequence of script starting at start and off the router. “Start”. a set of commands executed to launch something. “Stop”. for stopping. Honestly, I poorly understand how the functionality of the script starts can help when turning off, if the routers are usually turned off, simply pulling out of the outlet, and the corresponding button is usually not provided for. Actually, the latest versions of CJDNS provide for the Pidfile config option, but this change is not yet in the Master branch, from which it is collected under Openwrt. Now it remains to do
You can read more about starting scripts in OpenWRT here: wiki.Openwrt.org/doc/techref/initscripts
Fuh, it seems, everything. Successful firmware, and may not you work after it to work as a soldering iron!
UPD: CJDNS developers in the last commite for assembly scripts rubbed all files and in Readme.MD left the message that from now on we need to use assembly scripts from the Sitlovites.
UPD2: The Sitl version of the package did not work for me.
- They decided to make a config in UCI format. This, of course, is good, but their JSON-UCI configi converter, written on Lua, does not find all the necessary libraries, despite the fact that they were just in, but a little different place. Their copying and creation of Links did not help. Now swears for errors in libraries.
- It was not possible to start cjdrote manually. As it turned out later, he was going from the Cracehe branch.
- In their Init script, features are used with might and main, which so far are only in TrUNC.
- All this takes a lot of memory together. However, a decrease in the occupied amount of memory is in their TODO.
The volume of work done impressed me, and the implementation, it seems, is not bad. So I wish them good luck in their endeavors. But somehow it is still necessary to collect, so I decided to clean Makefile and make my Init script. I also removed everything from there, except in general, I got a lightweight version. Here it is: github.COM/Dinoasm/CJDNS-OPENWRT-TINY to collect, add to Feeds.Conf this line:
Setting up network intenses
Configuration file./etc/config/Network. In the simplest case, the setting of the network looks like this:
Where LAN is the role of this intese. It is needed for that it would be possible to abstract from the name of the intenses. For example, you can indicate in Faerwol that all incoming traffic C Lan. An example of adding a static route:
I note that the Inte we must specify. An example of tuning for vumors and adding it to Bridge:
Will create an BR-GUEST integral and include ETH1 integust.123 (123 VLAN-AID on the ETH1 Inteiis). Below will be an example of how to add a wireless integral to this bridge. Since chipsets used in routers usually have 1-2 Ethernet ports, and I want more, you use separate controller for Ethernet. It is connected by one port to the main chipset, and the rest out. Directly in the network system such a software switch is not represented in any way. The switch can be configured through the Swconfig utility, or through UCI. Suppose we have one Ethernet port ETH0 connected to the 5th port of the controlled switch:
Here ETH0 is the name of the integration where the switch is connected. In the first section, we include the switch and include support for the teghilized (traffic with humans) traffic. Each Switch_vlan section is responsible for the specific VLAN specified in the VLAN option. This tag will be used to add labels for the ports specified in the Ports section. The letter T at the port indicates that the traffic to this port should be transmitted by the tag (with a mark), it will fall into the rest of the listed ports without a mark. Record ‘0 1 2 5t’ must be read as follows: Pass the non.value traffic from ports 0, 1, 2 to port 5 with a mark 0. Since VLAN with a tag 0 is the same as traffic without a mark, then on our port ETH0 we will get traffic from ports 0, 1, 2 without any sores. The next section says: ports = ‘3 5t’, vlan = 1. This means that non-meticable traffic from Port 3 will come to ETH0 with vlan-ine = 1 (I do not recommend using vlan.id = 1). The last section says vlan = 124, port = “6t 5T”. this means that the traffic who came to Port6 with a tag 124 will come to ETH0 with a tag 124. In Network, you can configure connections like PPTP, PPPOE, and even 6TO4.
Wi-Fi Settings:
Configuration file to be here./etc/config/wireless. Setting up radio integrations is divided into two parts: PHY level settings and setting integration. The minimum settings look like this:
In the first section, we indicated that the type of chipset/driver. MAC80211 (determined when loading), the channel used. 6. You can also specify the standards used, the power of the transmitter, the antennas used, etc. In the second section we are already describing the integration itself. There can be several intensees, for example, with different SSIDs. In the Device option, it is necessary to specify the section identifier with the description of the device, in this case, Radio0. Network = Guest means attaching this device to the Guest integusted in Network. Since we (look above) in the description of the network says that Interface = Guest is a bridge, then this wireless integration add to the BR-GUEST bridge. An example of the Multi-SSID settings with WPA2-EnterpriseccMP encryption:
OpenWRT will create two integers with different SSID (Super and Puper) and will authorize them through the 192 Radius server.168.0.eleven. Key is the key Radius. You can usually raise up to 4 SSID, depends on the radio card. I note that OpenWRT automatically creates an Monitor type for each Wi-Fi device, with which you can catch levels of 802.eleven. Links: Wiki.Openwrt.org/doc/uci wiki.Openwrt.org/doc/uci/Network wiki.Openwrt.org/doc/uci/wireless wiki.Openwrt.org/DOC/UCI/Network/Switch