Dev – Page 3 – LouWii's Blog

Django : resize an image on upload

This is a typical use-case : your site/app allows users to upload a picture. But you don’t want to store full size 8Mb picture, and still, it’s comfortable for the user to not have to manually resize the image before uploading it. The solution : resizing the image “on the fly” when receiving it on the server side.

Another use-case, also quite common : you need to generate a thumbnail for the uploaded picture. The following code will help you too.

This script is re-sizing the image only if it’s a new PicturePost (we check that the object key isn’t set).

We’re doing some calculation to get the right ratio before re-sizing the image. We can’t use the thumbnail() method because we want to resize based only on the width of the image. The thumbnail() method will resize the image based on the biggest between width and height.

We convert the image to jpeg with a 90 quality (the default is 75, 100 meaning no jpeg compression at all).

We also keep the exif information if its exists. By default, it’ll disappear, so we have to manually add them again when saving the resized file.

Once it’s resized, we save the object into the database.

import PIL
from PIL import Image
from django.db import models
from django.core.files.uploadedfile import InMemoryUploadedFile
from django.utils.six import StringIO


class PicturePost(models.Model):

    # Picture
    picture = models.ImageField(upload_to='uploads/%Y/%m/%d/')
    
    def save(self, *args, **kwargs):
        # Do extra stuff before saving

        # If new post, get the picture and resize it on the fly
        if self.pk is None:
            # 1200px width maximum
            basewidth = 1200
            img = Image.open(self.picture)
            # Keep the exif data
            exif = None
            if 'exif' in img.info:
                exif = img.info['exif']
            width_percent = (basewidth/float(img.size[0]))
            height_size = int((float(img.size[1])*float(width_percent)))
            img = img.resize((basewidth, height_size), PIL.Image.ANTIALIAS)
            output = StringIO()
            # save the resized file to our IO ouput with the correct format and EXIF data ;-)
            if exif:
                img.save(output, format='JPEG', exif=exif, quality=90)
            else:
                img.save(output, format='JPEG', quality=90)
            output.seek(0)
            self.picture = InMemoryUploadedFile(output, 'ImageField', "%s.jpg" % self.picture.name, 'image/jpeg',
                                                output.len, None)

        super(CarPost, self).save(*args, **kwargs)

import PIL

from PIL import Image

from django.db import models

from django.core.files.uploadedfile import InMemoryUploadedFile

from django.utils.six import StringIO

class PicturePost(models.Model):

# Picture

picture = models.ImageField(upload_to='uploads/%Y/%m/%d/')

def save(self, *args, **kwargs):

# Do extra stuff before saving

# If new post, get the picture and resize it on the fly

if self.pk is None:

# 1200px width maximum

basewidth = 1200

img = Image.open(self.picture)

# Keep the exif data

exif = None

if 'exif' in img.info:

exif = img.info['exif']

width_percent = (basewidth/float(img.size[0]))

height_size = int((float(img.size[1])*float(width_percent)))

img = img.resize((basewidth, height_size), PIL.Image.ANTIALIAS)

output = StringIO()

# save the resized file to our IO ouput with the correct format and EXIF data ;-)

if exif:

img.save(output, format='JPEG', exif=exif, quality=90)

else:

img.save(output, format='JPEG', quality=90)

output.seek(0)

self.picture = InMemoryUploadedFile(output, 'ImageField', "%s.jpg" % self.picture.name, 'image/jpeg',

output.len, None)

super(CarPost, self).save(*args, **kwargs)

You can also use the same logic to create a thumbnail of the image and store it into another ImageField field. 😉

Quick Start with Foundation

Never re-invent the wheel ! That’s a good moto for any developer out there. Let me show you how to quickly bootstrap you website stylesheet with Foundation. Its default components will help you to define a generic style very easily so you can concentrate on customizing to match your pixel-perfect design.

Setup Foundation on you machine

Install the foundation command line using npm

$ sudo npm install --global foundation-cli

1	$ sudo npm install --global foundation-cli

