Linking a single PC to two networks one for printing only.

ajohnw · February 11, 2017, 8:57pm

I want to connect to a printer on another internal network so will have 2 adaptors one wired and one wifi that will just be used for printing. Looking around on the web I came across this and wonder how it can be done on opensuse


So in /etc/network/interfaces add these lines (with your own network information of course):
auto eth0
iface eth0 inet static
      address 192.168.2.2
      netmask 255.255.255.0
      up route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1

auto eth1
iface eth1 inet static
      address 192.168.3.2
      netmask 255.255.255.0
      up route add -net 192.168.3.0 netmask 255.255.255.0 gw 192.168.3.1

The page it came from states that all traffic will be automatically routed to eth0 unless an ip address of 192.168.3.x is accessed. That will go to eth1. The snippet looks like a static ip address of 192.168.3.2 to me rather than 192,168.3.x. Is the statement true? I suspect that the masks have that effect.

How can the same thing done on OpenSuse? Maybe there are other ways of achieving the same thing? The printer supports wifi direct but I prefer to avoid adding a utility to handle that.

The printer will be driven via cups. Currently the base addresses of both networks are probably the same but I can easily change that.

deano_ferrari · February 11, 2017, 9:25pm

The page it came from states that all traffic will be automatically routed to eth0 unless an ip address of 192.168.3.x is accessed. That will go to eth1. The snippet looks like a static ip address of 192.168.3.2 to me rather than 192,168.3.x. Is the statement true? I suspect that the masks have that effect.

That’s the address assigned to the eth1 interface, and so is a member of the 192.168.3.0/24 subnet.

How can the same thing done on OpenSuse? Maybe there are other ways of achieving the same thing? The printer supports wifi direct but I prefer to avoid adding a utility to handle that.

Yes, openSUSE can be configured to reach two networks without issue. You can do this via NetworkManager or wicked. Nothing exotic or complicated about it really.

ajohnw · February 11, 2017, 9:30pm

Searches for the same thing on opensuse didn’t bring up anything useful so perhaps I should have said just how do I do this with opensuse?

Preferably by editing system files but anyway really.

deano_ferrari · February 11, 2017, 9:46pm

The openSUSE Reference guide has information about network configuration but general networking knowledge is always a bonus too…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.basicnet.html

Are you wanting to do this with NM or wicked? I assume you already have the first LAN (192.168.2.0/24 network) up and running, and that you want to set up another network (192.168.3.0/24) just for printing? Are you planning to use a dedicated wireless router for this network? Something like the following perhaps?

ajohnw · February 12, 2017, 1:26am

My pc will be set up for some 192.168.x.x for the internet and dns etc plus anything else that is on the same network. Those may be wired or wireless.

The other network probably uses the same local network address range so I can change that at this end.

I then want to establish a permanent connection to the printer on the other network. Going on past problems the printer will be arranged to have a fixed IP address. The printer also has fax, and scanning. I will need to check but these are likely to be on different IP addresses as will it’s management interface. If the extras aren’t web based I may not be able to use them.

So say I set my end to 192.168.3.x and the other network is 192.168.1.x. The wifi dongle would need to be set for 192.168.1.x so that any accesses in that range goes to the other network. I had noticed that when it’s plugged in YAST lists it as eth1. I can’t currently find the ##!!!###!!!## thing. Some one must have tidied it up.

I did manage to find opensuse’s network config file but note that from the comments at the top it may not do anything any more or can be over ridden after it has run. Going on what is in that directory it looks like I’d need to create another ifcfg-XXX file for eth1. Add the parts from the snippet I posted to the one for eth0 and similar for eth1. It looks like the changes to eth0 wouldn’t be a problem but the template file shows wifi options and other things that I don’t understand. eth1 would need to take an ip address from the other network. The info that is missing from using this method is just what runs the files - maybe the directory is scanned or yet something else some where runs them via yet another script.

However the link shows how to do it all with yast so I can do it with that - maybe even see what it does to the files. One thing though. Does it understand syntax such as 192.168.3.0/24 and generate the mask from that ?

deano_ferrari · February 12, 2017, 1:46am

I did manage to find opensuse’s network config file but note that from the comments at the top it may not do anything any more or can be over ridden after it has run. Going on what is in that directory it looks like I’d need to create another ifcfg-XXX file for eth1. Add the parts from the snippet I posted to the one for eth0 and similar for eth1. It looks like the changes to eth0 wouldn’t be a problem but the template file shows wifi options and other things that I don’t understand. eth1 would need to take an ip address from the other network. The info that is missing from using this method is just what runs the files - maybe the directory is scanned or yet something else some where runs them via yet another script.

