Dobrodošli na FOSS Srbija

Free and Opensource Srbija je skup entuzijasta i ljubitelja slobodnog i otvorenog koda. Cilj nam je okupiti sve istomišljenike na jednom mestu i stvoriti najveći globalni OpenSource projekat u Srbiji i šire!

  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Debian Rešeno Posle instalcije sistema wireless problem s Network Manager

Discussion in 'Debian, LinuxMint, Ubuntu' started by Ladislav, 19.12.2017.

  1. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    Prilikom net-instalacije Stretch-xfce prepozanje moju wifi mrežu, uradim instalaciju. A kad podignem sistem, Network Manager vidi wifi mrežu (available) ali se ne povezuje.


    Raniji pokušaji uz traženje rešenja od Google, nisu dali rezultat kao ni sa instalacijom firmware i non-free firmware za moju mašinu. Te sam rešavao ili instalacijom Wicd ili instaliram Jessie pa upgrade na Stretch i onda wifi radi normalno.

    E sad pokušavam da to rešim direktno iz Stretch-a.
    Sistem je svež instal, uradjena samo početna podešavanja.

    Nisam još ništa pokušao u vezi wifi, čekam neku ideju, rešenje? :)
     
  2. muzicar

    Korisnik

    Joined:
    29.03.2012
    Messages:
    275
    Likes Received:
    187
    Location:
    Zrenjanin
    Okruženje:
    Ostalo
    Sistem:
    Ostalo
    Mozda glupo pitanje sa moje strane, ali da li ti je instaliran paket wpasupplicant. Inace ja koristim Wicd, posto po meni je bolji za podesavanje i upravljanje wifi mrezom. Inace imam usb wifi karticu kupljenu preko Aliexpressa za smesne pare.

    Sada vidim da je wpasupplicant jedan od zavisnosti instalacije Network managera
     
  3. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    instaliran je wpasupplicant.

    Wifi s Wicd radi, nije mi baš bitan NM, ali sam mislio da je bolji. U TRIOS smo izbacivali wicd, pa sam zato upro :)

    A inače koristim usb Ralink
    Code:
    Bus 008 Device 003: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter
    
    NM i wicd wiraless:

    NM_wicd1.jpg

    Da nije do kernela 4.9 i moje stare mašine iz 2008 ili mog (ne) znanja šta kako podesit/doinstalirati na Stretch?

    Code:
    ASUSTeK Computer INC.
    Model Maximus Formula (LGA775)
    CPU: Intel Core2 Quad CPU Q6600 @ 2.394GHz
    
    Date    28-Nov-08
    Imam na metalu instaliran i Jessie updejtovan na Stretch, na kojem mi wifi s NM nastavio da radi normalno. Te ću probati da uporedim instalirane pakete.
     
    #3 Ladislav, 19.12.2017
    Last edited: 19.12.2017
  4. muzicar

    Korisnik

    Joined:
    29.03.2012
    Messages:
    275
    Likes Received:
    187
    Location:
    Zrenjanin
    Okruženje:
    Ostalo
    Sistem:
    Ostalo
    Koliko vidim u NM appletu cita ti i Ethernet (wired) konekciju, da li ti je racunar istovremeno ukljucen na mrezu i wifi? Da tu ne dolazi do nekog konflikta? Moj racunar na kom je Debian je kupljen 2008 god. dok smo uzivali u malom PDV-u na IT opremu, i nemam tih problema. Jedino sto sam se opredelio za Wicd je sto je manji paket, i po meni je lakse podesavanje i uravljanje wifi mrezom.
     
  5. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    Inaće ne koristim net kabel, sad mi je ostao utaknut zbog instalacije wicd.
    Mada mislim da nije problem do toga, jer na Jeesie nema sukoba interesa, mogu da biram bez problema mrežu.

    e ako je tako, onda mogu zaključiti temu :) ... ili da je ostavim radi nauke :)
     
  6. muzicar

    Korisnik

    Joined:
    29.03.2012
    Messages:
    275
    Likes Received:
    187
    Location:
    Zrenjanin
    Okruženje:
    Ostalo
    Sistem:
    Ostalo
    Cekaj da neko malo iskusniji kaze svoje misljenje, ovo i mene interesuje
     
  7. joytoy

    Korisnik

    Joined:
    28.10.2017
    Messages:
    54
    Likes Received:
    62
    Okruženje:
    KDE 5
    Sistem:
    Kubuntu
    Zbog čega tačno neće da se poveže, šta izbacuje kao problem?
     
    Collapse Signature Expand Signature
  8. OpenSuse

    Guest

    U

    /etc/NetworkManager/NetworkManager.conf

    ubaciti sledeće

    [device]
    wifi.scan-rand-mac-address=0

    restart sistema

    i wifi će da radi .
     
    Tanja and Ladislav like this.
  9. Tanja

    Korisnik

    Joined:
    19.03.2013
    Messages:
    645
    Likes Received:
    494
    Okruženje:
    XFCE
    Sistem:
    Debian
    @Ladislav

    NM zna da zeza i ja ga ne koristim, ali imala sam sa njim jedno tupavo iskustvo još na Jessie.
    Probaj da se povežeš na wifi mrežu, izvadiš "žicu", pa rebutuj sistem.
    Mislim da sam na nekim forumima nailazila na komentare da neće da "reaguje" NM ako nije sistem podignut nakon (prvog) prijavljivanja na wifi, i da sam ja tako rešila problem, ali sam posle maknula to čudo.
     
    #9 Tanja, 19.12.2017
    Last edited: 19.12.2017
  10. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    jedino iskoči pop-up prozor
    Code:
    Disconnected
    
    The network connection has beeen disconnected
    A evo kako izgleda kad je mrežni kabel priključen i dostupne wifi mreže:

    20171219_170550.jpg


    Ne mogu se povezati na wifi s NM.

    Bunilo me, jer kad instaliram Jessie kernel 3.16 wifi radi s NM i upgradim na Stretch - kernel 9.0.4 wifi radi. Mislio da je greška do mene.
    Nisam znao da je NM tako mušićav.
    Interesantno da propoznaje wifi prilikom net-instalacije, uradim instalaciju izborom putem wifi, zapamti passwod od wifi a posle dizanja OS-a problem.
    Koristiću wicd za wifi nije problem.
     
  11. joytoy

    Korisnik

    Joined:
    28.10.2017
    Messages:
    54
    Likes Received:
    62
    Okruženje:
    KDE 5
    Sistem:
    Kubuntu
    Možeš da okačiš sadržaj syslog-a u trenutku kad se to dešava? Da vidimo šta ga tačno buni. :)
     
    Collapse Signature Expand Signature
  12. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    ne kontam baš, na šta misliš "... u trenutku kad se to dešava?"

    Ali evo deo syslog-a
    Dec 19 21:01:30 deb-pc NetworkManager[613]: <info> [1513713690.3243] manager: NetworkManager state is now DISCONNECTED
    Dec 19 21:01:30 deb-pc NetworkManager[613]: <warn> [1513713690.3253] device (wlx74ea3a88ee9c): Activation: failed for connection 'cisco'
    Dec 19 21:01:30 deb-pc NetworkManager[613]: <info> [1513713690.3261] device (wlx74ea3a88ee9c): state change: failed -> disconnected (reason 'none') [120 30 0]
    Dec 19 21:01:30 deb-pc kernel: [ 2473.004547] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:01:30 deb-pc NetworkManager[613]: <info> [1513713690.7317] device (wlx74ea3a88ee9c): set-hw-addr: set MAC address to CA:1A:54:B2:BF:4F (scanning)
    Dec 19 21:01:31 deb-pc kernel: [ 2473.911086] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:01:32 deb-pc NetworkManager[613]: <info> [1513713692.8585] device (wlx74ea3a88ee9c): supplicant interface state: disconnected -> inactive
    Dec 19 21:02:29 deb-pc kernel: [ 2532.439454] sky2 0000:04:00.0 enp4s0: Link is up at 1000 Mbps, full duplex, flow control both
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7616] device (enp4s0): link connected
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7623] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7634] policy: auto-activating connection 'Wired connection 1'
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7650] device (enp4s0): Activation: starting connection 'Wired connection 1' (f5fa1746-1123-319c-af83-ddd2531135c3)
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7653] device (enp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7655] manager: NetworkManager state is now CONNECTING
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7662] device (enp4s0): state change: prepare -> config (reason 'none') [40 50 0]
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7668] device (enp4s0): state change: config -> ip-config (reason 'none') [50 70 0]
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7673] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
    Dec 19 21:02:29 deb-pc NetworkManager[613]: <info> [1513713749.7698] dhcp4 (enp4s0): dhclient started with pid 2379
    Dec 19 21:02:29 deb-pc dhclient[2379]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 5
    Dec 19 21:02:31 deb-pc avahi-daemon[606]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::b9ec:548a:eb42:835f.
    Dec 19 21:02:31 deb-pc avahi-daemon[606]: New relevant interface enp4s0.IPv6 for mDNS.
    Dec 19 21:02:31 deb-pc avahi-daemon[606]: Registering new address record for fe80::b9ec:548a:eb42:835f on enp4s0.*.
    Dec 19 21:02:34 deb-pc dhclient[2379]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 13
    Dec 19 21:02:34 deb-pc dhclient[2379]: DHCPREQUEST of 192.168.0.32 on enp4s0 to 255.255.255.255 port 67
    Dec 19 21:02:34 deb-pc dhclient[2379]: DHCPOFFER of 192.168.0.32 from 192.168.0.1
    Dec 19 21:02:35 deb-pc dhclient[2379]: DHCPACK of 192.168.0.32 from 192.168.0.1
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5172] dhcp4 (enp4s0): address 192.168.0.32
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5173] dhcp4 (enp4s0): plen 24 (255.255.255.0)
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5173] dhcp4 (enp4s0): gateway 192.168.0.1
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5173] dhcp4 (enp4s0): server identifier 192.168.0.1
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5173] dhcp4 (enp4s0): lease time 3600
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5174] dhcp4 (enp4s0): nameserver '89.216.1.40'
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5174] dhcp4 (enp4s0): nameserver '89.216.1.50'
    Dec 19 21:02:35 deb-pc avahi-daemon[606]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.32.
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5174] dhcp4 (enp4s0): state changed unknown -> bound
    Dec 19 21:02:35 deb-pc avahi-daemon[606]: New relevant interface enp4s0.IPv4 for mDNS.
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5189] device (enp4s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
    Dec 19 21:02:35 deb-pc avahi-daemon[606]: Registering new address record for 192.168.0.32 on enp4s0.IPv4.
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5202] device (enp4s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5208] device (enp4s0): state change: secondaries -> activated (reason 'none') [90 100 0]
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5210] manager: NetworkManager state is now CONNECTED_LOCAL
    Dec 19 21:02:35 deb-pc dbus[443]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    Dec 19 21:02:35 deb-pc systemd[1]: Started Run anacron jobs.
    Dec 19 21:02:35 deb-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
    Dec 19 21:02:35 deb-pc anacron[2389]: Anacron 2.3 started on 2017-12-19
    Dec 19 21:02:35 deb-pc anacron[2389]: Normal exit (0 jobs run)
    Dec 19 21:02:35 deb-pc systemd[1]: anacron.timer: Adding 4min 19.662943s random time.
    Dec 19 21:02:35 deb-pc dbus[443]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Dec 19 21:02:35 deb-pc systemd[1]: Started Network Manager Script Dispatcher Service.
    Dec 19 21:02:35 deb-pc nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
    Dec 19 21:02:35 deb-pc nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
    Dec 19 21:02:35 deb-pc dhclient[2379]: bound to 192.168.0.32 -- renewal in 1504 seconds.
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5881] manager: NetworkManager state is now CONNECTED_GLOBAL
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5882] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
    Dec 19 21:02:35 deb-pc NetworkManager[613]: <info> [1513713755.5885] device (enp4s0): Activation: successful, device activated.
    Dec 19 21:02:35 deb-pc nm-dispatcher: req:2 'up' [enp4s0]: new request (1 scripts)
    Dec 19 21:02:35 deb-pc nm-dispatcher: req:2 'up' [enp4s0]: start running ordered scripts...
    Dec 19 21:03:20 deb-pc kernel: [ 2583.271809] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:50:39:55:a0:32:07:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
    Dec 19 21:04:32 deb-pc NetworkManager[613]: <info> [1513713872.4911] device (wlx74ea3a88ee9c): Activation: starting connection 'cisco' (8e46a47c-2e2a-4f0c-8277-fccb5e71e16a)
    Dec 19 21:04:32 deb-pc NetworkManager[613]: <info> [1513713872.4913] audit: op="connection-activate" uuid="8e46a47c-2e2a-4f0c-8277-fccb5e71e16a" name="cisco" pid=936 uid=1000 result="success"
    Dec 19 21:04:32 deb-pc NetworkManager[613]: <info> [1513713872.4916] device (wlx74ea3a88ee9c): state change: disconnected -> prepare (reason 'none') [30 40 0]
    Dec 19 21:04:32 deb-pc NetworkManager[613]: <info> [1513713872.9007] device (wlx74ea3a88ee9c): set-hw-addr: reset MAC address to 74:EA:3A:88:EE:9C (preserve)
    Dec 19 21:04:33 deb-pc kernel: [ 2656.075082] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4006] device (wlx74ea3a88ee9c): state change: prepare -> config (reason 'none') [40 50 0]
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4009] device (wlx74ea3a88ee9c): Activation: (wifi) access point 'cisco' has security, but secrets are required.
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4009] device (wlx74ea3a88ee9c): state change: config -> need-auth (reason 'none') [50 60 0]
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4098] device (wlx74ea3a88ee9c): state change: need-auth -> prepare (reason 'none') [60 40 0]
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4103] device (wlx74ea3a88ee9c): state change: prepare -> config (reason 'none') [40 50 0]
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4105] device (wlx74ea3a88ee9c): Activation: (wifi) connection 'cisco' has security, and secrets exist. No new secrets needed.
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4106] Config: added 'ssid' value 'cisco'
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4106] Config: added 'scan_ssid' value '1'
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4106] Config: added 'key_mgmt' value 'WPA-PSK'
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4106] Config: added 'psk' value '<hidden>'
    Dec 19 21:04:33 deb-pc NetworkManager[613]: <info> [1513713873.4282] device (wlx74ea3a88ee9c): supplicant interface state: inactive -> scanning
    Dec 19 21:04:34 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Trying to authenticate with 0c:54:a5:44:2a:3d (SSID='cisco' freq=2462 MHz)
    Dec 19 21:04:34 deb-pc kernel: [ 2657.619526] wlx74ea3a88ee9c: authenticate with 0c:54:a5:44:2a:3d
    Dec 19 21:04:35 deb-pc NetworkManager[613]: <info> [1513713875.0052] device (wlx74ea3a88ee9c): supplicant interface state: scanning -> authenticating
    Dec 19 21:04:35 deb-pc kernel: [ 2657.681403] wlx74ea3a88ee9c: send auth to 0c:54:a5:44:2a:3d (try 1/3)
    Dec 19 21:04:35 deb-pc kernel: [ 2657.683615] wlx74ea3a88ee9c: authenticated
    Dec 19 21:04:40 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Deauth request to the driver failed
    Dec 19 21:04:40 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="cisco" auth_failures=1 duration=10 reason=CONN_FAILED
    Dec 19 21:04:40 deb-pc NetworkManager[613]: <info> [1513713880.0116] device (wlx74ea3a88ee9c): supplicant interface state: authenticating -> disconnected
    Dec 19 21:04:50 deb-pc NetworkManager[613]: <info> [1513713890.0212] device (wlx74ea3a88ee9c): supplicant interface state: disconnected -> scanning
    Dec 19 21:04:51 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-REENABLED id=0 ssid="cisco"
    Dec 19 21:04:51 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Trying to authenticate with 0c:54:a5:44:2a:3d (SSID='cisco' freq=2462 MHz)
    Dec 19 21:04:51 deb-pc kernel: [ 2674.227659] wlx74ea3a88ee9c: authenticate with 0c:54:a5:44:2a:3d
    Dec 19 21:04:51 deb-pc NetworkManager[613]: <info> [1513713891.6127] device (wlx74ea3a88ee9c): supplicant interface state: scanning -> authenticating
    Dec 19 21:04:51 deb-pc kernel: [ 2674.289368] wlx74ea3a88ee9c: send auth to 0c:54:a5:44:2a:3d (try 1/3)
    Dec 19 21:04:51 deb-pc kernel: [ 2674.291255] wlx74ea3a88ee9c: authenticated
    Dec 19 21:04:56 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Deauth request to the driver failed
    Dec 19 21:04:56 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="cisco" auth_failures=2 duration=20 reason=CONN_FAILED
    Dec 19 21:04:56 deb-pc NetworkManager[613]: <info> [1513713896.6219] device (wlx74ea3a88ee9c): supplicant interface state: authenticating -> disconnected
    Dec 19 21:04:58 deb-pc NetworkManager[613]: <warn> [1513713898.3240] device (wlx74ea3a88ee9c): Activation: (wifi) association took too long, failing activation
    Dec 19 21:04:58 deb-pc NetworkManager[613]: <info> [1513713898.3241] device (wlx74ea3a88ee9c): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
    Dec 19 21:04:58 deb-pc NetworkManager[613]: <warn> [1513713898.3251] device (wlx74ea3a88ee9c): Activation: failed for connection 'cisco'
    Dec 19 21:04:58 deb-pc NetworkManager[613]: <info> [1513713898.3261] device (wlx74ea3a88ee9c): state change: failed -> disconnected (reason 'none') [120 30 0]
    Dec 19 21:04:58 deb-pc kernel: [ 2681.004534] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:04:58 deb-pc NetworkManager[613]: <info> [1513713898.7390] device (wlx74ea3a88ee9c): set-hw-addr: set MAC address to CA:C6:B6:54:62:4B (scanning)
    Dec 19 21:04:59 deb-pc kernel: [ 2681.915110] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:05:00 deb-pc NetworkManager[613]: <info> [1513713900.8745] device (wlx74ea3a88ee9c): supplicant interface state: disconnected -> inactive
    Dec 19 21:05:26 deb-pc kernel: [ 2709.276302] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:50:39:55:a0:32:07:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
    Dec 19 21:06:28 deb-pc NetworkManager[613]: <info> [1513713988.2103] device (wlx74ea3a88ee9c): Activation: starting connection 'cisco' (8e46a47c-2e2a-4f0c-8277-fccb5e71e16a)
    Dec 19 21:06:28 deb-pc NetworkManager[613]: <info> [1513713988.2106] audit: op="connection-activate" uuid="8e46a47c-2e2a-4f0c-8277-fccb5e71e16a" name="cisco" pid=936 uid=1000 result="success"
    Dec 19 21:06:28 deb-pc NetworkManager[613]: <info> [1513713988.2108] device (wlx74ea3a88ee9c): state change: disconnected -> prepare (reason 'none') [30 40 0]
    Dec 19 21:06:28 deb-pc NetworkManager[613]: <info> [1513713988.6195] device (wlx74ea3a88ee9c): set-hw-addr: reset MAC address to 74:EA:3A:88:EE:9C (preserve)
    Dec 19 21:06:29 deb-pc kernel: [ 2771.799066] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1246] device (wlx74ea3a88ee9c): state change: prepare -> config (reason 'none') [40 50 0]
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1249] device (wlx74ea3a88ee9c): Activation: (wifi) access point 'cisco' has security, but secrets are required.
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1249] device (wlx74ea3a88ee9c): state change: config -> need-auth (reason 'none') [50 60 0]
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1340] device (wlx74ea3a88ee9c): state change: need-auth -> prepare (reason 'none') [60 40 0]
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1345] device (wlx74ea3a88ee9c): state change: prepare -> config (reason 'none') [40 50 0]
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1348] device (wlx74ea3a88ee9c): Activation: (wifi) connection 'cisco' has security, and secrets exist. No new secrets needed.
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1349] Config: added 'ssid' value 'cisco'
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1349] Config: added 'scan_ssid' value '1'
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1349] Config: added 'key_mgmt' value 'WPA-PSK'
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1349] Config: added 'psk' value '<hidden>'
    Dec 19 21:06:29 deb-pc NetworkManager[613]: <info> [1513713989.1551] device (wlx74ea3a88ee9c): supplicant interface state: inactive -> scanning
    Dec 19 21:06:30 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Trying to authenticate with 0c:54:a5:44:2a:3d (SSID='cisco' freq=2462 MHz)
    Dec 19 21:06:30 deb-pc kernel: [ 2773.361191] wlx74ea3a88ee9c: authenticate with 0c:54:a5:44:2a:3d
    Dec 19 21:06:30 deb-pc kernel: [ 2773.433339] wlx74ea3a88ee9c: send auth to 0c:54:a5:44:2a:3d (try 1/3)
    Dec 19 21:06:30 deb-pc NetworkManager[613]: <info> [1513713990.7559] device (wlx74ea3a88ee9c): supplicant interface state: scanning -> authenticating
    Dec 19 21:06:30 deb-pc kernel: [ 2773.435113] wlx74ea3a88ee9c: authenticated
    Dec 19 21:06:35 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Deauth request to the driver failed
    Dec 19 21:06:35 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="cisco" auth_failures=1 duration=10 reason=CONN_FAILED
    Dec 19 21:06:35 deb-pc NetworkManager[613]: <info> [1513713995.7661] device (wlx74ea3a88ee9c): supplicant interface state: authenticating -> disconnected
    Dec 19 21:06:45 deb-pc NetworkManager[613]: <info> [1513714005.7709] device (wlx74ea3a88ee9c): supplicant interface state: disconnected -> scanning
    Dec 19 21:06:47 deb-pc kernel: [ 2789.967613] wlx74ea3a88ee9c: authenticate with 0c:54:a5:44:2a:3d
    Dec 19 21:06:47 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-REENABLED id=0 ssid="cisco"
    Dec 19 21:06:47 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Trying to authenticate with 0c:54:a5:44:2a:3d (SSID='cisco' freq=2462 MHz)
    Dec 19 21:06:47 deb-pc NetworkManager[613]: <info> [1513714007.3529] device (wlx74ea3a88ee9c): supplicant interface state: scanning -> authenticating
    Dec 19 21:06:47 deb-pc kernel: [ 2790.029443] wlx74ea3a88ee9c: send auth to 0c:54:a5:44:2a:3d (try 1/3)
    Dec 19 21:06:47 deb-pc kernel: [ 2790.031733] wlx74ea3a88ee9c: authenticated
    Dec 19 21:06:52 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: SME: Deauth request to the driver failed
    Dec 19 21:06:52 deb-pc wpa_supplicant[671]: wlx74ea3a88ee9c: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="cisco" auth_failures=2 duration=20 reason=CONN_FAILED
    Dec 19 21:06:52 deb-pc NetworkManager[613]: <info> [1513714012.3587] device (wlx74ea3a88ee9c): supplicant interface state: authenticating -> disconnected
    Dec 19 21:06:54 deb-pc NetworkManager[613]: <warn> [1513714014.3231] device (wlx74ea3a88ee9c): Activation: (wifi) association took too long, failing activation
    Dec 19 21:06:54 deb-pc NetworkManager[613]: <info> [1513714014.3231] device (wlx74ea3a88ee9c): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
    Dec 19 21:06:54 deb-pc NetworkManager[613]: <warn> [1513714014.3242] device (wlx74ea3a88ee9c): Activation: failed for connection 'cisco'
    Dec 19 21:06:54 deb-pc NetworkManager[613]: <info> [1513714014.3249] device (wlx74ea3a88ee9c): state change: failed -> disconnected (reason 'none') [120 30 0]
    Dec 19 21:06:54 deb-pc kernel: [ 2797.003391] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:06:54 deb-pc NetworkManager[613]: <info> [1513714014.7228] device (wlx74ea3a88ee9c): set-hw-addr: set MAC address to 7A:0F:C2:A5:48:51 (scanning)
    Dec 19 21:06:55 deb-pc kernel: [ 2797.923423] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
    Dec 19 21:06:56 deb-pc NetworkManager[613]: <info> [1513714016.8707] device (wlx74ea3a88ee9c): supplicant interface state: disconnected -> inactive
    Dec 19 21:07:32 deb-pc kernel: [ 2835.280828] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:50:39:55:a0:32:07:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
    Dec 19 21:09:38 deb-pc kernel: [ 2961.285317] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:50:39:55:a0:32:07:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
    Dec 19 21:10:06 deb-pc kernel: [ 2988.786571] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
    Dec 19 21:11:44 deb-pc kernel: [ 3087.289863] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:50:39:55:a0:32:07:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
    Dec 19 21:12:38 deb-pc NetworkManager[613]: <info> [1513714358.7598] device (wlx74ea3a88ee9c): set-hw-addr: set MAC address to 5E:7C:BB:63:B2:82 (scanning)
    Dec 19 21:12:39 deb-pc kernel: [ 3141.943084] IPv6: ADDRCONF(NETDEV_UP): wlx74ea3a88ee9c: link is not ready
     
  13. Tanja

    Korisnik

    Joined:
    19.03.2013
    Messages:
    645
    Likes Received:
    494
    Okruženje:
    XFCE
    Sistem:
    Debian
    Onda nije do kernela, ni do OS-a, već je izgleda loše "spakovan" NM u Xfce... aj da vidim šta pretraga kaže na tu temu.

    Edit:
    @Ladislav , je si li ti instalirao wicd u međuvremenu? Ako jesi, onda su te dve aplikacije u konfliktu, tj. jedna od njih mora da "leti"...
     
  14. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    Jesam instalirao wicd, brisao NM, pa vraćao NM brisao wicd e sad više ni wicd ne vidi wifi :)

    Edit
    Progutao mi prvu plovinu posta gde sam odgovorio na "...nije do kernela ...loše spakovan NM u xfce..."
    misliš, ja sam loše spakovao xfce:)
     
    #14 Ladislav, 19.12.2017
    Last edited: 19.12.2017
  15. Tanja

    Korisnik

    Joined:
    19.03.2013
    Messages:
    645
    Likes Received:
    494
    Okruženje:
    XFCE
    Sistem:
    Debian
    E do moga...
    Je li ti uopšte imaš sad net?

    Ako ne... onda ide malo tricky posao: rescue mod installera, pa onda instalacija wicd-a (po meni sigurica) ili network-manager-gnome(ta)...
     
  16. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    imam net preko mrežnog kabela i NM.
    Kasnije ću rešavati wicd, čekam da vidim šta je naumila @joytoy
     
  17. Tanja

    Korisnik

    Joined:
    19.03.2013
    Messages:
    645
    Likes Received:
    494
    Okruženje:
    XFCE
    Sistem:
    Debian
    Onda je "sve" tu... samo se pobrkalo usled igranja sa instalacijama...
    Wicd imaš? Uradi reboot, pa probaj onda da se nakačiš na wifi. Verovatno ima neka fora sa komandama, ali reboot će da pogasi sve repove od servisa pa da vidimo onda šta dalje...
     
  18. Ladislav

    Korisnik

    Joined:
    30.06.2015
    Messages:
    415
    Likes Received:
    435
    Location:
    Sombor
    Okruženje:
    XFCE
    Sistem:
    TRIOS
    probao sam restarte i ne vredi
     
  19. joytoy

    Korisnik

    Joined:
    28.10.2017
    Messages:
    54
    Likes Received:
    62
    Okruženje:
    KDE 5
    Sistem:
    Kubuntu
    Imala sam sličan, ako ne i isti problem, samo sa Realtek 8821ae. Da ne dužim priču, starije verzije kernela imaju problema sa pojedinim wi-fi adapterima/karticama.
    Na gitu sam manuelno našla drajver koji mi je trebao, nakon toga mi je sve radilo odlično, ako izuzmemo to da sam morala nekoliko puta da ga vraćam na podrazumevani posle nekih ažuriranja.

    Jesi li to pokušavao?

    Edit: wicd i običan nm bi trebalo da rade normalno i jedan pored drugog, tako da nema potrebe za brisanjem nekog od njih. Ako je neki prikačen na mrežu, drugi se samo automatski onemogućuje.
     
    Collapse Signature Expand Signature
  20. Tanja

    Korisnik

    Joined:
    19.03.2013
    Messages:
    645
    Likes Received:
    494
    Okruženje:
    XFCE
    Sistem:
    Debian
    Mislim da sam više puta pročitala da NM neće da radi ukoliko je Wicd "u akciji", naćiću već negde gde sam to videla, ali naravno, moguće je da je to bio pogrešan stav...

    @Ladislav
    Evo linka koji opisuje tvoj problem... bio je bug, ali su ga izgleda rešili... ja ne koristim NM na xfce-u uopšte....
    Can't connect to WiFi in debian 9 and Ubuntu 17.04/17.10 [FIXED]