Ir al contenido principal

Configurar la red en ubuntu.

Tras estar probando con Bind9, servidores DHCP y demas, perdi mi configuracion de la tarjeta de red.

El sistema no me reconocia la interfaz eth0 => no tenia internet => problema.

Como a mi me da direcciones mi router, sabia que tenia que configurarla para que le asignaran una direccion de forma dinamica.

Al final, los pasos que segui fueron estos:

Configurar el archivo /etc/network/interfaces de la siguiente manera:

sudo gedit /etc/network/interfaces

escribir las siguientes lineas en el archivo:

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp


Grabar los cambios y reiniciar la interfaz:

/etc/init.d/networking restart



En el caso de querer configurarla estaticamente, habria tenido que escribir las siguientes lineas en mi /etc/network/interfaces:


iface eth0 inet static
address 192.168.1.5
netmask 255.255.255.0
gateway 192.168.1.254


//LAS DIRECCIONES PUESTAS SON UN EJEMPLO

Comentarios

Entradas populares de este blog

Use django ORM standalone within your nameko micro-services

Learning about micro services with python, I found a great tool named nameko . https://www.nameko.io/ Nameko is a Python framework to build microservices that doesn't care in concrete technologies you will use within your project. To allow that microservices to work with a database, you can install into your project a wide variety of third parties, like SQLAlchemy (just like any other). To have an easy way to communicate with the database and keep track of the changes made to the models, I chose Django: I'm just learning about microservices and I want to keep focused on that. Easy to use, Django is a reliable web framework, have a powerful and well known ORM. Also using Django we will have many of the different functionalities that this framework provide. To make all this magic to work together, I developed a python package that allow you to use Django as a Nameko injected dependency: https://pypi.org/project/django-nameko-standalone/ You can found the source ...

Stop measuring time with time.clock() in Python3

If we read the time.clock() documentation ( https://docs.python.org/3/library/time.html#time.clock): Deprecated since version 3.3: The behaviour of this function depends on the platform: use perf_counter() or process_time() instead, depending on your requirements, to have a well defined behaviour. I use time.perf_counter, but feel free to use time.process_time if fits for your requirements. The main difference they have are: time.perf_counter() It does include time elapsed during sleep and is system-wide. time.process_time() It does not include time elapsed during sleep. It is process-wide by definition.

Stop python debugger exactly on the failing loop iteration

This post is for ipdb users. Is this case familiar for you?: Write a break point on your code Go into a loop Start pressing 'c' and 'n' until you found the iteration that is failing. It can works, but you can only do this ... one or two times maybe?? If you need to this frequently, this method doesn't works and you need another tool, but .... what's the tool I need? You need launch_ipdb_on_exception ... ... from ipdb import launch_ipdb_on_exception with launch_ipdb_on_exception(): for i in range ( 9 ): print (i) if i== 4 : raise Exception('Debug time!') ... # Output 0 1 2 3 4 Exception('Debug time!',) > <ipython-input-1-4f44dca149ad>(7)<module>() 5 print(i) 6 if i==4: ----> 7 raise Exception('Debug time!') ipdb> i # Note ipdb console!! 4 ipdb> c # Continues the execution In [2]: i # Ipython console again Out[2]: 4 In [3...