I wouldn’t suggest manually configuring of the files with your apparent level of knowledge. If you’re using wicked, then it does all the network management for you. You undertake the network interface configuration with YaST > System > Network Settings

However the link shows how to do it all with yast so I can do it with that - maybe even see what it does to the files.

That’s a good way to learn.

One thing though. Does it understand syntax such as 192.168.3.0/24 and generate the mask from that ?

You’ll need to specify network addresses and subnet masks.

BTW, you will also need to configure a network router for this ‘printer’ network. A simple approach is actually to let all printers and computers connect via DHCP, and have the router reserve specific IP addresses for given device MAC addresses. This minimises the configuration required at the host device end.

ajohnw · February 12, 2017, 11:44am

So I have to specify an address range of say 192.168.3.0/24 including the 0/24 implying an address range of .0 to .24 and also a mask to match ?

Or as per the snippet, say 192.168.3.any number that the mask allows and that will provide access according to the full range the mask allows.

My main problem with networks is jargon - on PC’s anyway. To be honest I have mixed feelings about leaving things like a network config file lying about when it should be done another way and there aught to be an explanation about on how to do it with script files as there will have been in the admin guide for my 1st suse system - Suse 9.0 bought from PC World complete with guides. I have always wondered why Suse stopped offering it like that so that. People could buy it locally in a box. I’ve been using Linux/kde ever since. Of late though I’m inclined to think it changes too often.

John

deano_ferrari · February 12, 2017, 12:15pm

This is CIDR notation ie /24 corresponds to a 255.255.255.0 subnet mask.

Here’s some references to help clarify this for you
https://en.m.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation
https://en.m.wikipedia.org/wiki/Subnetwork

tsu2 · February 15, 2017, 6:53pm

KISS (Keep it Simple)

Install a second physical NIC
The new NIC (actually both) should be automatically detected on bootup.
Open YaST > Network Settings
Assuming you’re not using Network Manager, you should see two NICs in the default window, likely one configured and the other not. The configured NIC is your original NIC when you first installed openSUSE and the unconfigured NIC is your newly added NIC.
Configure your NIC. It <must> use a network ID that’s not already used (in your case, that’s the first 3 octets of your network address, 192.168.1 ) and in your case should be a private address range… So, if you stay within Class C private addresses, the first two octets should stay the same (192.168 ). That leaves changing the third number to anything you want. Or, you can choose any other network ID, likely using some other Private network id(There are Class A and Class B private networks as well).
After the above, as you describe traffic will automatically be routed through the correct NIC (because of the dissimilar Network ID). But, depending on whether you’re using Hostnames or not, you may still need to set up some kind of name resolution. If you only have the one device (your printer) on the new network, then you may want to create an entry in your /etc/hosts file (You can also do this in YaST).

TSU

ajohnw · February 19, 2017, 6:02pm

No luck so far. If I try and access the router on the other network at 192.168.1.1 I get a network seems to exist but connection refused message. The other router which I use for web access comes up without any problems at 192.168.2.1.

I edited the hosts file as yast wouldn’t let me enter a /. I had switched my usual router to 192.168.2.x but the hosts file still showed 192.168.1. with 2 entries /20 and /24. The wireless dongle was there but not / so added /24.

I looked about on the web for any solutions but all seem to be aimed at using the dongle as a router. I did try setting it up for dns as it would be used normally but there wasn’t any scope for setting an address so set a static address 192.168.1.0/24. managed, wpa-pk passphrase and gave it the pass work in the encryption setting. The other router just states WPA2-personal, wpa encryption AES and uses a WPA-PSK key which I have entered into the encryption slot in yast.

:)Much of that is gobble de gook to me but I’ve never had any problem setting a pure router before.

The kernel supports the device directly and appears to be loading the correct module. This is it. I chose this one as it had a wps button but so far that hasn’t been of any use. It’s also been mentioned as works out of the box on Linux.

https://www.amazon.co.uk/d/us2/USB-high-performance-antennas-technology-Frequency-adjustable-Raspberry/B01C2N2O8S/ref=sr_1_20?ie=UTF8&qid=1487522798&sr=8-20&keywords=usb+wps+wifi+dongle

The usual system info asked for when people have asked about using them is these


dhcppc0:/home/john # iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:off/any  
          Mode:Managed  Frequency:5.2 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
eth0      no wireless extensions.

