You are not logged in.

#26 2014-05-14 23:49:01

cypro
Member
Registered: 2011-08-22
Posts: 25

Re: Problems to connect via wifi on my Arch Linux

Yes that's right it is only 1 is not by mistake.

Offline

#27 2014-05-14 23:54:31

cypro
Member
Registered: 2011-08-22
Posts: 25

Re: Problems to connect via wifi on my Arch Linux

@Trilby sorry about that, I follow the steps of all you guys and I think the problem with no wlan0 is going to the rule we set before with the MAC address and so on.

Offline

#28 2014-05-14 23:55:21

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Problems to connect via wifi on my Arch Linux

Oh, I missed the steps where you tried to disable the predictable interface naming.  It seems something went wrong there.  I don't think that was useful advice to start with - there was no indication that your interface name had ever changed.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#29 2014-05-14 23:58:29

cypro
Member
Registered: 2011-08-22
Posts: 25

Re: Problems to connect via wifi on my Arch Linux

So what next?

Offline

#30 2014-05-15 01:38:40

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Problems to connect via wifi on my Arch Linux

It's your system, you need to chose how you want it set up - but you need to make a choice and stick with it.  Here is some information on what you were *trying* to do with that udev rule.  To do that right, follow the directions in that link and simply create the link to /dev/null/ (after getting rid of the file you've already created in the udev rules directory).  But I'd suggest not bothering with this at all - renaming the interface was a red herring - it has nothing to do with your issues (but still undo what you've done: delete the file you created with the new udev rule).

Once you undo the problem that was created with that new udev rule, make sure your profile has interface=XXXXXX where the X's are the actual interface name given by `ip a` (it will be wlp2s0, unless you opt for the sybolic link to /dev/null which I'd discourage at this point - in that case it would be wlan0).

At that point we'll have gone back to where we were at post 18 of this thread at which point you should have answered ewaller's question.  The result there was almost certainly *not* the same.  The end product of "not working" may have been the same, but the error message almost certainly would be different.  We'd need to know what that error message was in order to continue working on the problem.

Last edited by Trilby (2014-05-15 01:40:50)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#31 2014-05-15 11:23:46

cypro
Member
Registered: 2011-08-22
Posts: 25

Re: Problems to connect via wifi on my Arch Linux

Wonderful, I follow a wiki post and I change the interface name of the wireless card to wlan0! Moreover, I do change and the netctl profile to wlan0!

Note: sudo netctl stop or start a profile works correct.

Here is the profile file of the netctl:

Description='A simple WPA encrypted wireless connection'
Interface=wlan0
Connection=wireless
Security=wpa

IP=dhcp

ESSID='myrouter'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='232psdfsf9'
# Uncomment this if your ssid is hidden
#Hidden=yes
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:12:cc:33:2f:5e brd ff:ff:ff:ff:ff:ff
$ sudo wifi-menu
Invalid interface specification
Usage: wifi-menu [-h | --help] [-o | --obscure] [INTERFACE]

Interactively connect to a wireless network on INTERFACE using netctl.
If only one wireless interface is available, INTERFACE can be omitted.

Arguments:
  -h, --help     Show this help
  -o, --obscure  Show asterisks for the characters of the password
                 and store the password as a hexadecimal string
$ journalctl -xn
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 14:18:30 EES
May 15 14:16:04 rootuser network[701]: The interface of network profile 'profile
May 15 14:16:11 rootuser sudo[707]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session opened for u
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session closed for u
May 15 14:17:00 rootuser sudo[719]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:17:00 rootuser sudo[719]: pam_unix(sudo:session): session opened for u
May 15 14:17:42 rootuser sudo[719]: pam_unix(sudo:session): session closed for u
May 15 14:18:30 rootuser sudo[729]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session opened for u
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session closed for u
lines 1-11/11 (END)...skipping...
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 14:18:30 EEST. --
May 15 14:16:04 rootuser network[701]: The interface of network profile 'profile' is already up
May 15 14:16:11 rootuser sudo[707]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session closed for user root
May 15 14:17:00 rootuser sudo[719]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:17:00 rootuser sudo[719]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:17:42 rootuser sudo[719]: pam_unix(sudo:session): session closed for user root
May 15 14:18:30 rootuser sudo[729]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session closed for user root
$ systemctl status -l netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

May 15 14:15:55 rootuser systemd[1]: Stopped Networking for netctl profile profile1.

Now I dont know if this a problem, I have two profiles the

profile

and the

profile1

I don't think that I have never link the profiles with the netctl, but when I am stop or start a profile all looks perfect.

Offline

#32 2014-05-15 16:58:12

cypro
Member
Registered: 2011-08-22
Posts: 25

Re: Problems to connect via wifi on my Arch Linux

Finally, I am going to reinstall arch-linux because this thing is so annoying!
Thanks all of you for your time and for the help.

Offline

Board footer

Powered by FluxBB