Category Archives: Devices

DDNS DynDNS setup IP number

Published by:

There are countless reports of people who are having trouble configuring their network equipment to work with Dyndns, mostly because they need to enter an IP ADDRESS on their devices, rather than the usual dns name : members.dyndns.org
The forum keeps running around the bush about it. So I will give you a straight and short answer here:

The DynDNS IP number is 204.13.248.111

🙂

long answer:

According to DynDNS the syntax for an HTTP request uses members.dyndns.org. Just open a DOS command prompt and type

The result will reveal the IP address.

Note that it is quite possible that the result will be different from the address stated on top of this post. Especially if they use load balancing on their servers. You can use the one found by me or yours, it should work in both cases.

Another note: This is crucial to configure the I Power IP9258 with DDNS

How to install nano on OpenPLI 4 ( Vu+ solo2 )

Published by:

While using console to change files on you satellite receiver, most people will use vi to edit. But vi can be complicated.
I like the more user friendly tool nano. Sadly it doesn’t come with OpenPli.

Here is how to install it manually.

First, open a console (telnet) and logon as root on your sat receiver.

Then execute these commands:

Now, nano needs libncurses. Without it , it will give an error:

nano: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

This can be solved by installing the lib.

now nano will work.

Android : Stereo recorder for Samsung Note 2

Published by:

I have been searching for a tool that can record in stereo on the Note 2 from Samsung. This seems to be a rare feature giving developers some difficulties to efficiently implement. Especially because the Note 2 uses two separate microphones for stereo recordings.

The Samsung Note 2 (and maybe also the S3, I’m not sure) has two microphones, one on the front and another on the back. If you record video, the source of the sound is comming from both these microphones, so giving you stereo sound. But most (if not all) of sound recording apps will allow you to select one of them, both not both. Even though they advertise to be able to record in stereo, they will not allow you to bind the front mic to the right channel and the back mic to the left.

Until I found Easy Voice Recorder. ( pro version ).

Screenshot_2013-02-13-10-56-40

 
By using the “Sound input source” in the settings and selecting Camcorder microphone, the app will actually record in stereo using both microphones of your phone. The pro version gives you some extra features, worthwhile. You can choose bitrate and filetype, though mp3 is not supported — it uses AAC for compressed files.

Please post any comments or questions in the comment section below.

BBox2 Sagem Blocked – NAT out failed First packet in connection is not a SYN packet (part 2)

Published by:

I have been experimenting again with the ” First packet in connection is not a SYN packet: TCP 192.168.1.51:1036->157.55.133.202:80 on ppp0 ” error in my SAGEM F@ST router.

What I found was that the Sagem firewall and/or NAT throws this messages whenever tcp packets are fragmented and this has to do with the MTU (maximum transmission unit)

In short this means:
IP packets have a maximum load of 1500 bytes without fragmentation. If the load is bigger, the package will be split in multiple fragments that are transmitted separately. (fragmentation). When a PC (browser) communicates with a server, they agree on a maximum packet size (mtu) and that will be used for the remainder of the communication. Both your computer and server use the internal MTU and they don’t care about the MTU of devices and routes in between. Windows usually has a MTU of 1500, meaning it will squeeze every last bit in one packet. This is fine on a local LAN, without routers. But when the packet needs to be transmitted over PPPoE (ADSL), there is some additional 8 bytes of header-information that needs to be added, thus making the packet 1508 bytes, which is to big and will be fragmented. (learn more about this here)

Normally fragmentation is handled fine by routers in between, but the Sagem seems to mess things up.

What we need to do is lowering the MTU on the computer. This may avoid fragmentation and maybe with it this problem. To do that I used TCP/IP Optimizer 3 found here.

This program needs to run as Administrator. Put it on “Custom” (bottom right) and select you Network Adapter. Then set MTU to something like 1492 (or if you want to be absolutely safe 1460) and press Apply changes. Reboot.

If found that using a setting less then 1492 would reduce the “NAT out failed First packet” errors somewhat, but not completely. I still believe there is no real fix, unless there is a firmware upgrade (doubtful).

Please let me know in the comments what results you had.