Creation of a new project

Setup your project with “foundation new” command.

You’ll have to choose between different options. I just choose the most common one, use Foundation for site with a simple template.

$ foundation new
? What are you building today? A website (Foundation for Sites)
? What's the project called? (no spaces) TestSite
? Which template would you like to use? Basic Template: includes a Sass compiler

            .
           /|     ,
      , /|/  \/| /|       Thanks for using ZURB Foundation for Sites!
     /|/       |/ |       -------------------------------------------
 |___|            |___|   Let's set up a new project.
 \___|  ^^   ^^   |___/   It shouldn't take more than a minute.
     | -[O]--[O]- |
     |    ___,    |
     |    ...     |
      \__________/


Downloading the project template...
Done downloading!

Installing dependencies...

[...]

You're all set!

 ✓ New project folder created.
 ✓ Node modules installed.
 ✓ Bower components installed.

Now run foundation watch while inside the TestSite folder.

$ foundation new

? What are you building today? A website (Foundation for Sites)

? What's the project called? (no spaces) TestSite

? Which template would you like to use? Basic Template: includes a Sass compiler

/| ,

, /|/ \/| /| Thanks for using ZURB Foundation for Sites!

/|/ |/ | -------------------------------------------

|___| |___| Let's set up a new project.

\___| ^^ ^^ |___/ It shouldn't take more than a minute.

| -[O]--[O]- |

| ___, |

| ... |

\__________/

Downloading the project template...

Done downloading!

Installing dependencies...

[...]

You're all set!

✓ New project folder created.

✓ Node modules installed.

✓ Bower components installed.

Now run foundation watch while inside the TestSite folder.

At the end, just type

$ cd TestSite
$ foundation watch

1 2	$ cd TestSite $ foundation watch

Each time you’ll modify a SASS file, it’ll be compiled (and rather quickly !) into an app.css file.

All you main SASS code has too be written in app.scss file.

You have the choice to include all foundation, or just a few part of it. Or even nothing at all. But I recommend at least one :

@include foundation-global-styles;

1	@include foundation-global-styles;

Which is taking care of resetting all styles, setting default styling for HTML elements and so on.

Write your code without annoying default Foundation classes

The goal is to use our own classes with Foundation code. Here is a simple example :

// Container will behave like a .row
// Create a row of 10 columns
.container {
  @include grid-row(10, 'collapse', null, true, $grid-column-gutter);
}

// 3 cols sidebar with 0 gutter
.sidebar {
  @include grid-column(3, 0);
}
// 7 cols main with 0 gutter
.main {
  @include grid-column(7, 0);
}

// Container will behave like a .row

// Create a row of 10 columns

.container {

@include grid-row(10, 'collapse', null, true, $grid-column-gutter);

}

// 3 cols sidebar with 0 gutter

.sidebar {

@include grid-column(3, 0);

}

// 7 cols main with 0 gutter

.main {

@include grid-column(7, 0);

}

For each of its components, Foundation gives you access to several mixins that you can include everywhere.

Anatomy of a good ExpressionEngine add-on

ExpressionEngine 3 has brought a lot of changes and if you’re coming from EE2, you might miss some that are really interesting. Ellislab team has a done a good job of bringing APIs and services for third party developers to use in their add-ons. Your code will be cleaner than ever 🙂

Here is just a selection of things that are used in almost every add-ons, the ones that you should really use in your next project.

Use Models

Documentation

Messing around with SQL queries might be ok, but if you add-on is quite complex and modify EE data, you might want to switch to using models. Models help you handling EE data (channel, members…) but you can also create your own ones. You’ll just rely on EE code and APIs, it’s way safer and will facilitate maintaining your code.

Plus it totally makes sense to use that service when doing OOP. It’s way easier to get back Objects and play with them, than getting back SQL results and process them before doing anything relevant.

Use shared form view

Documentation

