SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Not able to ping google

6/2/2023 5:44 PM	Rate (0)
oluwasedago Experienced Member Joined: 3/30/2015 Last visit: 3/7/2024 Posts: 70 Rating: (1)	Hi please I am having similar issue, not able to ping google and I am sure I have network on the cable connected to my X2P1 LAN. My port config is shown below ###################### x auto eth0 x iface eth0 inet static x address 192.168.200.1 x netmask 255.255.255.0 x x auto eth1 x iface eth1 inet dhcp x x wlan0 config: x network={ ###################### I want to install node red S7 and not able to. Could you help please Result of my ping is: ################ root@iot2000:~# ping www.google.com ping: bad address 'www.google.com' ############### If I remove the Ethernet cable and plug to my laptop, I get immediate internet access. Thank you ------------------------------------------------------------------------------------------ Split from [SOLVED]IOT2020 Internet Connection Issue - Ping Bad Address.
	Last edited by: Jen_Moderator at: 06/05/2023 08:38:24 New subject after splitting
Suggestion To thank Quote Answer

6/2/2023 5:48 PM	Rate (0)
oluwasedago Experienced Member Joined: 3/30/2015 Last visit: 3/7/2024 Posts: 70 Rating: (1)	My ifconfig result ####################### root@iot2000:~# ifconfig eth0 Link encap:Ethernet HWaddr E0:DC:A0:12:FA:F6 inet addr:192.168.200.1 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::e2dc:a0ff:fe12:faf6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5080 errors:0 dropped:0 overruns:0 frame:0 TX packets:6622 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:481934 (470.6 KiB) TX bytes:4475114 (4.2 MiB) Interrupt:56 Base address:0x8000 eth1 Link encap:Ethernet HWaddr E0:DC:A0:12:FA:F7 inet addr:192.168.2.74 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::e2dc:a0ff:fe12:faf7/64 Scope:Link inet6 addr: 2003:db:4f15:54dd:e2dc:a0ff:fe12:faf7/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21279 errors:0 dropped:131 overruns:0 frame:0 TX packets:1458 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1343283 (1.2 MiB) TX bytes:156706 (153.0 KiB) Interrupt:57 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:773 errors:0 dropped:0 overruns:0 frame:0 TX packets:773 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:57972 (56.6 KiB) TX bytes:57972 (56.6 KiB)

Suggestion To thank Quote Answer

6/4/2023 5:32 AM	Rate (0)
oluwasedago Experienced Member Joined: 3/30/2015 Last visit: 3/7/2024 Posts: 70 Rating: (1)	Fixed by changing the content of my resolv.conf file # Generated by Connection Manager # search speedport.ip # nameserver fe80::1 nameserver 8.8.8.8 nameserver 192.168.1.1 nameserver 8.8.4.4 chattr +i /etc/resolv.conf

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Jen_Moderator

Share this page:

Share this page on...