More Echolink findings · Apr 23, 05:51 PM by Gregg Wonderly
Tonight, I helped WD4OIN get his DI-624 AirPlus Xtreme router setup for echolink use. This is the first device that I’ve seen that is actually two different routers. It has a VOIP module in it as a separate routing device and it has a wireless/wired router in it as well.
What we found was that the WAN address for the router which we found by web browsing to the “gateway address” was 192.168.15.28, a private network address. I had Jack open his web browser to 192.168.15.1 and found another routing device.
This device had port triggering available and so we set up port triggering on port 5200/TCP to cause forwarding of 5198-5199/UDP. It took us a while to get through the configuration over the phone because I did not find a manual for the AirPlus Xtreme to look at on line. But, once we got that router configured with port forwarding, everything worked.
I had Jack change his computer to use a fixed IP address of 192.168.0.50 instead of the DHCP address of 192.168.0.100. We used ‘ipconfig/all’ in a DOS window to find out the DHCP configuration before hand, so then we could copy the netmask, default gateway and DNS addresses that the router was providing with DHCP.
And, we also removed the IP V6 stack because the IP addresses for IPV6 are a different format (typically they include the IPV4 private network prefix), and can be confusing to read through.
Anyway, Jack is on echolink now, and hopefully anyone else with the D-Link DI-624+ AirPlus Xtreme can use the above information to find a solution for their woes.
