Let see my setup environment:
Server:
- Arch Linux 4.2.5-1-ARCH
- samba Version 4.3.3
Client:
Same as server
Network Setup:
Internet - Server(192.168.1) - Router(192.168.2) - Clients
= = =
Setup procedure:
1. Installation: (For both server and client)
#pacman -Syu samba
2. Setup config
I have made a config file to share the server /tmp folder and allow only me and home subnet only.
= = =
[global]
workgroup = WORKGROUP
server string = Samba Server
hosts allow = 192.168.1. 127.
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/%m.log
max log size = 50
security = user
dns proxy = no
invalid users = nobody root
map to guest = Bad User
max connections = 10
[homes]
comment = Home Directories
browseable = no
writable = yes
[tmp]
comment = Temporary file space
path = /tmp
valid users = your_user
public = no
writable = yes
= = =
Configure your user to samba, and enter the user password.
#pdbedit -a -u your_user
3. Run
In server:
#systemctl enable smbd.service
If you also need netbios support:
#systemctl enable nmbd.service
Server side should be more or less ready and change to Client
Client:
Just test the samba connection to the server
user@localhost:~$ smbclient -L 192.168.1.1 -U your_user
smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it
Enter your_user's password:
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.3.3]
Sharename Type Comment
--------- ---- -------
tmp Disk Temporary file space
IPC$ IPC IPC Service (Samba Server)
your_user Disk Home Directories
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.3.3]
Server Comment
--------- -------
LOCALHOST Samba Server
Workgroup Master
--------- -------
WORKGROUP LOCALHOST
If you see similar output, the connection should be ready and you can mount remote samba drive
#mount -t cifs //LOCALHOST/tmp /mnt -o user=your_user,workgroup=WORKGROUP,ip=192.168.1.1
password:
Nice and Done!!
2015年12月20日 星期日
2015年12月16日 星期三
[How To] Fix Tearing on Linux Intel Graphics
#cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection
Works well on my arch linux machine. No tearing now in watching One Punch Man~ Cheers
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection
Works well on my arch linux machine. No tearing now in watching One Punch Man~ Cheers
2015年5月23日 星期六
[How To] turn arch linux box to a wireless Access Point in the simplest way
Access point setting may be a little difficult for general linux user, I would like to introduce a one step way to use your linux box with a USB wifi dongle to change it to a wireless AP
1. Identify your USB wifi dongle support AP mode or not.
In order to turn your USB wifi to Access Point, your USB dongle must support AP Mode. you may check if it is supported by following:
$iw list
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* 00-0f-ac:10
* GCMP (00-0f-ac:8)
* 00-0f-ac:9
* CMAC (00-0f-ac:6)
* 00-0f-ac:13
* 00-0f-ac:11
* 00-0f-ac:12
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point ...
If you plug in your usb dongle and the Supported Interface modes do not have the "AP" mode, you need another usb module. Most likely for my personsal recommendation Atheros Chipset is a good choice.
2. Introduce to you a create_ap script. You may find it in the following link:
https://bbs.archlinux.org/viewtopic.php?pid=1269258
or from AUR
https://aur.archlinux.org/packages/create_ap/
Just install it and with the dependencies.
Just simply run a command
#create_ap wlan0 eth0 MyAccessPoint MyPassPhrase
And it is Done!! How come it is so easy.
There is a word for Chinese People "前人種樹後人蔭" "People plant trees, childen cools under tree"
Thanks for open source
1. Identify your USB wifi dongle support AP mode or not.
In order to turn your USB wifi to Access Point, your USB dongle must support AP Mode. you may check if it is supported by following:
$iw list
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* 00-0f-ac:10
* GCMP (00-0f-ac:8)
* 00-0f-ac:9
* CMAC (00-0f-ac:6)
* 00-0f-ac:13
* 00-0f-ac:11
* 00-0f-ac:12
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point ...
If you plug in your usb dongle and the Supported Interface modes do not have the "AP" mode, you need another usb module. Most likely for my personsal recommendation Atheros Chipset is a good choice.
2. Introduce to you a create_ap script. You may find it in the following link:
https://bbs.archlinux.org/viewtopic.php?pid=1269258
or from AUR
https://aur.archlinux.org/packages/create_ap/
Just install it and with the dependencies.
Just simply run a command
#create_ap wlan0 eth0 MyAccessPoint MyPassPhrase
And it is Done!! How come it is so easy.
There is a word for Chinese People "前人種樹後人蔭" "People plant trees, childen cools under tree"
Thanks for open source
2015年3月16日 星期一
New Computer - migrate arch linux from AMD to intel
For years my computer is used, it was found dead after 7 years of working of my AMD Computer. After recover from sadness, I bought new parts to fix it. As the original one was using DDR2 which is quite outdated, I bought a new (not means fast) CPU and mainboard.
Let see the migration spec:
Original Config:
AMD Athlon II X2 240e
J&W Nvidia Geforce 8200 Mainboard
2GB x4 DDR2 RAM
GPU: nvidia onboard
New Config:
Intel Pentium G3258
Asrock B85 Mainboard
8GB x1 DDR3 RAM
GPU: intel onboard
Software:
Arch Linux 3.18.6-ARCH 64bit
After connect everything, computer bootup as usual. It boot up successfully to console user login.
The following is not work:
1. X
2. network
For the network part as the interface index was changed, just amend the configuration on netctl, the dnsmasq (dhcp server and dns provider) and dhcp client and everything works great. Just a reminder that the service of original setting was still running, and these services should be stopped.
For X windows, as I original was using the open-source driver xf86, what I need to do is uninstall nouveau, remove all the configurations and install package "xf86-video-intel" from pacman and it works!!
Let see the migration spec:
Original Config:
AMD Athlon II X2 240e
J&W Nvidia Geforce 8200 Mainboard
2GB x4 DDR2 RAM
GPU: nvidia onboard
New Config:
Intel Pentium G3258
Asrock B85 Mainboard
8GB x1 DDR3 RAM
GPU: intel onboard
Software:
Arch Linux 3.18.6-ARCH 64bit
After connect everything, computer bootup as usual. It boot up successfully to console user login.
The following is not work:
1. X
2. network
For the network part as the interface index was changed, just amend the configuration on netctl, the dnsmasq (dhcp server and dns provider) and dhcp client and everything works great. Just a reminder that the service of original setting was still running, and these services should be stopped.
For X windows, as I original was using the open-source driver xf86, what I need to do is uninstall nouveau, remove all the configurations and install package "xf86-video-intel" from pacman and it works!!
2015年3月7日 星期六
[How to] bind volume keys on Thinkpad X61 on arch linux
[How to] bind volume keys on Thinkpad X61 on arch linux
Org:
http://mizupc8.bio.mie-u.ac.jp/pukiwiki/index.php?ArchLinux%2FThinkPad%20X61
I don't know japanese but it works as expected. Cool
= = = Quote = = =
Org:
http://mizupc8.bio.mie-u.ac.jp/pukiwiki/index.php?ArchLinux%2FThinkPad%20X61
I don't know japanese but it works as expected. Cool
= = = Quote = = =
ThinkPad X61 での ArchLinux の設定に関するページです。
Volume キー †
画面の照度調整などは標準インストールで使えるようになったが、Awesome WM ではボリュームの調整ボタンが使えなかった。xbindkeys パッケージをインストールして、設定ファイルに volume キーに関する記述をすればよい。% sudo pacman -S xbindkeys 依存関係を解決しています... 相互衝突をチェックしています... パッケージ (1): xbindkeys-1.8.6-1 Total Download Size: 0.02 MiB Total Installed Size: 0.05 MiB :: インストールを行いますか? [Y/n] y :: パッケージを取得します ... xbindkeys-1.8.6-1-x... 20.5 KiB 133K/s 00:00 [######################] 100% (1/1) キーリングのキーを確認 [######################] 100% (1/1) パッケージの整合性をチェック [######################] 100% (1/1) パッケージファイルのロード [######################] 100% (1/1) ファイルの衝突をチェック [######################] 100% (1/1) 空き容量を確認 [######################] 100% (1/1) インストール xbindkeys [######################] 100% xbindkeys の提案パッケージ tk: xbindkeys_show % xbindkeys -d > ~/.xbindkeysrc以下の内容を ~/.xbindkeysrc に追加。
# Increase volume #"amixer set Master 2dB+" ←dBで指定すると、Invalid command で不可だった。 "amixer set 'Master' 5%+" XF86AudioRaiseVolume # Decrease volume #"amixer set Master 2dB-" "amixer set 'Master' 5%-" XF86AudioLowerVolume # Toggle mute "amixer set Master toggle" XF86AudioMute.xinitrc に awesome を起動する前に xbindkeys を実行するよう記述する。
xbindkeys ←追加
exec awesome
訂閱:
文章 (Atom)