Creating forms can be long and complex. But with the shared form view, it’s so easy you’ll even enjoy it. You basically need to declare your form using arrays. A lot of different field types are available. EE will generate all the HTML for you. Honestly, dealing with add-on settings is no more a pain now.

Use validation service

Documentation

Now it’s time to validate the user inputs. Again, no more pain, just use the validation service. It contains pre-defined rules and you can also create custom ones. Easy to write, easy to maintain, and a nice beautiful code. 😀

Add internal documentation

Documentation

This is not a code tip, but EE now includes internal doc. If you add a README.md file inside your add-on folder, you’ll be able to access that file from within EE. It might not be useful to you, but it’ll surely be for other developers out there that will need your add-on doc. 😉

Check the other services

ExpressionEngine 3 is providing other services that you might want to use, check them out.

EE3 architecture is working with dependencies, prefixes and providers.

There’s even a tree data structure if you ever need one.

Quick guide about Django translation

The documentation of translation in Django is pretty well done, but quite long. If you want to setup it up easily, here are the steps.

Translation Setup

Make sure you have gettext installed on your machine. I wrote an article about the OSX specificities.

# Ubuntu
$ sudo apt-get install gettext

# OSX
$ brew install gettext
$ brew link gettext --force

# Ubuntu

$ sudo apt-get install gettext

# OSX

$ brew install gettext

$ brew link gettext --force

Create a locale folder inside your main project folder

$ mkdir mysite/locale

1	$ mkdir mysite/locale

Django will create subfolders in the locale folder for each language you want to support.

Make sure you include the middleware class in your settings.py file, create or modify the languages settings and set the LOCALE_PATH variable :

MIDDLEWARE_CLASSES = (
    ...
    'django.middleware.locale.LocaleMiddleware',
    ...
)

LANGUAGES = (
    ## Customize this
    ('en', gettext('en')),
    ('fr', gettext('fr')),
)

LOCALE_PATHS = (
    'locale',
)

MIDDLEWARE_CLASSES = (

...

'django.middleware.locale.LocaleMiddleware',

...

)

LANGUAGES = (

## Customize this

('en', gettext('en')),

('fr', gettext('fr')),

)

LOCALE_PATHS = (

'locale',

)

Depending on your project structure, you might need to change the locale path to suit your needs. It’s often the cause of the translations not working !

Translation in .py files

We create an alias to it’s easier to use and I think it makes it more readable.

We can add a special comment which will be displayed in the translation file. It can be useful for your translators.

from django.utils.translation import ugettext as _
from django.http import HttpResponse

def my_view(request):
    # Translators: This message appears on the home page only
    output = _("Welcome to my site.")
    return HttpResponse(output)

from django.utils.translation import ugettext as _

from django.http import HttpResponse

def my_view(request):

# Translators: This message appears on the home page only

output = _("Welcome to my site.")

return HttpResponse(output)

There are a lot of other possibilities. Please read the documentation.

Translation in templates

We need to indicate that we’re using translation, so put that code somewhere near the top of your template.

{% load i18n %}

1	{% load i18n %}

Then it’s pretty easy

<title>{% trans "This is the title." %}</title>
<title>{% trans myvar %}</title>

1 2	<title>{% trans "This is the title." %}</title> <title>{% trans myvar %}</title>

Again, a lot of options and other methods are available, please read the doc.

Create the language files

Fortunately, Django is doing that for us ! Let’s create the french file :

$ django-admin makemessages -l fr

1	$ django-admin makemessages -l fr

Django will create the file in mysite/locale/fr/LC_MESSAGES/django.po

It’ll look like this :

#: auth/views.py:84
msgid "Username/password combination invalid"
msgstr ""

#: auth/views.py:84

msgid "Username/password combination invalid"

msgstr ""

You simply have to fill out msgstr with the translated phrase.

If you add new phrases in your code, just run

$ django-admin makemessages -a

1	$ django-admin makemessages -a

It’ll update all the languages.

Now, the last step : compiling the files into .mo files (binary files optimized for gettext)

$ django-admin compilemessages