dhcppc0:/home/john # ifconfig
eth0      Link encap:Ethernet  HWaddr B4:B5:2F:A9:D9:6E  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23374 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16018 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:29301478 (27.9 Mb)  TX bytes:1646551 (1.5 Mb)
          Interrupt:20 Memory:dc300000-dc320000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:528 (528.0 b)  TX bytes:528 (528.0 b)

wlan0     Link encap:Ethernet  HWaddr 24:05:0F:9E:2D:20  
          inet addr:192.168.1.0  Bcast:192.168.15.255  Mask:255.255.240.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2565 (2.5 Kb)  TX bytes:5711 (5.5 Kb)

dhcppc0:/home/john # cat etc/resolv.conf
cat: etc/resolv.conf: No such file or directory                                                                                      
dhcppc0:/home/john # lspci -k | grep -A 3 -i "network"
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05)
        Subsystem: Hewlett-Packard Company Device 1589                                                                               
        Kernel driver in use: e1000e                                                                                                 
        Kernel modules: e1000e

Initially I had problems picking up the wifi signal but adding a separate usb socket stand has fixed that. It always shows 5gig now,

John

deano_ferrari · February 19, 2017, 8:47pm

Okay, so you have a wired ethernet connection for your LAN with eth0 assigned as 192.168.2.2, and can reach the internet ok as well. However, I note that wlan0 is not associated with any network so that would explain why you have no visibility of the 192.168.1.x network. Back in post #4 I illustrated how the printer network might be connected. You didn’t confirm or clarify the linking plan, so it all becomes a bit vague. In any case until wlan0 is associated with a wireless router you won’t be able to access the other network.

ajohnw · February 19, 2017, 9:52pm

I used the scan option in YAST and selected the correct wifi router. Also gave the link a name of wlan0 and also entered the pass phase into the encryption part. I think I have selected the correct encryption method. I set the network name as Other. I also tried adding a gateway address based on examples using older methods of setting this sort of thing up.

Repeating the output


wlan0     IEEE 802.11abgn  ESSID:off/any                                                                            
          Mode:Managed  Frequency:5.2 GHz  Access Point: Not-Associated                                             
          Tx-Power=20 dBm                                                                                           
          Retry short limit:7   RTS thr:off   Fragment thr:off                                                      
          Encryption key:off                                                                                        
          Power Management:off

So are you saying that Not-Associated is the problem? If so what do I have to do to fix it. I also noticed Encryption key off.

John

deano_ferrari · February 19, 2017, 11:31pm

I used the scan option in YAST and selected the correct wifi router.

Okay, I take it that you’re using wicked to manage/connect (as opposed to using NetworkManager)? If so, open a terminal window and examine the journal on the fly with

sudo journalctl -f

In another terminal do

sudo ifdown wlan0

then

sudo ifup wlan0

Any errors? Look for Copy/paste the output here for others to review.

ajohnw · February 20, 2017, 12:55am

It’s getting a bit close to midnight. In the mean time by activating a system service related to wifi - need to come back on it’s name a reboot and now I get this


dhcppc0:/home/john # iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"Blue Hills 2"  
          Mode:Managed  Frequency:5.2 GHz  Access Point: 1C:B7:2C:F2:23:34   
          Bit Rate=6 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=34/70  Signal level=-76 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

There is no signs of access when I try to access 192.168.1.1 - just using that because it should ask me to log into the other router. There is signs of activity during boot. There is no signs of activity on hot plug. YAST setting suggest that there should be.

The forgotten service name is something to do with wpa_suplicant which I assume uses it’s conf file in /etc.

Before going to bed I ran journalc… this is what was in it. I suspect the last part was due to a replug I just tried.


hcppc0:/home/john # journalctl -f
-- Logs begin at Tue 2017-02-14 14:18:11 GMT. --
Feb 19 23:50:34 dhcppc0 kernel: ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
Feb 19 23:50:34 dhcppc0 kernel: ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 000f detected
Feb 19 23:50:34 dhcppc0 kernel: ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Feb 19 23:50:34 dhcppc0 kernel: ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
Feb 19 23:50:34 dhcppc0 kernel: ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
Feb 19 23:50:34 dhcppc0 mtp-probe[3080]: checking bus 4, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2"
Feb 19 23:50:34 dhcppc0 mtp-probe[3080]: bus: 4, device: 5 was not an MTP device
Feb 19 23:50:34 dhcppc0 systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 19 23:50:35 dhcppc0 systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 19 23:50:37 dhcppc0 ModemManager[1134]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2': not supported by any plugin

John

deano_ferrari · February 20, 2017, 1:10am

This shows that you are now connected


