SOLLAE SYSTEMS ENGLISH BLOG

I have received an e-mail from DynDNS.

Thay said the account service will be changed.

I'll let you know the contents.

What changes?

Previously they offered each account to have 5 free hostnames and you could select them from 88 different domains.

Now, this will be limited to 2 free hostnames from 18 DynDNS branded domains.

Why they making these changes?

There are a number of reasons that they thought it was important to make the changes now.

1. Having 88 free domains to choose from was overwhelming for many of new users.By reducing this to 18 it makes it easier for people to get started.

2. By limiting the free options to the DynDNS branded domains, it helps grow the awareness of their services. Although they are happy to offer the free services, they simply ask that you help spread the word to other people who might find their paid services helpful. They have to pay those bills somehow.

2. Looking at the stats of their users over the past 12 years, they see that the vast majority of people only use 1 free hostname. Their support team has seen a lot of confusion caused by the five free hostnames, so when you combine that with the normal use case, it just made sense. They are allowing the 2^nd hostname for those who need to create a WebHop to access your hostname. If you are going to need more than 1 or 2 hostnames there's a good chance you are using us for something important. If that's the case, they simply ask that you pay $15/yr for the DynDNS Pro upgrade, which provides a number of other benefits.

If you are using DynDNS services for business critical needs, you should consider the Custom DNS service.

What will happen to your current account and hostnames?

Nothing, as long as you keep your hostnames active and up-to-date. If you allow your account or hostnames to expire, you will have to select from the new domains instead and will be limited to the 2 free hostnames. To ensure you aren’t affected by these changes, upgrade to DynDNS Pro for just $15/yr. Again, there are a number of other benefits to upgrading.

They just trying to force us to pay you, aren't they?

No, not really. As long as you keep your account active, you won't be affected by these changes. They would never want to have a user feel like they were forced to use their services. This does not seem to be a very good business model to them. You do your part (log into your account or update your hostname monthly) and they will do theirs (continue to offer free Dynamic DNS services to you).

(0) (0)

Posted by eztcp

UDP (User Datagram Protocol) is one of two prominent protocols in transport layer.

This protocol is quite simple and fast so many real time systems are taking it.

However it is unreliable on data integrity.

If your system does not allow any data loss, you should take TCP rather than UDP.

ezTCP has two optional communication modes and they are TCP and UDP.

You can select one considering your systems and its environment.

In case of TCP, ezTCP communicates one remote host at a time.

(Except for some products which have multiple monitoring function)

Like this, ezTCP can set a peer host as its counterpart in UDP.

However, because this protocol has no connection procedure, transferring same data to multiple hosts at a time.

This is possible because the peer host address could be set to broadcast IP address.

Then, how about switching peer host?

This means that ezTCP communicate with one host at a time but the host can be changed without additional setting.

ezTCP can do this.

We call this option “Dynamic Peer Host Configuration” and almost products equip that.

ezTCP changes peer host to a new one which sends the last received data to itself.

Even if ezTCP is sending data continuously, it changes the peer host right after data from another host has arrived.

 

ezTCP updates the peer host address when a packet from another device has been arrived.

How to use it?

 Just set both peer IP address and port number to 0.

That’s all.

(0) (0)

Posted by eztcp

Almost ezTCP products have restriction function.

The concept is block accesses from any unauthorized devices.

MAC address and IP address with the network mask can be used for this function.

According to using which products, you can use both or just one way.

The blow table shows you which products support both ways.

Using restriction

1. An IP address only.

When ezTCP is in TCP server mode, the restriction is available.

   a. Run ezConfig

   b. Search and Select your product

   c. Set an IP address on the [Allowed IP Address] parameter.

It seems to be quite simple.

Now, only a device whose IP address is the same with the value of the [Allowed IP Address] parameter can access to your product.

In this case, you can set only one IP address for the permission.

2. An IP address with network mask.

   a. Run ezManager

   b. Search and select your product

   c. Move to the [Option] tab

   d. Check the [Allowed IP Range] option.

   e. Set an IP address on the [IP Address] box.

   f. Check or uncheck each check box of the [Network Mask]

If you check all the check boxes, just one device which is set to the [IP Address] box is the only one which can access to your device.

Otherwise, it is possible to adjust the range of permission.

The detail is in the below table.

3. MAC address.

   a. Run ezManager

   b. Search and select your product

   c. Move to the [Option] tab

   d. Check the [Allowed MAC address] option.

   e. Set an MAC address on the box.

Like the case 1, you can set just one device for permission.

And, note that MAC address is valid only the same local network.

(0) (0)

Posted by eztcp