1	$ django-admin compilemessages

And you’re pretty much done. It’s really awesome to see how easy it is.

gettext issue when using Django Translation in OSX

I ran into an issue when generating my language files for Django.

$ django-admin makemessages -l fr
CommandError: Can't find msguniq. Make sure you have GNU gettext tools 0.15 or newer installed.

1 2	$ django-admin makemessages -l fr CommandError: Can't find msguniq. Make sure you have GNU gettext tools 0.15 or newer installed.

This is because OSX has an old version of gettext installed. To use the last one, install it with homebrew and force homebrew to override OSX gettext command.

$ brew install gettext
...

$ brew link gettext --force
Linking /usr/local/Cellar/gettext/0.19.7... 190 symlinks created

$ brew install gettext

...

$ brew link gettext --force

Linking /usr/local/Cellar/gettext/0.19.7... 190 symlinks created

And then, no more problems !

$ django-admin makemessages -l fr
processing locale fr

1 2	$ django-admin makemessages -l fr processing locale fr

Source

Handling several PHP versions on OSX (including php7)

I was trying to use Phan, a PHP code analyser, on my Macbook, but it’s requiring PHP 7 cli. I never modified the PHP cli on my machine, mainly because I use MAMP to handle different environments. But here I had no choice. Here is the way I handled it.

Easy trick : use aliases

Yeah, it’s way too easy that way, just create an alias from your command line pointing to a php bin. In my case, I made it point to php7 bin from MAMP.

alias php='/Applications/MAMP/bin/php/php7.0.0/bin/php'

1	alias php='/Applications/MAMP/bin/php/php7.0.0/bin/php'

Note : you can name it whatever you want. php7 could be a good option too. 😉

To remove the alias :

unalias php

1	unalias php

To make the changes effective, either close and open your terminal again, or type in

source ~/.bash_profile

1	source ~/.bash_profile

Cleanest way : using brew

If you have Homebrew installed on your machine, it’s pretty easy to install whatever version of PHP with it. And it’ll take care of every cli bins.

In my case, I had a 5.5 version of PHP already installed, so I need to tell brew to unlink it before installing another one

brew unlink php55

1	brew unlink php55

And then, let brew do the dirty work for you

brew install php70

1	brew install php70

Et voilà !

$ php -v
PHP 7.0.3 (cli) (built: Feb  6 2016 03:16:24) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies

$ php -v

PHP 7.0.3 (cli) (built: Feb 6 2016 03:16:24) ( NTS )

Lazy way to make your WordPress content working with HTTPS

Yeah, we’re all lazy sometime. I recently added HTTPS support to this blog but the content saved might contain http links or image addresses. Instead of updating the whole database, you can just add this to your theme functions.php file :

//Custom to handle embedded content without https
function force_https_the_content($content) {
  if ( is_ssl() )
  {
    $content = str_replace( 'http://blog.louwii.fr', 'https://blog.louwii.fr', $content );
  }
  return $content;
}
add_filter('the_content', 'force_https_the_content');

//Custom to handle embedded content without https

function force_https_the_content($content) {

if ( is_ssl() )

{

$content = str_replace( 'http://blog.louwii.fr', 'https://blog.louwii.fr', $content );

}

return $content;

}

add_filter('the_content', 'force_https_the_content');

Problem solved ! I know, it’s not very clean, but it’s working great.

Setup environment to work with Django CMS on OSX

Getting the whole python / environment / Django / server running is not that easy when you’re not familiar with it, especially if you’re used to use Apache/MySQL combo. I wrote that guide as a reminder, but I’m sure it can help you setup a Django CMS site pretty easily.

Continue reading Setup environment to work with Django CMS on OSX

Create your own seedbox with Transmission torrent client

Want a small seedbox on your server ? It’s really not complicated, thanks to Transmission.

First step, install it using your OS package manager

apt-get install transmission-daemon

1	apt-get install transmission-daemon

Then we need to stop the deamon to configure it.