dhcppc0:/home/john # iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"Blue Hills 2"  
          Mode:Managed  Frequency:5.2 GHz  Access Point: 1C:B7:2C:F2:23:34   
          Bit Rate=6 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=34/70  Signal level=-76 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

You should now check IP addressing and routing

ip add

ip route

Your journalctl output makes reference to ModemManager (which should only be active when NetworkManager is in use). Again, please clarify if you are using NM or wicked. Run these and report back.

sudo systemctl status NetworkManager

sudo systemctl status wicked

ajohnw · February 20, 2017, 11:09am

I rebooted to get the connection back up but this time it’s failed again, YAST installed a lot of bits and pieces when I first set it up so maybe that’s where modem… came from. I’ve certainly not installed it and apart from 2 photo apps and a couple of browsers it’s a fresh install.

Outputs - I thought managed by wicked had been mentioned already.


hcppc0:/home/john # ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b4:b5:2f:a9:d9:6e brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 24:05:0f:9e:2d:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.0/24 brd 192.168.1.255 scope global wlan0
       valid_lft forever preferred_lft forever
dhcppc0:/home/john # 
dhcppc0:/home/john # ip route
default via 192.168.2.1 dev eth0  proto dhcp 
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.0 linkdown 
192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.2 
dhcppc0:/home/john # 
dhcppc0:/home/john # systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
dhcppc0:/home/john # systemctl status wicked
● wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2017-02-20 09:40:06 GMT; 10min ago                                                                  
  Process: 1267 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)                                            
 Main PID: 1267 (code=exited, status=0/SUCCESS)                                                                                          
    Tasks: 0 (limit: 512)                                                                                                                
   CGroup: /system.slice/wicked.service                                                                                                  
                                                                                                                                         
Feb 20 09:39:57 wlan0 systemd[1]: Starting wicked managed network interfaces...                                                          
Feb 20 09:40:06 dhcppc0 wicked[1267]: lo              up                                                                                 
Feb 20 09:40:06 dhcppc0 wicked[1267]: eth0            up                                                                                 
Feb 20 09:40:06 dhcppc0 wicked[1267]: wlan0           up                                                                                 
Feb 20 09:40:06 dhcppc0 systemd[1]: Started wicked managed network interfaces.                                                           
dhcppc0:/home/john #

if down and up produced this but as it hasn’t connected this time ??? If up also doesn’t cause any re attempts to connect.


Feb 20 10:03:41 dhcppc0 wickedd[1261]: wlan0: failed to remove network                                                                   
Feb 20 10:03:52 dhcppc0 wickedd[1261]: wlan0: failed to remove network                                                                   
Feb 20 10:03:52 dhcppc0 wickedd[1261]: wlan0.setAPScan(1) failed                                                                         
Feb 20 10:03:52 dhcppc0 wickedd[1261]: ni_wpa_network_set failed: org.freedesktop.DBus.Error.UnknownMethod (Method "set" with signature "a{sv}" on interface "fi.epitest.hostap.WPASupplicant.Network" doesn't exist                                                              
                                       )                                                                                                 
Feb 20 10:03:52 dhcppc0 wickedd-nanny[1264]: device wlan0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure  
^C

To save rebooting it would be nice to get the hotplug working or is there some command that will cause the dongle to try and reconnect again. It may not have connected just down to a weak signal.

John

deano_ferrari · February 20, 2017, 11:20am

You have NetworkManager.service and wicked.service running concurrently. That is a problem. You need to decide which one you want to use and disable the other.

ajohnw · February 20, 2017, 11:47am

How come it reported this then ?


dhcppc0:/home/john # systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

YAST shows networkmanager and it’s wait on line disabled but it’s dispatched enabled. I’ve just disabled it. No activity on a
hot plug.
I have to be away for several days so can’t try other things at the moment,

:)But I’ll be back.

John

deano_ferrari · February 20, 2017, 12:28pm

ajohnw:

How come it reported this then ?


dhcppc0:/home/john # systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

Sorry, my mistake. Trying to read and post from my iPhone. I should be asleep. We can pick this up again when you’re ready.

ajohnw · February 24, 2017, 2:32pm

I tried disabling modemmanager. ifwlan0 then didn’t do anything. It proved odd to disable. Had to stop it first in yast and then disable it. Then it remained disabled. It’s now enabled again.

I tried reading some background info from the doc’s but way too much jargon for me but noticed the wicked commands. One of them produced this.


dhcppc0:/home/john # wicked show all
lo              up
      link:     #1, state up
      type:     loopback
      config:   compat:suse:/etc/sysconfig/network/ifcfg-lo
      leases:   ipv4 static granted
      addr:     ipv4 127.0.0.1/8 [static]

