I am working back through each step of your help. Looking at the networkmanager connection settings above, on the IPv4 Settings tab. I notice the DHCP client ID you referenced. Please see the image link below. That cell is greyed out and will not allow me to add the client ID address. What else needs to be selected to allow that field to be entered?
thank you.
I can ping 8.8.8.8 and 8.8.4.4 and also the router at 192.168.50.1
The firewall is not on.
I added the 8.8.8.8 & 8.8.4.4 to the router DNS Servers list
Still no internet.
The article on setting up a home network didn’t have anything new.
As a matter of fact, it didn’t have an details of how to set up a network.
Pepwave router in eth2
ping 192.168.50.1
PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data.
64 bytes from 192.168.50.1: icmp_seq=1 ttl=64 time=0.250 ms
64 bytes from 192.168.50.1: icmp_seq=2 ttl=64 time=0.318 ms
64 bytes from 192.168.50.1: icmp_seq=3 ttl=64 time=0.291 ms
ip route
default via 192.168.50.1 dev ens2 proto dhcp metric 100
192.168.50.0/24 dev ens2 proto kernel scope link src 192.168.157.10 metric 100
**the computer is communicating with the router
**NetworkManager / Network Settings shows connected to device
IPv4 192.168.50.12
IPv6 fe80::3145:14cc:b664:3f1a
Hardware address: 00:12:2A:34:33:10
Default route: 192.168.50.1
DNS: 192.168.50.1 8.8.8.8 8.8.4.4
networkmanager finds the router
Connects via the browser to it’s admin app
the computer is communicating with the router
It will not provide internet, “can’t connect to the server at www.opensuse.org”
no internet
For your earlier question about a single port & router, the example above is what we are trying to get to work, but it still won’t connect to the internet.
There must be some setting that we are missing.
btw, everything should be up todate as I have used zypper dup to verify.
Thanks and hoping we can find that missing link.
What command can I use to identify my computer’s ip and gateway?
I may have found a place to put that in the router app.
I assume it is 192.168.1.1 or 127.0.0.0 or something.
When you ping 8.8.8.8 and 8.8.4.4, you are using the internet. Can you ping 195.135.221.140? That is the IP address of opensuse.org as seen in your post #32. The problem seems to be that the router reaches specific IP addresses, but fails to reach a DNS server to resolve a name like opensuse.org. Pinging with either should work, as
howard@HP-oS15KDE:~> nslookup opensuse.org
Server: 208.201.224.33
Address: 208.201.224.33#53
Non-authoritative answer:
Name: opensuse.org
Address: 195.135.221.140
Name: opensuse.org
Address: 2620:113:80c0:8::16
howard@HP-oS15KDE:~> ping 195.135.221.140
PING 195.135.221.140 (195.135.221.140) 56(84) bytes of data.
64 bytes from 195.135.221.140: icmp_seq=1 ttl=53 time=164 ms
64 bytes from 195.135.221.140: icmp_seq=2 ttl=53 time=164 ms
64 bytes from 195.135.221.140: icmp_seq=3 ttl=53 time=164 ms
64 bytes from 195.135.221.140: icmp_seq=4 ttl=53 time=163 ms
64 bytes from 195.135.221.140: icmp_seq=5 ttl=53 time=164 ms
^64 bytes from 195.135.221.140: icmp_seq=6 ttl=53 time=163 ms
64 bytes from 195.135.221.140: icmp_seq=7 ttl=53 time=163 ms
64 bytes from 195.135.221.140: icmp_seq=8 ttl=53 time=164 ms
64 bytes from 195.135.221.140: icmp_seq=9 ttl=53 time=164 ms
^C
--- 195.135.221.140 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8011ms
rtt min/avg/max/mdev = 163.587/164.132/164.534/0.548 ms
howard@HP-oS15KDE:~> ping opensuse.org
PING opensuse.org (195.135.221.140) 56(84) bytes of data.
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=1 ttl=53 time=164 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=2 ttl=53 time=164 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=3 ttl=53 time=163 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=4 ttl=53 time=164 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=5 ttl=53 time=163 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=6 ttl=53 time=163 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=7 ttl=53 time=164 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=8 ttl=53 time=165 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=9 ttl=53 time=164 ms
64 bytes from proxy-nue.opensuse.org (195.135.221.140): icmp_seq=10 ttl=53 time=164 ms
^C
--- opensuse.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9008ms
rtt min/avg/max/mdev = 163.549/164.276/165.767/0.795 ms
howard@HP-oS15KDE:~>
Is there a setting in your new router that blocks DNS access?
thanks,
ping 195.135.221.140
PING 195.135.221.140 (195.135.221.140) 56(84) bytes of data.
64 bytes from 195.135.221.140: icmp_seq=1 ttl=40 time=164 ms
64 bytes from 195.135.221.140: icmp_seq=2 ttl=40 time=161 ms
64 bytes from 195.135.221.140: icmp_seq=3 ttl=40 time=161 ms
It looks like it is connecting. Is that correct?
Is there a setting in your new router that blocks DNS access?
I will check on that
Yes, you are accessing the internet, but seem unable to use a DNS server for name resolution.
This looks to be the DNS settings available in the router app.
What do you suggest? Is this what you we looking for?
https://paste.opensuse.org/5611549 https://paste.opensuse.org/5611549
I wonder about the line in DNS Resolvers that says WAN - Disabled (Activation Required)
Do you need to register this new router with your ISP to get full internet access?
Identify your link:
erlangen:~ # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether d0:50:99:9a:e1:50 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 84:16:f9:3f:0c:01 brd ff:ff:ff:ff:ff:ff
erlangen:~ #
Find the address:
erlangen:~ # ip address show wlp3s0
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 84:16:f9:3f:0c:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.3/24 brd 192.168.178.255 scope global wlp3s0
valid_lft forever preferred_lft forever
inet6 2001:b29:308:3e01:8616:f9ff:fe3f:c01/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6832sec preferred_lft 2752sec
inet6 fe80::4711:f9ff:fe3f:c01/64 scope link
valid_lft forever preferred_lft forever
erlangen:~ #
Perform dns lookup:
erlangen:~ # host 192.168.178.3
3.178.168.192.in-addr.arpa domain name pointer erlangen.fritz.box.
erlangen:~ #
Routers are as easy as using the power outlet: Connect one end to the line. Connect the other end to the computer.
I am not familiar with your model. Mine has a nice section on dns: https://en.avm.de/service/fritzbox/fritzbox-7360/knowledge-base/publication/show/165_Configuring-different-DNS-servers-in-the-FRITZ-Box/ I selected ‘Vom Internetanbieter zugewiesene DNSv4-Server verwenden’ (‘use what is recommended by the provider’). The pepwave router has: https://download.peplink.com/manual/device_connector_user_manual_v1.0.pdf
When setting up my home network I finally came up with static addresses and delegated dns to the router by setting NETCONFIG_DNS_POLICY=“” and using the following:
karl@erlangen:~> cat /etc/resolv.conf
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
karl@erlangen:~>
That’s all I needed to configure.
How is your new router connecting to the internet? Through its internal LTE Modem? Through the WAN Ethernet Port with a cable to an external wired modem?
AFAICS the SIM card is not activated.
That was my first thoughts waaayyyy back in post #2, and the OP replied that the service was activated. Also, subsequent posts by the OP demonstrate internet connectivity eg posts #42 and #45. I also suggested in post #8 that name resolution was the issue, but I must admit I haven’t I haven’t kept track of this convoluted thread.
Got the wrong model this morning. The documentation is here: https://download.peplink.com/manual/pepwave_max_firmware_manual-fw7.pdf Section 9 Configuring the LAN Interface(s). Watch for dns settings.
Yeah, but the pic showed by the OP clearly shows it is not.
It is through an internal LTE modem and sim card.
It does connect to the internet and provide that to the house via wifi to my son’s laptop.
My computer does not have wifi, and so I am trying to connect it via ethernet lan.
I will call this morning to Pepwave to ask about the disabled WAN.
Thank you all. I know this has been frustrating and I appreciate all of the help. Every router in the past has been that simple. This one was simple for wifi, but will not provide internet to my computer via LAN for some strange reason. I appreciate everyone’s help.
The DNS “host” lookup command doesn’t find the address.
We talked about it before but did not get it resolved (#27)
host 192.168.50.10
Host 10.50.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
Does that point to anything?
Not sure if related:
Crazy long journal file in #34 & #35.
In #38, I tried to change to the Wicked network in YaST.
It was throwing errors so I returned to NetworkManager.
There is a log file available if that helps.
thank you all again, sorry this is such a pain
So if a computer connects to the router via wi-fi, it can access the internet correctly, but if a computer is cable connected, it cannot reach DNS servers? That seems very odd. Is the cable plugged into the router LAN port, not the WAN/LAN port? Could make a difference.
Your screen shot at SUSE Paste shows DNS servers for cellular WAN, and those seem to work for the wi-fi connected machine. Very strange it does not work for the cable connection. There must be a router setting somewhere that is specific to the cable LAN connection.
It is crazy, and that has been the frustration.
There are two ethernet ports on the router. Working with the provider’s tech we tried both, and both had the same results.
1- LAN & Console (preferred) we are plugged in here
2- LAN/WAN PoeIN
I am calling their tech today at lunch to see if they can provide additional help. I talked with them before coming to the forum and they thought it was a linux settings issue. That is what we have been trying to solve here. The fact that it can ping out, but still doesn’t connect the LAN over the internet is something I will bring up.
There is a new twist to this challenge. I have been working with the provider tech support and the router settings and the provider believes that there is something about the router that is just not compatible. Based on that they will refund my cost and I can pick any router/modem that accepts a sim.
What are your suggestions for a router/LTE modem that will work flawlessly with openSuse?
I would like to buy one right away and get through this all.
Thank you all for the help along the way.
A couple of last gasp efforts: is the Firmware updated to the latest version 8.0.2?
Also, your screen shot shows two DNS servers for cellular WAN, 68.28.31.30 and 68.28.31.31. Try putting those in the NetworkManager settings and see what happens.
If still no success, a different router/modem sounds like the right move. I have no knowledge to offer on that hardware.