My internet is routed from a home router D-Link DIR-600 which I have installed DD-WRT . In general, not a bad router maintains a relatively good maximum stable operation and N wi-fi standard. Separately, DD-WRT software gives me a lot of freedom of settings and voodoo spells.
Behind it in my local network is the server on which my modest blog is hosted. In general, dramas are derived from fact, that when a request is sent to the dns, my public IP corresponds to which I have forwarded to the host of my blog and when the request from the internal network it is not necessary to address my public address. Решението на проблема се оказа повече от елементарен трябва да се направи запис в /etc/hosts файлът в които да се посочи domain-a и IP адреса. Това става посредством следните 2 команди
echo '192.168.1.2 host.com' >> /etc/hosts
killall -HUP dnsmasq
You put them as a startup script in the administration -> commands part. Then restart your router or give a run to the command to run and you are ready the host you have described from your internal network will be visible with your local address.
Today I once again returned a router from the other world – his WAN port had burned out and he was generally just throwing. Yes, but not because it was suitable for * WRT firmware, I flashed it and replaced the WAN port to be one of those for LAN, so the procedure itself is generally bean
Does not allow resetting of vlan0ports
nvram set manual_boot_nv=1
Maha port 4(0) from Lan ports
nvram set vlan0ports=”3 2 1 5*”
Port 4 becomes a WAN port
nvram set vlan1ports=”0 5″
Restarts the router
The procedure was tested on Tomato WRT and works 100%, it will be similar for Open WRT and DD-Wrt it has a straight graphical gui tool. In general, the procedure is standard for most routers as long as they support VLAN-and so that different ports can be inserted into different network segments.
Yesterday I had a friend with the root of d-link dir-300 – an unpretentious low-end router. He complained of minor problems. He had problems with the automatic connection with pppoe or via wi-fi. I looked at everything, it looked fine, I upgraded its factory firmware, things were stable. Despite everything, I wanted to put dd-wrt on it because I know from last year, that there is firmware for this model as well. Since I was unlucky, the router was a revision of A1, the hamalogy of the hook was great. I will not explain in detail how to flash and so on, but I will rather emphasize 2 thin moments, because flash guide is good enough to handle on its own. The first thin moment is when you will enter RedBoot – the guide does not state that the reset button should be held for about 30 seconds after restarting the router and after starting it to connect to the router via telnet to 192.168.20.81 on the port 9000 through the wan port. This port is very important for the future because it will give you access to the boot rom in case you overdo something without wanting to.. At the end of the guide there is a short script that automatically connects to RedBoot for you. If you are using a Windows machine I highly recommend using putty instead of the built-in telnet client. The other thin point is the answer with y to all the questions the console asks you. There are no other pitfalls.
Once everything is ready and you do the last reset it will take you around 2 minutes to run the dd-wrt web part. You will guess, that everything is started when the wi-fi network indicator lights up. In general, the router loads much slower than before, it used to take him about 40-50 seconds now over a minute and a half. This is generally not a pain to die given that we already have a much more stable router. The problem is that it has a weak 183Mhz processor for comparison my Linksys WRT54G is with 200. It is also annoying that the processor is atheros and does not support overclocking.
In a few days I will probably repeat the procedure on another dir-300 A1, after all, the linux is based on the firmware and the stability it gives to the little box, separately the many new features with which routers can compete for several hundred $ it is not a fact of neglect.
My home router started to annoy me a bit that its range is a bit small but normally it still works with 2dBi antennas. Реших да потърся информация за цените на 5dBi или повече усилени антени и попаднах в един форум където имаше схема на една такава и човека беше описал че е модифицирал неговата стандартна до такава. In the afternoon I think to strip mine and fashion it to see, if not at least I will have a reason to buy new antennas 😀
Hello, I haven't written for a long time, that I had some heavy ones 5 daily parties 😆 and I almost didn't have time to be in real shape, that I scribble meaningful things 😈 But anyway this is a topic for some next post 😉 For now I will work on looking at the topic of open source firmware for routers (routers). I have mentioned it several times so far dd-wrt as my personal favorite, but less than a week ago our boy gat3way discovered brutal security bug in its software, which made me take some of the other projects more seriously. In particular, I stopped at tomato which was given to me by my friend Joro Filipov.
Switching from one software to another was a hassle straight from the upgrade part, there was no need for additional screws. After installing the “tomatoes” I was impressed by its clean interface. In general, I have always preferred something simple as a design, not something crowded. As a beauty definitely dd-wrt leads and tomato looks like it was created by me – 2-3 colors, but for some it's beautiful 😉 . The other thing that made a big impression on me was the very few possibilities – he misses around 40% from its various server havi and other things that dd-wrt has. However, I give, on the other hand, it works much easier 😉 So the defect can be an effect. It's a pleasant surprise, that tomato comes with described ports for better p2p traffic and with allowed UPnP . It also makes an impression, that tomatoes support slightly higher transfer speeds over a wireless connection, I didn't test it because I don't have much time, but I think there is still something to be optimized. Minus is the support of the small range of devices unlike dd-wrt, tomato works on quite a limited number of devices, I hope this fact will change in the future 😉 Also a minus is quite a complicated filter of traffic limitation (I like it, but some uneducated people will be glazed). Another downside is the lack of overclocking of the router's processor, although I read about spells through the console 😉 . Overall, this is a relatively synthesized and simplified comparative review between the two software, Personally, I like the tomato more, but there are still others like it that I haven't tested 😉