eth0            up
      link:     #2, state up, mtu 1500
      type:     ethernet, hwaddr b4:b5:2f:a9:d9:6e
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth0
      leases:   ipv4 dhcp granted
      addr:     ipv4 192.168.2.2/24 [dhcp]
      route:    ipv4 default via 192.168.2.1 proto dhcp

wlan0           setup-in-progress
      link:     #3, state device-up, mtu 1500
      type:     wireless
      config:   compat:suse:/etc/sysconfig/network/ifcfg-wlan0
      leases:   ipv4 static granted
      addr:     ipv4 192.168.1.0/24 [static]

It shows setup-in-progress for ever. The compat I assume means it using the older style of files.

Anyway ifdown wlan0 and ifup wlan0 produced this wicked log.

dhcppc0:/home/john # journalctl -f
-- Logs begin at Tue 2017-02-14 14:18:11 GMT. --
Feb 24 13:07:53 dhcppc0 kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 24 13:07:53 dhcppc0 kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 24 13:07:53 dhcppc0 kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb 24 13:07:53 dhcppc0 kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Feb 24 13:07:53 dhcppc0 kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Feb 24 13:08:10 dhcppc0 su[3499]: (to root) john on pts/0
Feb 24 13:08:10 dhcppc0 su[3499]: pam_unix(su:session): session opened for user root by john(uid=1000)
Feb 24 13:08:10 dhcppc0 su[3499]: pam_systemd(su:session): Cannot create session: Already running in a session
Feb 24 13:08:15 dhcppc0 wickedd-nanny[1255]: device wlan0: got signal linkDown
Feb 24 13:08:15 dhcppc0 wickedd-nanny[1255]: wlan0: failed to bring up device, still continuing
Feb 24 13:08:41 dhcppc0 avahi-daemon[1097]: Withdrawing address record for 192.168.1.0 on wlan0.
Feb 24 13:08:41 dhcppc0 avahi-daemon[1097]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.0.
Feb 24 13:08:41 dhcppc0 avahi-daemon[1097]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 24 13:08:55 dhcppc0 wpa_supplicant[1106]: ioctl[SIOCSIWFREQ]: Device or resource busy
Feb 24 13:08:55 dhcppc0 kernel: wlan0: authenticate with 1c:b7:2c:f2:23:34
Feb 24 13:08:55 dhcppc0 kernel: wlan0: send auth to 1c:b7:2c:f2:23:34 (try 1/3)
Feb 24 13:08:55 dhcppc0 kernel: wlan0: authenticated
Feb 24 13:08:55 dhcppc0 kernel: wlan0: associate with 1c:b7:2c:f2:23:34 (try 1/3)
Feb 24 13:08:55 dhcppc0 kernel: wlan0: RX AssocResp from 1c:b7:2c:f2:23:34 (capab=0x11 status=0 aid=1)
Feb 24 13:08:55 dhcppc0 kernel: wlan0: associated
Feb 24 13:08:55 dhcppc0 systemd-udevd[3737]: Process '/usr/sbin/crda' failed with exit code 255.
Feb 24 13:08:55 dhcppc0 kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 1c:b7:2c:f2:23:34
Feb 24 13:08:56 dhcppc0 wickedd[1252]: wlan0: No duplicates for IP address 192.168.1.0 detected
Feb 24 13:08:56 dhcppc0 avahi-daemon[1097]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.0.
Feb 24 13:08:56 dhcppc0 avahi-daemon[1097]: New relevant interface wlan0.IPv4 for mDNS.
Feb 24 13:08:56 dhcppc0 avahi-daemon[1097]: Registering new address record for 192.168.1.0 on wlan0.IPv4.
Feb 24 13:08:56 dhcppc0 wickedd[1252]: wlan0: Notified neighbours about IP address 192.168.1.0
Feb 24 13:08:59 dhcppc0 kernel: cfg80211: World regulatory domain updated:
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:  DFS Master region: unset
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)                              
Feb 24 13:08:59 dhcppc0 kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)                             
Feb 24 13:09:04 dhcppc0 kernel: wlan0: deauthenticated from 1c:b7:2c:f2:23:34 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)                        
Feb 24 13:09:04 dhcppc0 kernel: cfg80211: World regulatory domain updated:                                                               
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:  DFS Master region: unset                                                                      
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)            
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)                              
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)                              
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)                              
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)             
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)             
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)                             
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)                              
Feb 24 13:09:04 dhcppc0 kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)                             
^C

I assume ctrl C is the correct way to exit. Wicked ups and downs give identical results. If left running the log just repeats the same pattern.