/etc/init.d/transmission-daemon stop

1	/etc/init.d/transmission-daemon stop

To edit the configuration file (vi FTW):

vi /etc/transmission-daemon/settings.json

1	vi /etc/transmission-daemon/settings.json

Here is a list of important values to change. You can find documentation about the configuration file there.

/* Username and password so only you can access the web interface */
"rpc-username": "myUsername",
/* You can enter the password here, it will be hashed on the first login */
"rpc-password": "my5up3r$C0mplic47edPa$$",
/* If you don't want login/pass protection, set that to false */
"rpc-authentification-required": true,
/* If you want to find your files easily, better change this one */
"download-dir": "/path/to/the/dir",
/* You might want to change this one also */
"incomplete-dir": "/path/to/the/dir",
/* Authorize access only to known connections 
 * You can set that to false, especially if you have dynamic IP address
 */
"rpc-whitelist-enabled": true,
/* Add your IP address here if you set previous param to true */
"rpc-whitelist": "127.0.0.1,192.168.1.1",
/* -- ports setup -- */
/* access to the web interface */
"rpc-port": 8353,
/* peer port */
/* set fixed port */
"peer-port": 6401,
/* or set a range */
"peer-port-random-high": 6411,
"peer-port-random-low": 6401,
"peer-port-random-on-start": true,

/* Username and password so only you can access the web interface */

"rpc-username": "myUsername",

/* You can enter the password here, it will be hashed on the first login */

"rpc-password": "my5up3r$C0mplic47edPa$$",

/* If you don't want login/pass protection, set that to false */

"rpc-authentification-required": true,

/* If you want to find your files easily, better change this one */

"download-dir": "/path/to/the/dir",

/* You might want to change this one also */

"incomplete-dir": "/path/to/the/dir",

/* Authorize access only to known connections

* You can set that to false, especially if you have dynamic IP address

"rpc-whitelist-enabled": true,

/* Add your IP address here if you set previous param to true */

"rpc-whitelist": "127.0.0.1,192.168.1.1",

/* -- ports setup -- */

/* access to the web interface */

"rpc-port": 8353,

/* peer port */

/* set fixed port */

"peer-port": 6401,

/* or set a range */

"peer-port-random-high": 6411,

"peer-port-random-low": 6401,

"peer-port-random-on-start": true,

Configure the firewall so we can actually access the web interface and send/receive packets. Be sure to set it up regarding the ports you entered in your configuration file.

sudo iptables -t filter -A OUTPUT -p tcp --dport 8353 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 8353 -j ACCEPT
sudo iptables -t filter -A OUTPUT -p tcp --dport 6401:6411 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 6401:6411 -j ACCEPT
sudo iptables -t filter -A OUTPUT -m owner --gid-owner debian-transmission -j ACCEPT

sudo iptables -t filter -A OUTPUT -p tcp --dport 8353 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 8353 -j ACCEPT

sudo iptables -t filter -A OUTPUT -p tcp --dport 6401:6411 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 6401:6411 -j ACCEPT

sudo iptables -t filter -A OUTPUT -m owner --gid-owner debian-transmission -j ACCEPT

Now, time to start the daemon again

/etc/init.d/transmission-daemon start

1	/etc/init.d/transmission-daemon start

To access transmission web interface, use your server IP address

http://1.2.3.4:8353/transmission

And you’re done ! Easy, isn’t it ?

iptables basic configuration for your webserver

Very important aspect of your web server security : the firewall. Most of web servers are using iptables to control what is going in and out. And it’s pretty easy to use.

Here is my basic configuration (you can also find it on Github) :

#!/bin/sh
 
# Empty all rules
sudo iptables -t filter -F
sudo iptables -t filter -X
 
# Bloc everything by default
sudo iptables -t filter -P INPUT DROP
sudo iptables -t filter -P FORWARD DROP
sudo iptables -t filter -P OUTPUT DROP
 
