<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Ashus.ashus.net - Other]]></title>
		<link>https://ashus.ashus.net/</link>
		<description><![CDATA[Ashus.ashus.net - https://ashus.ashus.net]]></description>
		<pubDate>Sat, 02 May 2026 03:05:47 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[OpenWRT radio check]]></title>
			<link>https://ashus.ashus.net/thread-202.html</link>
			<pubDate>Sun, 04 Jun 2023 16:01:22 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-202.html</guid>
			<description><![CDATA[Recently there have been issues with DFS around me. Personally I think it is being misused to free up space in 5 GHz range - someone shoots radar signals and it kills my wi-fi 5 GHz radios until restart. It happens once a week and then I find out about it few days later after people yell at me it's working too slow (only on 2.4 GHz range).<br />
<br />
To deal with this I've come up with this script:<br />
<a href="https://github.com/Ashus/OpenWRT-radio-check" target="_blank" rel="noopener" class="mycode_url">https://github.com/Ashus/OpenWRT-radio-check</a><br />
<br />
I am going to need this fix until hostapd gets fixed and try the same DFS channels again after reasonable time.]]></description>
			<content:encoded><![CDATA[Recently there have been issues with DFS around me. Personally I think it is being misused to free up space in 5 GHz range - someone shoots radar signals and it kills my wi-fi 5 GHz radios until restart. It happens once a week and then I find out about it few days later after people yell at me it's working too slow (only on 2.4 GHz range).<br />
<br />
To deal with this I've come up with this script:<br />
<a href="https://github.com/Ashus/OpenWRT-radio-check" target="_blank" rel="noopener" class="mycode_url">https://github.com/Ashus/OpenWRT-radio-check</a><br />
<br />
I am going to need this fix until hostapd gets fixed and try the same DFS channels again after reasonable time.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OpenWRT 19.07.10 squashfs for ar71xx 4MB devices (-tiny) with LuCI]]></title>
			<link>https://ashus.ashus.net/thread-196.html</link>
			<pubDate>Sun, 08 May 2022 17:31:18 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-196.html</guid>
			<description><![CDATA[This is a package of OpenWRT 19.07.10 stable builds for targets ar71xx.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>added relayd<br />
</li>
<li>added WatchCat<br />
</li>
<li>replaced wpad-mini by wpad-basic<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. Relayd is there for cases where you use the device as LAN extender over WLAN without additional NAT. Wpad-basic enables the use of 802.11r.<br />
<br />
I have selected to build only those targets, that have not been ported to ath79.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/19.07.10-targets-ar71xx-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/19.07.10-targe...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/19.07.10-targets-ar71xx-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/19.07.10-target...tiny-luci/</a>]]></description>
			<content:encoded><![CDATA[This is a package of OpenWRT 19.07.10 stable builds for targets ar71xx.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>added relayd<br />
</li>
<li>added WatchCat<br />
</li>
<li>replaced wpad-mini by wpad-basic<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. Relayd is there for cases where you use the device as LAN extender over WLAN without additional NAT. Wpad-basic enables the use of 802.11r.<br />
<br />
I have selected to build only those targets, that have not been ported to ath79.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/19.07.10-targets-ar71xx-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/19.07.10-targe...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/19.07.10-targets-ar71xx-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/19.07.10-target...tiny-luci/</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OpenWRT 21.02 squashfs for ath79 4MB devices (-tiny) with LuCI]]></title>
			<link>https://ashus.ashus.net/thread-192.html</link>
			<pubDate>Fri, 03 Sep 2021 23:51:45 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-192.html</guid>
			<description><![CDATA[This is a package of OpenWRT 21.02.3 stable builds for targets ath79.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed SSL support</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed signature checking, etc.</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed swapoff and long options support from busybox</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">stripped to bare bones</span><br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>flashing from LuCI switched off (it causes devices to freeze)<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. <span style="color: #000000;" class="mycode_color">Relayd or wpad-basic could not fit in anymore.</span><br />
<br />
Please note there is still upgrading incompatibility against deprecated target ar71xx (OpenWRT version 18.06 or older), please see <a href="https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79" target="_blank" rel="noopener" class="mycode_url">https://openwrt.org/docs/guide-user/inst...x.to.ath79</a> for more info.<br />
<br />
Backup your configuration via webserver, but flash new upgrades using SSH. Webserver most likely doesn't have enough memory to handle file upload as all my tests resulted in the need to reboot the device entirely.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>  ssh root@192.168.1.1 #or use PuTTY<br />
  grep machine /proc/cpuinfo #check device identification<br />
  cd /tmp<br />
  wget HTTP-URL #copy URL from browser, HTTPS won't work<br />
  sysupgrade -v openwrt- #use TAB to autocomplete filename</code></div></div><br />
<br />
If you are unable to log into LuCI, you probably have old /etc/config/uhttpd file present and there are attempts to redirect you to HTTPS protocol. Remove it (use rm /etc/config/uhttpd) and re-flash using the guide above.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/21.02.3-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/21.02.3-target...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/21.02.3-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/21.02.3-targets...tiny-luci/</a>]]></description>
			<content:encoded><![CDATA[This is a package of OpenWRT 21.02.3 stable builds for targets ath79.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed SSL support</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed signature checking, etc.</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">removed swapoff and long options support from busybox</span><br />
</li>
<li><span style="color: #000000;" class="mycode_color">stripped to bare bones</span><br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>flashing from LuCI switched off (it causes devices to freeze)<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. <span style="color: #000000;" class="mycode_color">Relayd or wpad-basic could not fit in anymore.</span><br />
<br />
Please note there is still upgrading incompatibility against deprecated target ar71xx (OpenWRT version 18.06 or older), please see <a href="https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79" target="_blank" rel="noopener" class="mycode_url">https://openwrt.org/docs/guide-user/inst...x.to.ath79</a> for more info.<br />
<br />
Backup your configuration via webserver, but flash new upgrades using SSH. Webserver most likely doesn't have enough memory to handle file upload as all my tests resulted in the need to reboot the device entirely.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>  ssh root@192.168.1.1 #or use PuTTY<br />
  grep machine /proc/cpuinfo #check device identification<br />
  cd /tmp<br />
  wget HTTP-URL #copy URL from browser, HTTPS won't work<br />
  sysupgrade -v openwrt- #use TAB to autocomplete filename</code></div></div><br />
<br />
If you are unable to log into LuCI, you probably have old /etc/config/uhttpd file present and there are attempts to redirect you to HTTPS protocol. Remove it (use rm /etc/config/uhttpd) and re-flash using the guide above.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/21.02.3-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/21.02.3-target...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/21.02.3-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/21.02.3-targets...tiny-luci/</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Mailcow-dockerized systemd control script]]></title>
			<link>https://ashus.ashus.net/thread-190.html</link>
			<pubDate>Mon, 28 Jun 2021 01:25:56 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-190.html</guid>
			<description><![CDATA[You can use this control script to enable commands like <span style="font-style: italic;" class="mycode_i">service mailcow restart</span> just like with other services.<br />
Add the following file named <span style="font-weight: bold;" class="mycode_b">mailcow.service</span> to directory<span style="font-weight: bold;" class="mycode_b"> /etc/systemd/system</span> of your Debian installation.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Unit]<br />
Description=Mailcow-dockerized control<br />
# no need to enable as a service - mailcow-dockerized gets executed on reboot automatically<br />
Requires=docker.service<br />
After=docker.service<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=true<br />
Restart=no<br />
RestartSec=2<br />
User=root<br />
WorkingDirectory=/opt/mailcow-dockerized/<br />
ExecStart=/usr/local/bin/docker-compose up -d<br />
ExecStop=/usr/local/bin/docker-compose down<br />
<br />
[Install]<br />
WantedBy=multi-user.target</code></div></div>]]></description>
			<content:encoded><![CDATA[You can use this control script to enable commands like <span style="font-style: italic;" class="mycode_i">service mailcow restart</span> just like with other services.<br />
Add the following file named <span style="font-weight: bold;" class="mycode_b">mailcow.service</span> to directory<span style="font-weight: bold;" class="mycode_b"> /etc/systemd/system</span> of your Debian installation.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Unit]<br />
Description=Mailcow-dockerized control<br />
# no need to enable as a service - mailcow-dockerized gets executed on reboot automatically<br />
Requires=docker.service<br />
After=docker.service<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=true<br />
Restart=no<br />
RestartSec=2<br />
User=root<br />
WorkingDirectory=/opt/mailcow-dockerized/<br />
ExecStart=/usr/local/bin/docker-compose up -d<br />
ExecStop=/usr/local/bin/docker-compose down<br />
<br />
[Install]<br />
WantedBy=multi-user.target</code></div></div>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[RamDisk - cause of BSOD PFN_LIST_CORRUPT on Windows 10]]></title>
			<link>https://ashus.ashus.net/thread-187.html</link>
			<pubDate>Thu, 27 Aug 2020 00:54:11 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-187.html</guid>
			<description><![CDATA[I tried to upgrade my Windows 10 to 2004 build lately. Everytime I tried to do it, I had to revert because of <span style="font-weight: bold;" class="mycode_b">PFN_LIST_CORRUPT </span>BSODs happening more and more frequently after boot (from 20 to 5 minutes). It happened on both, my AMD Ryzen 7 and Intel i3 platform. I suspected antivirus software at first, tried to remove it, but it didn't help.<br />
<br />
The cause was <span style="font-weight: bold;" class="mycode_b">Softperfect RAM disk 3.4.8</span> (last version under free-for-personal-use license).<br />
I removed it an used latest <span style="font-weight: bold;" class="mycode_b">ImDisk Tools</span> released for free. This fixed the problem.<br />
<br />
I use Ramdisk for volatile data, browser cache and user TEMP directory, mainly because of SSD limited writes. Also, a single reboot automatically cleans this drive after some badly written apps. The only downside of this - there are some application installations, which unpack themselves once again to Temp and they can run out of space, so then it is needed to temporarily redirect Temp back to system drive.<br />
<br />
To have persistent Ramdisk while using <span style="font-weight: bold;" class="mycode_b">ImDisk Tools</span>, you need to use an image or Task Scheduler, because built-in persistency over reboots works only partially. The Ramdisk ends up created, but unformatted. I suspect there is a problem with security as only administrators can format disks and if launched from admin command line, it works until first reboot. Either create empty Ramdisk and create a directory there using these task actions:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -a -m Z: -t vm -s 3G -p "/fs:ntfs /q /y"<br />
mkdir Z:&#92;temp</code></div></div><br />
or prepare an image of specific size and mount it once with persistency (-P):<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -a -P -m Z: -o sparse -o awe -f c:&#92;ramdisk.img</code></div></div><br />
To unmount any of them you can use:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -d -m Z:</code></div></div><br />
In system variables, you can then modify the user's variables <span style="font-weight: bold;" class="mycode_b">TEMP </span>and <span style="font-weight: bold;" class="mycode_b">TMP </span>to point to <span style="font-style: italic;" class="mycode_i">Z:\temp</span>.<br />
Chromium browsers need to be launched with parameter as in example: <span style="font-weight: bold;" class="mycode_b">--disk-cache-dir=z:\Vivaldi\</span> every single time.]]></description>
			<content:encoded><![CDATA[I tried to upgrade my Windows 10 to 2004 build lately. Everytime I tried to do it, I had to revert because of <span style="font-weight: bold;" class="mycode_b">PFN_LIST_CORRUPT </span>BSODs happening more and more frequently after boot (from 20 to 5 minutes). It happened on both, my AMD Ryzen 7 and Intel i3 platform. I suspected antivirus software at first, tried to remove it, but it didn't help.<br />
<br />
The cause was <span style="font-weight: bold;" class="mycode_b">Softperfect RAM disk 3.4.8</span> (last version under free-for-personal-use license).<br />
I removed it an used latest <span style="font-weight: bold;" class="mycode_b">ImDisk Tools</span> released for free. This fixed the problem.<br />
<br />
I use Ramdisk for volatile data, browser cache and user TEMP directory, mainly because of SSD limited writes. Also, a single reboot automatically cleans this drive after some badly written apps. The only downside of this - there are some application installations, which unpack themselves once again to Temp and they can run out of space, so then it is needed to temporarily redirect Temp back to system drive.<br />
<br />
To have persistent Ramdisk while using <span style="font-weight: bold;" class="mycode_b">ImDisk Tools</span>, you need to use an image or Task Scheduler, because built-in persistency over reboots works only partially. The Ramdisk ends up created, but unformatted. I suspect there is a problem with security as only administrators can format disks and if launched from admin command line, it works until first reboot. Either create empty Ramdisk and create a directory there using these task actions:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -a -m Z: -t vm -s 3G -p "/fs:ntfs /q /y"<br />
mkdir Z:&#92;temp</code></div></div><br />
or prepare an image of specific size and mount it once with persistency (-P):<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -a -P -m Z: -o sparse -o awe -f c:&#92;ramdisk.img</code></div></div><br />
To unmount any of them you can use:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>imdisk -d -m Z:</code></div></div><br />
In system variables, you can then modify the user's variables <span style="font-weight: bold;" class="mycode_b">TEMP </span>and <span style="font-weight: bold;" class="mycode_b">TMP </span>to point to <span style="font-style: italic;" class="mycode_i">Z:\temp</span>.<br />
Chromium browsers need to be launched with parameter as in example: <span style="font-weight: bold;" class="mycode_b">--disk-cache-dir=z:\Vivaldi\</span> every single time.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OpenWRT 19.07.10 squashfs for ath79 4MB devices (-tiny) with LuCI]]></title>
			<link>https://ashus.ashus.net/thread-184.html</link>
			<pubDate>Sat, 15 Feb 2020 15:38:54 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-184.html</guid>
			<description><![CDATA[This is a package of OpenWRT 19.07.10 stable builds for targets ath79.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>added relayd<br />
</li>
<li>added WatchCat<br />
</li>
<li>replaced wpad-mini by wpad-basic<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. Relayd is there for cases where you use the device as LAN extender over WLAN without additional NAT. Wpad-basic enables the use of 802.11r.<br />
<br />
Please note there is still upgrading incompatibility against deprecated target ar71xx (OpenWRT version 18.06 or older), please see <a href="https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79" target="_blank" rel="noopener" class="mycode_url">https://openwrt.org/docs/guide-user/inst...x.to.ath79</a> for more info.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/19.07.10-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/19.07.10-targe...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/19.07.10-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/19.07.10-target...tiny-luci/</a>]]></description>
			<content:encoded><![CDATA[This is a package of OpenWRT 19.07.10 stable builds for targets ath79.<br />
<br />
Modifications against default tiny packages:<ul class="mycode_list"><li>removed PPP support<br />
</li>
<li>removed OPKG<br />
</li>
<li>added <span style="font-weight: bold;" class="mycode_b">LuCI</span><br />
</li>
<li>added relayd<br />
</li>
<li>added WatchCat<br />
</li>
<li>replaced wpad-mini by wpad-basic<br />
</li>
</ul>
<br />
This way the builds could fit into <span style="font-weight: bold;" class="mycode_b">squashfs </span>(factory/<span style="font-weight: bold;" class="mycode_b">sysupgrade</span>) compatible builds. Relayd is there for cases where you use the device as LAN extender over WLAN without additional NAT. Wpad-basic enables the use of 802.11r.<br />
<br />
Please note there is still upgrading incompatibility against deprecated target ar71xx (OpenWRT version 18.06 or older), please see <a href="https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79" target="_blank" rel="noopener" class="mycode_url">https://openwrt.org/docs/guide-user/inst...x.to.ath79</a> for more info.<br />
<br />
Builds have not been tested for all devices, but compiling resulted in no errors.<br />
<br />
<br />
<a href="https://openwrt.ashus.net/19.07.10-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.ashus.net/19.07.10-targe...tiny-luci/</a><br />
For wget in console you can use extra configured non-secure source <a href="http://openwrt.ashus.net/19.07.10-targets-ath79-tiny-luci/" target="_blank" rel="noopener" class="mycode_url">http://openwrt.ashus.net/19.07.10-target...tiny-luci/</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Google AdSense Extension for PhpBB 3.1.x]]></title>
			<link>https://ashus.ashus.net/thread-169.html</link>
			<pubDate>Mon, 27 Apr 2015 00:11:10 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-169.html</guid>
			<description><![CDATA[An extension for phpBB 3.1 that allows administrators to easily add their Google AdSense ads after first post in topic display details.<br />
<br />
Modified from this extension: <a href="https://github.com/phpbb-extensions/googleanalytics" target="_blank" rel="noopener" class="mycode_url">Google Analytics from phpBB team</a><br />
Thanks guys.<br />
<br />
<br />
<h2>Quick Install</h2><br />
You can install this on the latest release of phpBB 3.1 by following the steps below:<br />
<br />
<ol type="1" class="mycode_list"><li>Download the latest release<br />
</li>
<li>Unzip the downloaded release.<br />
</li>
<li>Copy the `ashus` directory to `phpBB/ext/ashus/` (if done correctly, you'll have the main composer JSON file at (your forum root)/ext/ashus/adsense/composer.json).<br />
</li>
<li>Navigate in the ACP to `Customise -&gt; Manage extensions`.<br />
</li>
<li>Look for `Google AdSense` under the Disabled Extensions list, and click its `Enable` link.<br />
</li>
<li>Set up and configure Google AdSense by navigating in the ACP to `General` -&gt; `Board Configuration` -&gt; `Board Settings`.</li>
</ol>
<br />
<h2>Uninstall</h2><br />
<ol type="1" class="mycode_list"><li>Navigate in the ACP to `Customise -&gt; Extension Management -&gt; Extensions`.<br />
</li>
<li>Look for `Google AdSense` under the Enabled Extensions list, and click its `Disable` link.<br />
</li>
<li>To permanently uninstall, click `Delete Data` and then delete the `/ext/ashus/adsense` directory.</li>
</ol>
<br />
<h2>Support</h2><ul class="mycode_list"><li>Support requests should be posted and discussed in the <a href="https://ashus.ashus.net/viewtopic.php?f=7&amp;t=295" target="_blank" rel="noopener" class="mycode_url">Google AdSense topic at ashus.ashus.net</a>.</li>
</ul>
<br />
<h2>License</h2><br />
<a href="http://opensource.org/licenses/GPL-2.0" target="_blank" rel="noopener" class="mycode_url">GNU General Public License v2</a><br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=164" target="_blank">ashus-adsense.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">15,44 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1470</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[An extension for phpBB 3.1 that allows administrators to easily add their Google AdSense ads after first post in topic display details.<br />
<br />
Modified from this extension: <a href="https://github.com/phpbb-extensions/googleanalytics" target="_blank" rel="noopener" class="mycode_url">Google Analytics from phpBB team</a><br />
Thanks guys.<br />
<br />
<br />
<h2>Quick Install</h2><br />
You can install this on the latest release of phpBB 3.1 by following the steps below:<br />
<br />
<ol type="1" class="mycode_list"><li>Download the latest release<br />
</li>
<li>Unzip the downloaded release.<br />
</li>
<li>Copy the `ashus` directory to `phpBB/ext/ashus/` (if done correctly, you'll have the main composer JSON file at (your forum root)/ext/ashus/adsense/composer.json).<br />
</li>
<li>Navigate in the ACP to `Customise -&gt; Manage extensions`.<br />
</li>
<li>Look for `Google AdSense` under the Disabled Extensions list, and click its `Enable` link.<br />
</li>
<li>Set up and configure Google AdSense by navigating in the ACP to `General` -&gt; `Board Configuration` -&gt; `Board Settings`.</li>
</ol>
<br />
<h2>Uninstall</h2><br />
<ol type="1" class="mycode_list"><li>Navigate in the ACP to `Customise -&gt; Extension Management -&gt; Extensions`.<br />
</li>
<li>Look for `Google AdSense` under the Enabled Extensions list, and click its `Disable` link.<br />
</li>
<li>To permanently uninstall, click `Delete Data` and then delete the `/ext/ashus/adsense` directory.</li>
</ol>
<br />
<h2>Support</h2><ul class="mycode_list"><li>Support requests should be posted and discussed in the <a href="https://ashus.ashus.net/viewtopic.php?f=7&amp;t=295" target="_blank" rel="noopener" class="mycode_url">Google AdSense topic at ashus.ashus.net</a>.</li>
</ul>
<br />
<h2>License</h2><br />
<a href="http://opensource.org/licenses/GPL-2.0" target="_blank" rel="noopener" class="mycode_url">GNU General Public License v2</a><br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=164" target="_blank">ashus-adsense.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">15,44 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1470</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to print business cards better]]></title>
			<link>https://ashus.ashus.net/thread-166.html</link>
			<pubDate>Fri, 13 Mar 2015 01:35:57 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-166.html</guid>
			<description><![CDATA[You likely have an image of your business card in resolution 9x5cm (300 DPI) from Photoshop.<br />
Now how to tile the image to make them fit on A4 page as many times as possible?<br />
<br />
Install <a href="http://www.imagemagick.org/" target="_blank" rel="noopener" class="mycode_url">ImageMagick</a> and use the attached batch script.<br />
It takes the source image, duplicates it to 3x4 grid to make them fit 12 times on one A4 page. They are easy to cut, with borders as guidelines around them.<br />
Just make sure to set the same DPI before printing, to retain the 9x5cm dimensions.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=163" target="_blank">make-cards.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">390 bytes</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">926</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[You likely have an image of your business card in resolution 9x5cm (300 DPI) from Photoshop.<br />
Now how to tile the image to make them fit on A4 page as many times as possible?<br />
<br />
Install <a href="http://www.imagemagick.org/" target="_blank" rel="noopener" class="mycode_url">ImageMagick</a> and use the attached batch script.<br />
It takes the source image, duplicates it to 3x4 grid to make them fit 12 times on one A4 page. They are easy to cut, with borders as guidelines around them.<br />
Just make sure to set the same DPI before printing, to retain the 9x5cm dimensions.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=163" target="_blank">make-cards.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">390 bytes</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">926</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to delete all logs in multiple */data/logs/* folders]]></title>
			<link>https://ashus.ashus.net/thread-164.html</link>
			<pubDate>Sun, 08 Mar 2015 14:27:47 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-164.html</guid>
			<description><![CDATA[On Windows you need to install cygwin first.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>%WINDIR%&#92;linux&#92;find c:/temporary/htdocs -type f -iwholename "*/data/logs/*" -delete</code></div></div>]]></description>
			<content:encoded><![CDATA[On Windows you need to install cygwin first.<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>%WINDIR%&#92;linux&#92;find c:/temporary/htdocs -type f -iwholename "*/data/logs/*" -delete</code></div></div>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Ping, traceroute and nslookup shortcuts]]></title>
			<link>https://ashus.ashus.net/thread-162.html</link>
			<pubDate>Thu, 12 Feb 2015 22:44:28 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-162.html</guid>
			<description><![CDATA[In Windows extract these files to your \Windows folder.<br />
<!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=160" target="_blank">net utils.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">1,5 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1039</span></span>
</div>
<!-- end: postbit_attachments_attachment --><br />
<br />
In linux append this to your ~/.bashrc file:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>alias p='ping'<br />
alias pp='ping -s 1024'<br />
alias p4='ping'<br />
alias pp4='ping -s 1024'<br />
alias p6='ping6'<br />
alias pp6='ping6 -s 1024'<br />
alias t='traceroute'<br />
alias tt='traceroute -n'<br />
alias n='nslookup'</code></div></div><br />
<h2>Guide</h2><br />
<span style="font-weight: bold;" class="mycode_b">p</span> pings using default stack<br />
<span style="font-weight: bold;" class="mycode_b">pp</span> pings using 1kB data<br />
<span style="font-weight: bold;" class="mycode_b">p4</span> forces IPv4 (<span style="font-weight: bold;" class="mycode_b">pp4</span> 1kB data)<br />
<span style="font-weight: bold;" class="mycode_b">p6</span> forces IPv6 (<span style="font-weight: bold;" class="mycode_b">pp6</span> 1kB data)<br />
<span style="font-weight: bold;" class="mycode_b">t</span> makes a traceroute (you can use first parameter -4 or -6 to force stack)<br />
<span style="font-weight: bold;" class="mycode_b">tt</span> makes a traceroute without resolving names (-4, -6)<br />
<span style="font-weight: bold;" class="mycode_b">n</span> resolves a name to IP address]]></description>
			<content:encoded><![CDATA[In Windows extract these files to your \Windows folder.<br />
<!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=160" target="_blank">net utils.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">1,5 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1039</span></span>
</div>
<!-- end: postbit_attachments_attachment --><br />
<br />
In linux append this to your ~/.bashrc file:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>alias p='ping'<br />
alias pp='ping -s 1024'<br />
alias p4='ping'<br />
alias pp4='ping -s 1024'<br />
alias p6='ping6'<br />
alias pp6='ping6 -s 1024'<br />
alias t='traceroute'<br />
alias tt='traceroute -n'<br />
alias n='nslookup'</code></div></div><br />
<h2>Guide</h2><br />
<span style="font-weight: bold;" class="mycode_b">p</span> pings using default stack<br />
<span style="font-weight: bold;" class="mycode_b">pp</span> pings using 1kB data<br />
<span style="font-weight: bold;" class="mycode_b">p4</span> forces IPv4 (<span style="font-weight: bold;" class="mycode_b">pp4</span> 1kB data)<br />
<span style="font-weight: bold;" class="mycode_b">p6</span> forces IPv6 (<span style="font-weight: bold;" class="mycode_b">pp6</span> 1kB data)<br />
<span style="font-weight: bold;" class="mycode_b">t</span> makes a traceroute (you can use first parameter -4 or -6 to force stack)<br />
<span style="font-weight: bold;" class="mycode_b">tt</span> makes a traceroute without resolving names (-4, -6)<br />
<span style="font-weight: bold;" class="mycode_b">n</span> resolves a name to IP address]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to turn off camera sounds (shutter and focus) on CM11]]></title>
			<link>https://ashus.ashus.net/thread-159.html</link>
			<pubDate>Tue, 16 Dec 2014 20:11:29 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-159.html</guid>
			<description><![CDATA[Copy sh script using ES File Explorer (with root) to folder /system/addon.d . Set up rights to be 770 (rwxrwx---).<br />
Re-flash firmware (upgrade).<br />
Tested on CyanogenMod 11 (Android 4.4.4 KitKat) od NovaFusion (20141214).<br />
<br />
<br />
Nahrát sh skript pomocí ES File Exploreru (s rootem) do /system/addon.d . Nastavte práva na 770 (rwxrwx---).<br />
Flashnout znovu firmware (aktualizovat).<br />
Testováno na CyanogenModu 11 (Android 4.4.4 KitKat) od NovaFusion (20141214).<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=159" target="_blank">ashus-camera-sound.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">714 bytes</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">878</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[Copy sh script using ES File Explorer (with root) to folder /system/addon.d . Set up rights to be 770 (rwxrwx---).<br />
Re-flash firmware (upgrade).<br />
Tested on CyanogenMod 11 (Android 4.4.4 KitKat) od NovaFusion (20141214).<br />
<br />
<br />
Nahrát sh skript pomocí ES File Exploreru (s rootem) do /system/addon.d . Nastavte práva na 770 (rwxrwx---).<br />
Flashnout znovu firmware (aktualizovat).<br />
Testováno na CyanogenModu 11 (Android 4.4.4 KitKat) od NovaFusion (20141214).<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=159" target="_blank">ashus-camera-sound.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">714 bytes</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">878</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Windows 7 - přepínátko priority mezi IPv4 a IPv6]]></title>
			<link>https://ashus.ashus.net/thread-158.html</link>
			<pubDate>Wed, 11 Jun 2014 14:42:50 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-158.html</guid>
			<description><![CDATA[V přiloženém ZIPu jsou dva reg soubory pro modifikaci registru Windows. Jeden nastavuje prioritu IPv4, druhý zpátky na IPv6, tedy pokud máte dualstack spojení internetu, můžete si zvolit, které spojení se má používat prioritně. Po aplikování je nutný restart systému.<br />
<br />
V případě tunelování IPv6 nebo pokud potřebujete používat VPN spojení, které je nakonfigurováno čistě v IPv4 k sítím, které jsou zároveň dostupné i přes IPv6 se to může hodit.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=152" target="_blank">DualStack.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">1 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">870</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[V přiloženém ZIPu jsou dva reg soubory pro modifikaci registru Windows. Jeden nastavuje prioritu IPv4, druhý zpátky na IPv6, tedy pokud máte dualstack spojení internetu, můžete si zvolit, které spojení se má používat prioritně. Po aplikování je nutný restart systému.<br />
<br />
V případě tunelování IPv6 nebo pokud potřebujete používat VPN spojení, které je nakonfigurováno čistě v IPv4 k sítím, které jsou zároveň dostupné i přes IPv6 se to může hodit.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="ZIP File" alt=".zip" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=152" target="_blank">DualStack.zip</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">1 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">870</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MiniUPNPd patched for routed network]]></title>
			<link>https://ashus.ashus.net/thread-156.html</link>
			<pubDate>Tue, 18 Mar 2014 18:14:19 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-156.html</guid>
			<description><![CDATA[If you have tried to forward UDP packets of UPNP (dynamic NAT port forwarding) to another network (you may have NAT further away from you), you need a little workaround for miniupnpd server to accept addresses that are not bound to any interface. The message in debug reads following: miniupnpd[3605]: get_lan_for_peer(): 192.168.5.25:1900 not found !<br />
<br />
<br />
Let's say we have main router A, that NATs traffic of clients at A and router B. Router A also shapes traffic, so we can't use NAT on B natively and just forward everything to A. We need to forward UPNP and nat-PMP requests from clients of B to the router A. Clients of A have IP range 192.168.1.0/24, clients of B 192.168.5.0/24. The router A has IP 192.168.1.1 and 192.168.2.1 on p2p link with B. Router B has IPs 192.168.5.1 and 192.168.2.2 on p2p link with A.<br />
<br />
Getting NAT-PMP to work is really easy, only one line is required in the firewall of B:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code># NAT-PMP relay<br />
iptables -t nat -A PREROUTING -i eth0 -p udp -d 192.168.5.1 --dport 5351 -j DNAT --to-destination 192.168.2.1</code></div></div><br />
<br />
To route multicast traffic, you need to use smcroute on B. Configuration must be done per-IP:<br />
[code]function smcroute_ip {<br />
    smcroute -a "&#36;2" "&#36;1" 239.255.255.250 wlan0<br />
}<br />
<br />
smcroute -a wlan0 192.168.2.1 239.255.255.250 eth0<br />
<br />
for (( i = 2 ; i <br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/bootbb/attachtypes/unknown.png" title="Unknown" alt=".tgz" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=156" target="_blank">miniupnpd-1.8.20140523-ashus.tgz</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">190,68 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">3</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[If you have tried to forward UDP packets of UPNP (dynamic NAT port forwarding) to another network (you may have NAT further away from you), you need a little workaround for miniupnpd server to accept addresses that are not bound to any interface. The message in debug reads following: miniupnpd[3605]: get_lan_for_peer(): 192.168.5.25:1900 not found !<br />
<br />
<br />
Let's say we have main router A, that NATs traffic of clients at A and router B. Router A also shapes traffic, so we can't use NAT on B natively and just forward everything to A. We need to forward UPNP and nat-PMP requests from clients of B to the router A. Clients of A have IP range 192.168.1.0/24, clients of B 192.168.5.0/24. The router A has IP 192.168.1.1 and 192.168.2.1 on p2p link with B. Router B has IPs 192.168.5.1 and 192.168.2.2 on p2p link with A.<br />
<br />
Getting NAT-PMP to work is really easy, only one line is required in the firewall of B:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code># NAT-PMP relay<br />
iptables -t nat -A PREROUTING -i eth0 -p udp -d 192.168.5.1 --dport 5351 -j DNAT --to-destination 192.168.2.1</code></div></div><br />
<br />
To route multicast traffic, you need to use smcroute on B. Configuration must be done per-IP:<br />
[code]function smcroute_ip {<br />
    smcroute -a "&#36;2" "&#36;1" 239.255.255.250 wlan0<br />
}<br />
<br />
smcroute -a wlan0 192.168.2.1 239.255.255.250 eth0<br />
<br />
for (( i = 2 ; i <br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/bootbb/attachtypes/unknown.png" title="Unknown" alt=".tgz" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=156" target="_blank">miniupnpd-1.8.20140523-ashus.tgz</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">190,68 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">3</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PHP icon, PHPX executable for Windows]]></title>
			<link>https://ashus.ashus.net/thread-134.html</link>
			<pubDate>Fri, 08 Feb 2013 19:53:05 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-134.html</guid>
			<description><![CDATA[Contents:<br />
<span style="font-weight: bold;" class="mycode_b">PHP icon</span> - extract to your WINDOWS directory.<br />
<span style="font-weight: bold;" class="mycode_b">PHP cli-exec</span> - contains registry settings to launch PHP script from context menu (.php) or by double-clicking (.phpx)<br />
<br />
Of course in order to launch PHP script, you need to have <a href="https://windows.php.net/download/" target="_blank" rel="noopener" class="mycode_url">PHP</a> installed. The requirement is to have the system PATH variable pointing to PHP binary file (php.exe).<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="" alt=".7z" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=174" target="_blank">PHP-icon-assoc.7z</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">7,88 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1080</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[Contents:<br />
<span style="font-weight: bold;" class="mycode_b">PHP icon</span> - extract to your WINDOWS directory.<br />
<span style="font-weight: bold;" class="mycode_b">PHP cli-exec</span> - contains registry settings to launch PHP script from context menu (.php) or by double-clicking (.phpx)<br />
<br />
Of course in order to launch PHP script, you need to have <a href="https://windows.php.net/download/" target="_blank" rel="noopener" class="mycode_url">PHP</a> installed. The requirement is to have the system PATH variable pointing to PHP binary file (php.exe).<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="" alt=".7z" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=174" target="_blank">PHP-icon-assoc.7z</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">7,88 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">1080</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PSPad PHP definition file]]></title>
			<link>https://ashus.ashus.net/thread-133.html</link>
			<pubDate>Thu, 07 Feb 2013 13:04:41 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://ashus.ashus.net/member.php?action=profile&uid=2">Ashus</a>]]></dc:creator>
			<guid isPermaLink="false">https://ashus.ashus.net/thread-133.html</guid>
			<description><![CDATA[My updated PHP definition file (downloaded directly from documentation at php.net on 05/14/2013).<br />
Contains functions and updated parameterers for PHP 5.4/6.<br />
<br />
Put it in your Context folder.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="" alt=".7z" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=136" target="_blank">PHP.7z</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">99,53 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">947</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[My updated PHP definition file (downloaded directly from documentation at php.net on 05/14/2013).<br />
Contains functions and updated parameterers for PHP 5.4/6.<br />
<br />
Put it in your Context folder.<br /><!-- start: postbit_attachments_attachment -->
<div style="padding:4px 0px;"><span class="inline-block vmiddle"><!-- start: attachment_icon -->
<img src="https://ashus.ashus.net/images/attachtypes/zip.png" title="" alt=".7z" />
<!-- end: attachment_icon --></span>
<a  class="vmiddle inline-block" href="attachment.php?aid=136" target="_blank">PHP.7z</a> <span class="smalltext float_right">Size: <span class="inline-block vmiddle">99,53 KB</span>&nbsp;&nbsp;Downloads: <span class="inline-block vmiddle">947</span></span>
</div>
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
	</channel>
</rss>