Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Connection to the router

Created by: McSaesch at: 5/11/2018 3:18 PM (7 Replies)

Rating (1)

Thanks 0

8 Entries

5/11/2018 3:18 PM	Rate (0)
McSaesch Regular Member Joined: 6/1/2017 Last visit: 1/18/2019 Posts: 21 Rating: (0)	Hardware: IOT2040 Hi, i 've download the last sample image (Example_Image_V2.2.0) , set it up and configurated the interfaces: # The loopback interface auto lo iface lo inet loopback # Wired interfaces auto eth0 iface eth0 inet static address 192.168.0.253 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.0.255 gateway 192.168.0.1 auto eth1 iface eth1 inet dhcp I want to connect (over eth1) to a router (192.168.0.1) with a SIM, for a mobile internet connection.If i "ping www.google.com" OR "ping 8.8.8.8" all i get, is 'bad address'. Which settings are missing or what should i change?! Regards
	Last edited by: McSaesch at: 5/11/2018 3:27:58 PM Last edited by: McSaesch at: 5/11/2018 3:31:46 PM
Suggestion To thank Quote Answer

5/11/2018 3:32 PM	Rate (0)
trinitry Experienced Member Joined: 12/17/2013 Last visit: 2/19/2019 Posts: 31 Rating: (3)	hi, type in terminal echo "nameserver 8.8.8.8" > /etc/resolv.conf and ping again to see if it works

Suggestion To thank Quote Answer

5/11/2018 3:36 PM	Rate (0)
McSaesch Regular Member Joined: 6/1/2017 Last visit: 1/18/2019 Posts: 21 Rating: (0)	I get the same answer, "bad address" by pining www.google.com or 8.8.8.8

Suggestion To thank Quote Answer

5/12/2018 9:11 AM	Rate (0)
trinitry Experienced Member Joined: 12/17/2013 Last visit: 2/19/2019 Posts: 31 Rating: (3)	could you please post the output from the bellow terminal command ifconfig eth1

Suggestion To thank Quote Answer

5/12/2018 11:53 AM	Rate (0)
bergmanu Gold Expert Joined: 4/28/2015 Last visit: 2/21/2019 Posts: 1019 Rating: (166)	Hi, that won't work like that. Because you will have the same IP range on both interfaces (etc0 and eth1). The eth0 has 192.168.0.253 and the eth1 will reveice an address 192.168.0.xxx. You will have to set your eth0 to another range, maybe like 192.168.1.253. There is a good explanation of this problem in this topic. Best regards!

Suggestion To thank Quote Answer

5/14/2018 1:05 PM	Rate (0)
McSaesch Regular Member Joined: 6/1/2017 Last visit: 1/18/2019 Posts: 21 Rating: (0)	Thanks for the feedback. I've done a lot of search at the weekend, so i changed my configuration: /etc/network/interfaces #X1P1 auto eth0 iface eth0 inet static address 192.168.0.253 netmask 255.255.255.0 gateway 192.168.0.1 #auto eth1 #iface eth1 inet dhcp #X2P1 auto eth1 iface eth1 inet static address 192.168.200.1 netmask 255.255.255.0 The IOT is connected over eth0 with the router (192.168.0.1). I connected to the IOT over the router, everything works fine. BUT the result is the same... i can ping 8.8.8.8, but i get a bad address on "google.com". I think, it's a DNS problem. If i add "nameserver 8.8.8.8" to /etc/resolv.conf", ich can "ping www.google.com"... but after a reboot, the resolv.conf is empty. ifconfig: eth0 Link encap:Ethernet HWaddr E0:DC:A0:17:2B:05 inet addr:192.168.0.253 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::e2dc:a0ff:fe17:2b05%134535671/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:532 errors:0 dropped:0 overruns:0 frame:0 TX packets:477 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:51813 (50.5 KiB) TX bytes:67227 (65.6 KiB) Interrupt:34 Base address:0xc000 eth1 Link encap:Ethernet HWaddr E0:DC:A0:17:2B:06 inet addr:192.168.200.1 Bcast:192.168.200.255 Mask:255.255.255.0 inet6 addr: fe80::e2dc:a0ff:fe17:2b06%134535671/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:508 (508.0 B) Interrupt:35 Base address:0xc000 Any ideas?! Thanks in advance

Suggestion To thank Quote Answer

5/16/2018 9:42 AM	Rate (1)
bergmanu Gold Expert Joined: 4/28/2015 Last visit: 2/21/2019 Posts: 1019 Rating: (166)	Hi, yes this is problem.. The resolv.conf file is overwritten with every boot. Here is the solution for this problem Best regards!

Suggestion To thank Quote Answer

5/22/2018 11:31 AM	Rate (0)
McSaesch Regular Member Joined: 6/1/2017 Last visit: 1/18/2019 Posts: 21 Rating: (0)	Thanks!! Looks very good, the settings will stay in the resolv.conf after a reboot. Thumbs up!!

Suggestion To thank Quote Answer

| |

Related topics by keywords:

SIMATIC IOT2000 System

Follow us on