# Authorize already established connexions
sudo iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -t filter -A INPUT -i lo -j ACCEPT
sudo iptables -t filter -A OUTPUT -o lo -j ACCEPT
 
# ICMP (Ping)
sudo iptables -t filter -A INPUT -p icmp -j ACCEPT
sudo iptables -t filter -A OUTPUT -p icmp -j ACCEPT
 
# SSH
sudo iptables -t filter -A INPUT -p tcp --dport 22 -j ACCEPT
sudo iptables -t filter -A OUTPUT -p tcp --dport 22 -j ACCEPT
 
# DNS
sudo iptables -t filter -A OUTPUT -p tcp --dport 53 -j ACCEPT
sudo iptables -t filter -A OUTPUT -p udp --dport 53 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 53 -j ACCEPT
sudo iptables -t filter -A INPUT -p udp --dport 53 -j ACCEPT
 
# HTTP
sudo iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT
 
#HTTPS
sudo iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT
 
# FTP
sudo iptables -t filter -A OUTPUT -p tcp --dport 20:21 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 20:21 -j ACCEPT
 
# Git
sudo iptables -t filter -A OUTPUT -p tcp --dport 9418 -j ACCEPT
sudo iptables -t filter -A INPUT -p tcp --dport 9418 -j ACCEPT
 
# Mail SMTP
iptables -t filter -A INPUT -p tcp --dport 25 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 25 -j ACCEPT
 
# Mail POP3
iptables -t filter -A INPUT -p tcp --dport 110 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 110 -j ACCEPT
 
# Mail IMAP
iptables -t filter -A INPUT -p tcp --dport 143 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 143 -j ACCEPT
 
# NTP (server time)
sudo iptables -t filter -A OUTPUT -p udp --dport 123 -j ACCEPT

#!/bin/sh

# Empty all rules

sudo iptables -t filter -F

sudo iptables -t filter -X

# Bloc everything by default

sudo iptables -t filter -P INPUT DROP

sudo iptables -t filter -P FORWARD DROP

sudo iptables -t filter -P OUTPUT DROP

# Authorize already established connexions

sudo iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

sudo iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

sudo iptables -t filter -A INPUT -i lo -j ACCEPT

sudo iptables -t filter -A OUTPUT -o lo -j ACCEPT

# ICMP (Ping)

sudo iptables -t filter -A INPUT -p icmp -j ACCEPT

sudo iptables -t filter -A OUTPUT -p icmp -j ACCEPT

# SSH

sudo iptables -t filter -A INPUT -p tcp --dport 22 -j ACCEPT

sudo iptables -t filter -A OUTPUT -p tcp --dport 22 -j ACCEPT

# DNS

sudo iptables -t filter -A OUTPUT -p tcp --dport 53 -j ACCEPT

sudo iptables -t filter -A OUTPUT -p udp --dport 53 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 53 -j ACCEPT

sudo iptables -t filter -A INPUT -p udp --dport 53 -j ACCEPT

# HTTP

sudo iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT

#HTTPS

sudo iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT

# FTP

sudo iptables -t filter -A OUTPUT -p tcp --dport 20:21 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 20:21 -j ACCEPT

# Git

sudo iptables -t filter -A OUTPUT -p tcp --dport 9418 -j ACCEPT

sudo iptables -t filter -A INPUT -p tcp --dport 9418 -j ACCEPT

# Mail SMTP

iptables -t filter -A INPUT -p tcp --dport 25 -j ACCEPT

iptables -t filter -A OUTPUT -p tcp --dport 25 -j ACCEPT

# Mail POP3

iptables -t filter -A INPUT -p tcp --dport 110 -j ACCEPT

iptables -t filter -A OUTPUT -p tcp --dport 110 -j ACCEPT

# Mail IMAP

iptables -t filter -A INPUT -p tcp --dport 143 -j ACCEPT

iptables -t filter -A OUTPUT -p tcp --dport 143 -j ACCEPT

# NTP (server time)

sudo iptables -t filter -A OUTPUT -p udp --dport 123 -j ACCEPT