Thanks guys. I'll try to find out why mine does not work. And, yes, it's TW of 12/19. On Wed, Dec 26, 2018 at 6:57 PM Patrick Shanahan <paka@opensuse.org> wrote:

* Chuck Davis <cjgunzel@gmail.com> [12-26-18 21:49]:

...

Does NetworkManager only work with DHCP ?? And, if so, why?

It's been my experience that I cannot configure a static IP anymore.

Thanks if anybody knows about this.

I have had no problem configuring a static "local" ip on tw.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 27/12/2018 03:51, James Knott wrote:

On 12/26/2018 09:46 PM, Chuck Davis wrote:

...

Does NetworkManager only work with DHCP ?? And, if so, why?

I It works fine with static IPs to.  I have several I can select from on my notebook computer.

I have a strange wifi problem on 2 Tumbleweed boxes - slipstream and tindog where no IP addresses show up but wifi works perfectly. slipstream -- With out an IP address I am ssh logged in over wifi to a number of boxes -- Tumbleweed, Leap 15,Ubuntu aarch64 and Kubuntu x86_64 18.10. =========== wlp1s0f0u14: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500         ether ce:b1:51:16:05:a3  txqueuelen 1000  (Ethernet)         RX packets 0  bytes 0 (0.0 B)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 0  bytes 0 (0.0 B) slipstream:/c1/usr/src # ping 192.168.0.41 PING 192.168.0.41 (192.168.0.41) 56(84) bytes of data. 64 bytes from 192.168.0.41: icmp_seq=1 ttl=63 time=4.45 ms 64 bytes from 192.168.0.41: icmp_seq=2 ttl=63 time=1.81 ms slipstream:/c1/usr/src # ping 192.168.0.8 PING 192.168.0.8 (192.168.0.8) 56(84) bytes of data. 64 bytes from 192.168.0.8: icmp_seq=1 ttl=63 time=1.34 ms PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. 64 bytes from 192.168.0.2: icmp_seq=1 ttl=63 time=38.3 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=63 time=60.10 ms tindog ======= wlp0s19f2u4: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500         ether 4e:11:8c:b2:ab:39  txqueuelen 1000  (Ethernet)         RX packets 99  bytes 26970 (26.3 KiB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 56  bytes 8513 (8.3 KiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 siddly (Leap15 laptop) ================== wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 192.168.0.8  netmask 255.255.255.0  broadcast 192.168.0.255         inet6 fe80::d50a:27:c4ae:5a9c  prefixlen 64  scopeid 0x20<link>         ether 00:1f:3b:af:b3:ed  txqueuelen 1000  (Ethernet)         RX packets 5168308  bytes 3537319468 (3.2 GiB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 2396254  bytes 223151500 (212.8 MiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 sabre ===== wlp0s19f2u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500         inet 192.168.0.41  netmask 255.255.255.0  broadcast 192.168.0.255         inet6 fe80::22cf:30ff:fec5:2044  prefixlen 64  scopeid 0x20<link>         ether 20:cf:30:c5:20:44  txqueuelen 1000  (Ethernet)         RX packets 86880  bytes 19908885 (18.9 MiB)         RX errors 0  dropped 4072  overruns 0  frame 0         TX packets 32106  bytes 3231742 (3.0 MiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 slipstream:/c1/usr/src # nmap -sT 192.168.0.0/24 Starting Nmap 7.70 ( https://nmap.org ) at 2018-12-27 11:43 GMT Nmap scan report for 192.168.0.1 Host is up (0.0036s latency). Not shown: 994 filtered ports PORT     STATE  SERVICE 23/tcp   closed telnet 80/tcp   open   http 443/tcp  closed https 1900/tcp open   upnp 5000/tcp open   upnp 8080/tcp closed http-proxy Nmap scan report for 192.168.0.2 Host is up (0.015s latency). Not shown: 999 closed ports PORT   STATE SERVICE 22/tcp open  ssh Nmap scan report for 192.168.0.3 Host is up (0.0083s latency). All 1000 scanned ports on 192.168.0.3 are closed Nmap scan report for siddly.site (192.168.0.8) Host is up (0.0014s latency). Not shown: 999 closed ports PORT   STATE SERVICE 22/tcp open  ssh Nmap scan report for 192.168.0.11 Host is up (0.00032s latency). Not shown: 996 filtered ports PORT    STATE SERVICE 53/tcp  open  domain 81/tcp  open  hosts2-ns 222/tcp open  rsh-spx 444/tcp open  snpp Nmap scan report for 192.168.0.19 Host is up (0.011s latency). Not shown: 999 closed ports PORT   STATE SERVICE 22/tcp open  ssh Nmap scan report for 192.168.0.41 Host is up (0.010s latency). Not shown: 999 closed ports PORT   STATE SERVICE 22/tcp open  ssh Nmap done: 256 IP addresses (7 hosts up) scanned in 147.21 seconds Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org