Hi
I have a dual boot Opensuse Leap15/Ubuntu 18.04 system on HP G2 laptop with 4g modem.
In ubuntu all works fine
In opensuse I added the connection in KDE - all default options -my carrier was listed.
The modem get’s connected - receives default route, IP assignment, DNS
but for some reason no data is being sent/received - not even a simple
ping 8.8.8.8 works
I even tried shytting down FW completely but nothing - all packages are being dropped.
I reported a bug but it seems like not many ppl look into this one - if any at all
There’s nothing in the log snippet you submitted in the bug report that suggests an issue here. It showed that an IP address, default gateway. and DNS were provided. You can always check these against the assigned addresses and routes using…
ip a
ip r
grep name /etc/resolv.conf
BTW, I would have tried pinging the gateway and DNS address(es) first. Ideally, commands and output should be posted here to demonstrate success or failure of these.
laprus:/home/polrus # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 70:5a:0f:60:ac:14 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether da:cd:7c:24:9b:dd brd ff:ff:ff:ff:ff:ff
7: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 7a:c6:53:8c:bf:03 brd ff:ff:ff:ff:ff:ff
inet 100.98.234.244/29 brd 100.98.234.247 scope global noprefixroute wwan0
valid_lft forever preferred_lft forever
inet6 fe80::ea46:9bf3:d28c:3030/64 scope link noprefixroute
valid_lft forever preferred_lft forever
laprus:/home/polrus # ip route show
default via 100.98.234.241 dev wwan0 proto static metric 20700
100.98.234.240/29 dev wwan0 proto kernel scope link src 100.98.234.244 metric 700
The networking seems to be ok, and no problems reported in NM log. Ubuntu 18.04 will be using a newer kernel, so you could try testing with a more recent kernel I guess
zypper ar -f http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ kernel
Hi, thanks for being interested in helping,
I’d follow the advise but I actually tested with the latest tumbleweed and still does not work.
Tried disabling apparmor and fw and nothing.
Ok, good to know. The fact that you get an IP address assigned, and assuming a valid default gateway, it’s not clear why you can’t reach the internet. I guess a bug report is required.
Tried disabling apparmor and fw and nothing.
I didn’t think these would be relevant factors here.
A couple items of note…
You pinged yourself, not your DG so you really didn’t test network connectivity…
I made your DG bold red in the quote above…
Your log also curiously says that your system reconfigured itself to use a multi-cast network configuration instead of your original network settings, so I’m guessing that’s where you’re blocking yourself… Your firewall probably isn’t configured to allow the new network configuration. I guess you’re trying to play some Internet game? Curious thing though, the address you <seem> to be using isn’t part of the reserved address space for multi-casting. What provider are you connecting to?
For testing purposes only, I’d suggest you drop your firewall long enough to verify that allows network traffic, if my suspicion is verified then you can go about identifying the multi-cast network settings you need to enable. If you think you dropped your firewall, describe how you did it, via YaST or stopping the firewall service… and if the latter what command you used.
Hmmm - i’m not a network guru but still GW for me is a host and in ubuntu I’m able to ping it.
What you marked red seems to be a subnet/broadcast not a host right?
Anyway i tried to the broadcast using ping -b with no reply.
In ubuntu (where it works) it the same connection is also multicast
Am theorizing that despite your posted network information, it may still not be what your router expects. This can be caused by multi-booting because each OS presents the same MAC address to DHCP, if this is determined to be the problem then you might be able to configure a different IP address in Network Manager (or possibly interface configuration files).
To test whether this is the problem, try restarting your network service to re-acquire/refresh your network settings to see if that makes a difference