[Jesse Gilles]

Two things:

You probably want to specify the specific port that should be forwarded in your rule and possibly the protocol (UDP/TCP). Also, the “–to” option I believe should be “–to-destination”.

Example using port 80 for TCP:

iptables -t nat -A PREROUTING -p tcp -d 166.30.11.22 –dport 80 -j DNAT –to-destination 192.168.1.212

[Jesse Gilles]

You can access the console by using the serial debug cable and connecting at 115200 8N1. Hope that helps.

[Jesse Gilles]

I also added a link to it on the Getting Started page.

[Jesse Gilles]

It is under the Application Development section:

http://www.multitech.net/developer/products/cellular-development-platform/development/creating-a-custom-image/

[Jesse Gilles]

Opkg isn’t configured by default to pull from any feeds because Multi-Tech doesn’t publish any feeds for public use.

You’ll need to set up a feed on your development machine if you want to use ‘opkg update’ and ‘opkg install’ to install packages that you build. See this article for more information: http://www.multitech.net/developer/products/cellular-development-platform/development/setting-up-a-package-feed/

How did you install gdb on the unit?

You also have the option of reflashing the unit with your custom image (that contains gdb, glibc-dbg, etc).

[Jesse Gilles]

If you used opkg to install glibc-dbg and libthread-db1, try forcefully reinstalling the libc6 package.

opkg update

opkg –force-reinstall install libc6

We ran into a similar issue and it was resolved by reflashing the entire rootfs or by reinstalling libc6.

[Jesse Gilles]

What libraries are you interested in specifically?

Most python modules can be added using the “distutils” bitbake class. Recipes for such modules can be very simple, look at the python-pybluez_0.15.bb recipe for an example (located in openembedded/recipes/python).

The distutils class is described here:

http://docs.openembedded.org/usermanual/usermanual.html#distutils_class

The easiest way to learn is by looking at the other python module recipes.

[Jesse Gilles]

If the full NTPD server is using too much data for you, you can also run “ntpdate” from a cron job. ntpdate will run a one-time sync and exit. Then you can run it as often as you like. This is probably the simplest solution.

You can get the cellular network time from the modem by using AT^SIND as you mentioned, but the “nitz” value is only updated when the modem registers with the network. It doesn’t get continually updated. You would have to read the “nitz” value from AT^SIND on start up and use that value to set the real time clock (AT+CCLK=). Note that the AT^SIND command is specific to the MTSMC-E1 modem.

[Jesse Gilles]

I would recommend trying NTP. There is a package included in the base-image called ‘ntpdate’ that allows syncing the clock with an NTP server. This can be called from a cron job to be done periodically.

If you need more continuous synchronization, the NTP daemon (ntpd) will constantly correct the clock. ntpd is provided by the “ntp” package.

[Author]

Posts