DNS configuration on MLinux
Home › Forums › Conduit: mLinux Model › DNS configuration on MLinux
Tagged: Conduit mLinux DNS LoRa
- This topic has 12 replies, 4 voices, and was last updated 8 years, 9 months ago by
Jason Reiss.
-
AuthorPosts
-
May 21, 2016 at 4:22 am #12632
Thierry Schneider
ParticipantHi,
I would like to forward LoRa messages to iot.semtech.com but it seem the DNS function is not working in the Multitech Conduit.How can I enable it ?
Thanks
ThierryMay 23, 2016 at 7:37 am #12637Jeff Hatch
KeymasterThierry,
If you have a cellular radio and a SIM card installed, once cellular is enabled and ppp is up and running you should have DNS working. If you don’t have a cellular radio and/or SIM card, in the UI you can go to Setup->Network Interfaces, select the eth0 interface and set DNS and gateway settings.
Jeff
May 23, 2016 at 7:43 am #12638Jeff Hatch
KeymasterThierry,
Sorry, I thought you were running an AEP model Conduit. To set up the DNS on the mLinux model, if you have a cellular radio and SIM card, you can set up ppp with the instructions at:
If you don’t have a cellular radio and/or SIM card, you can update the /etc/network/interfaces file to configure the eth0 with an entry like:
# Wired interface
auto eth0
iface eth0 inet static
address 192.168.2.100
gateway 192.168.2.1
netmask 255.255.255.0Jeff
May 23, 2016 at 8:54 am #12641Thierry Schneider
ParticipantHi Jeff,
Thank you for the answer. Unfortunately this specifies the IP address and routing but it doesn’s active DNS
Best regards
ThierryMay 23, 2016 at 9:03 am #12642Jeff Hatch
KeymasterThierry,
For DNS you should be able to add the dns nameservers:
# Wired interface
auto eth0
iface eth0 inet static
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 12.34.56.78 12.34.56.79
netmask 255.255.255.0Jeff
June 10, 2016 at 6:52 am #12963Thierry Schneider
ParticipantHi Jeff,
Here is the content of my interfaces configuration file
The DNS is not working.
When I make
ping http://www.google.com
ping: unknown host http://www.google.com# /etc/network/interfaces — configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback# Wired interface
auto eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.0
network 192.168.1.1
broadcast 192.168.0.255
post-up route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.1
dns-nameservers 8.8.8.8 194.230.55.99June 10, 2016 at 9:04 am #12968Jeff Hatch
KeymasterThierry,
Is ppp running and is there a ppp interface instantiated? Second, can you ping 8.8.8.8 or 194.230.55.99? I don’t see a gateway specified in your configuration, so I can’t tell whether the device has any routes to get to the nameservers.
Jeff
June 10, 2016 at 9:06 am #12969Jeff Hatch
KeymasterI see the “post-up route add”, but am not sure how that works, especially with the unspecified addresses for the net and netmask.
Jeff
June 10, 2016 at 9:26 am #12970Thierry Schneider
Participantping 8.8.8.8 is working
I have no task named ppp or pppdI’m connected to the internet through a direct ETH connection
Thierry
June 10, 2016 at 9:35 am #12971Jason Reiss
KeymasterIf you edit /etc/resolv.conf and add your dns servers there
nameserver 8.8.8.8
The resolv.conf file will be reset on reboot so you will have to change the file again.
It seems the dns-nameservers line in /etc/network/interfaces is not being applied on startup.
June 10, 2016 at 9:49 am #12973Bryan Tran
ModeratorHi Thierry,
Try this and see if it helps?
Remove this line: dns-nameservers 8.8.8.8 194.230.55.99
Add these lines: post-up echo “nameserver 8.8.8.8″ > /etc/resolv.conf
post-up echo “nameserver 194.230.55.99″ >> /etc/resolv.confThanks,
BT
June 10, 2016 at 10:00 am #12974Bryan Tran
ModeratorHi Thierry,
Also, when you issue the ping – omit the http:// – Try do like: ping http://www.google.com from the Conduit.
Thanks,
BT
June 10, 2016 at 10:01 am #12975Jason Reiss
KeymasterThat worked for me Bryan, thanks.
Just do not copy and paste from the post as the quotes are not “quotes”.
-
AuthorPosts
- You must be logged in to reply to this topic.