'분류 전체보기' 카테고리의 글 목록 (61 Page)

'잡동사니'에 해당되는 글 13848건

2025.02.19 candump, cansend와 vcan
2025.02.18 NCSI (Network Controller Sideband Interface)
2025.02.18 "smart card resource manager is not running"
2025.02.18 linux can 테스트(가상 CAN IF)
2025.02.18 can-utils(cansend, candump)
2025.02.18 mosquitto for windows 계정추가
2025.02.18 acr1252u 스마트 카드 리더
2025.02.18 golang 윈도우 서비스 프로그램 작성하기
2025.02.18 윈도우 서비스 등록
2025.02.18 mosquitto service for windows

candump, cansend와 vcan

$ modprobe vcan
modprobe: ERROR: could not insert 'vcan': Operation not permitted

$ sudo modprobe vcan
$ sudo ip link add dev vcan0 type vcan

$ ifconfig
br-638c83b169eb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:d5:e6:f1:21  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:40:63:97:cb  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enxf8e43b9b776b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.108  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::81f4:65ad:f7cc:2f2c  prefixlen 64  scopeid 0x20<link>
        ether f8:e4:3b:9b:77:6b  txqueuelen 1000  (Ethernet)
        RX packets 3619726  bytes 2156366501 (2.1 GB)
        RX errors 0  dropped 106170  overruns 0  frame 0
        TX packets 1452518  bytes 317915291 (317.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 160829  bytes 14028478 (14.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 160829  bytes 14028478 (14.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.107  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::104b:d69c:878f:cfaa  prefixlen 64  scopeid 0x20<link>
        ether 8c:55:4a:28:25:bc  txqueuelen 1000  (Ethernet)
        RX packets 809871  bytes 90255020 (90.2 MB)
        RX errors 0  dropped 99865  overruns 0  frame 0
        TX packets 53067  bytes 6125665 (6.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ ifconfig -a
br-638c83b169eb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:d5:e6:f1:21  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:40:63:97:cb  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enxf8e43b9b776b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.108  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::81f4:65ad:f7cc:2f2c  prefixlen 64  scopeid 0x20<link>
        ether f8:e4:3b:9b:77:6b  txqueuelen 1000  (Ethernet)
        RX packets 3620125  bytes 2156544266 (2.1 GB)
        RX errors 0  dropped 106183  overruns 0  frame 0
        TX packets 1452676  bytes 317938700 (317.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 160841  bytes 14030154 (14.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 160841  bytes 14030154 (14.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vcan0: flags=128<NOARP>  mtu 72
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.107  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::104b:d69c:878f:cfaa  prefixlen 64  scopeid 0x20<link>
        ether 8c:55:4a:28:25:bc  txqueuelen 1000  (Ethernet)
        RX packets 809990  bytes 90270371 (90.2 MB)
        RX errors 0  dropped 99877  overruns 0  frame 0
        TX packets 53074  bytes 6126348 (6.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ sudo ifconfig vcan0 up
$ ifconfig
br-638c83b169eb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:d5:e6:f1:21  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:40:63:97:cb  txqueuelen 0  (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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enxf8e43b9b776b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.108  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::81f4:65ad:f7cc:2f2c  prefixlen 64  scopeid 0x20<link>
        ether f8:e4:3b:9b:77:6b  txqueuelen 1000  (Ethernet)
        RX packets 3620430  bytes 2156573250 (2.1 GB)
        RX errors 0  dropped 106197  overruns 0  frame 0
        TX packets 1452764  bytes 317953427 (317.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 160841  bytes 14030154 (14.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 160841  bytes 14030154 (14.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vcan0: flags=193<UP,RUNNING,NOARP>  mtu 72
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        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)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.220.107  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::104b:d69c:878f:cfaa  prefixlen 64  scopeid 0x20<link>
        ether 8c:55:4a:28:25:bc  txqueuelen 1000  (Ethernet)
        RX packets 810099  bytes 90278671 (90.2 MB)
        RX errors 0  dropped 99889  overruns 0  frame 0
        TX packets 53074  bytes 6126348 (6.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[링크 : https://ola-page.tistory.com/66]

$ candump
candump - dump CAN bus traffic.

Usage: candump [options] <CAN interface>+
  (use CTRL-C to terminate candump)

Options:
         -t <type>   (timestamp: (a)bsolute/(d)elta/(z)ero/(A)bsolute w date)
         -H          (read hardware timestamps instead of system timestamps)
         -c          (increment color mode level)
         -i          (binary output - may exceed 80 chars/line)
         -a          (enable additional ASCII output)
         -S          (swap byte order in printed CAN data[] - marked with '`' )
         -s <level>  (silent mode - 0: off (default) 1: animation 2: silent)
         -l          (log CAN-frames into file. Sets '-s 2' by default)
         -L          (use log file format on stdout)
         -n <count>  (terminate after reception of <count> CAN frames)
         -r <size>   (set socket receive buffer to <size>)
         -D          (Don't exit if a "detected" can device goes down.
         -d          (monitor dropped CAN frames)
         -e          (dump CAN error frames in human-readable format)
         -x          (print extra message infos, rx/tx brs esi)
         -T <msecs>  (terminate after <msecs> without any reception)

Up to 16 CAN interfaces with optional filter sets can be specified
on the commandline in the form: <ifname>[,filter]*

Filters:
  Comma separated filters can be specified for each given CAN interface:
    <can_id>:<can_mask>
         (matches when <received_can_id> & mask == can_id & mask)
    <can_id>~<can_mask>
         (matches when <received_can_id> & mask != can_id & mask)
    #<error_mask>
         (set error frame filter, see include/linux/can/error.h)
    [j|J]
         (join the given CAN filters - logical AND semantic)

CAN IDs, masks and data content are given and expected in hexadecimal values.
When the can_id is 8 digits long the CAN_EFF_FLAG is set for 29 bit EFF format.
Without any given filter all data frames are received ('0:0' default filter).

Use interface name 'any' to receive from all CAN interfaces.

Examples:
candump -c -c -ta can0,123:7FF,400:700,#000000FF can2,400~7F0 can3 can8

candump -l any,0~0,#FFFFFFFF
         (log only error frames but no(!) data frames)
candump -l any,0:0,#FFFFFFFF
         (log error frames and also all data frames)
candump vcan2,12345678:DFFFFFFF
         (match only for extended CAN ID 12345678)
candump vcan2,123:7FF
         (matches CAN ID 123 - including EFF and RTR frames)
candump vcan2,123:C00007FF
         (matches CAN ID 123 - only SFF and non-RTR frames)

$ cansend vcan0
cansend - send CAN-frames via CAN_RAW sockets.

Usage: cansend <device> <can_frame>.

<can_frame>:
<can_id>#{data}          for 'classic' CAN 2.0 data frames
<can_id>#R{len}          for 'classic' CAN 2.0 data frames
<can_id>##<flags>{data}  for CAN FD frames

<can_id>:
3 (SFF) or 8 (EFF) hex chars
{data}:
0..8 (0..64 CAN FD) ASCII hex-values (optionally separated by '.')
{len}:
an optional 0..8 value as RTR frames can contain a valid dlc field
<flags>:
a single ASCII Hex value (0 .. F) which defines canfd_frame.flags

Examples:
  5A1#11.2233.44556677.88 / 123#DEADBEEF / 5AA# / 123##1 / 213##311223344 /
  1F334455#1122334455667788 / 123#R / 00000123#R3

아래는 데이터 출력 포맷 확인용

인터페이스 / CAN id / 길이 / 데이터(페이로드 길이)

receive	send
$ candump vcan0 vcan0 111 [5] 01 02 03 04 05	$ cansend vcan0 111#010203.04.05
vcan0 112 [5] 01 02 03 04 05	$ cansend vcan0 112#010203.04.05
vcan0 112 [0]	$ cansend vcan0 112#
vcan0 112 [00]	$ cansend vcan0 112##1
vcan0 112 [01] 23	$ cansend vcan0 112##123
vcan0 112 [0] remote request	$ cansend vcan0 112#R
vcan0 112 [3] remote request	$ cansend vcan0 112#R3

받는 쪽에서 CAN id 제한할 경우, 112를 받도록 설정했기에 113은 무시된다.


$ candump vcan0,112:FF	$ cansend vcan0 111#R3
vcan0 112 [3] remote request	$ cansend vcan0 112#R3
	$ cansend vcan0 113#R3
vcan0 112 [5] 01 02 03 04 05	$ cansend vcan0 112#010203.04.05
vcan0 112 [6] 01 02 03 04 05 06	$ cansend vcan0 112#010203.04.0506
vcan0 112 [7] 01 02 03 04 05 06 07	$ cansend vcan0 112#010203.04.0506.07
vcan0 112 [0] remote request	$ cansend vcan0 112#R $ cansend vcan0 112#R10 $ cansend vcan0 112#R100
vcan0 112 [1] remote request	$ cansend vcan0 112#R1
vcan0 112 [2] remote request	$ cansend vcan0 112#R2
vcan0 112 [8] remote request	$ cansend vcan0 112#R8

그나저나 mask 라는데 이해가 안되네..

123 = 0x7B & 0x7F0 하면 0x7B가 되어야 하니 16개에 대해서 받아들여야 할 거 같은데 왜 119에서 130 까지 12개 받아들여 질까?

$ candump vcan0,123:7F0
vcan0  120   [0]  remote request
vcan0  121   [0]  remote request
vcan0  122   [0]  remote request
  vcan0  123   [0]  remote request
  vcan0  124   [0]  remote request
  vcan0  125   [0]  remote request
  vcan0  126   [0]  remote request
  vcan0  127   [0]  remote request
  vcan0  128   [0]  remote request
  vcan0  129   [0]  remote request

$ cansend vcan0 119#R
$ cansend vcan0 120#R
$ cansend vcan0 121#R
$ cansend vcan0 122#R
$ cansend vcan0 123#R
$ cansend vcan0 124#R
$ cansend vcan0 125#R
$ cansend vcan0 126#R
$ cansend vcan0 127#R
$ cansend vcan0 128#R
$ cansend vcan0 129#R
$ cansend vcan0 130#R

저작자표시 (새창열림)

'모종의 음모 > CAN' 카테고리의 다른 글

DeviceNet CAN (0)	2025.04.01
linux can 테스트(가상 CAN IF) (0)	2025.02.18
can-utils(cansend, candump) (0)	2025.02.18
can invader (0)	2024.01.09
CAN(controller area network) (0)	2023.10.31

Posted by 구차니

NCSI (Network Controller Sideband Interface)

서버 메인보드에서 NCSI 라는 명칭이 나오길래 찾아보는 중

서버 보드에 관리용 포트로 보이는게 두개 있는데

하나는 IPMI 라고 bios에서 써있고

다른 하나는 NCSI 라고 써있다.

[링크 : https://www.lr-link.com/newsdetail/654.html]

저작자표시 (새창열림)

'하드웨어 > Server Case & board' 카테고리의 다른 글

xeon phi (0)	2025.01.03
보드에 ECC/reg 장착하기 (0)	2024.04.09
구형 시스템 메모리 클럭 제한 (0)	2024.04.05
supermicro 구형 IPMI iKVM 접속 (0)	2024.04.01
xeon에 non-ecc가 가능한가? (0)	2024.03.31

Posted by 구차니

"smart card resource manager is not running"

윈도우에서 USB 카드리더를 통해서 읽으려는데 이런 에러가 발생한다.

"smart card resource manager is not running"

보안 정책을 바꾸어주고

Local:
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options / Interactive logon: Smart card removal behvior (select any option other than "no action")

[링크 : https://github.com/actions/runner-images/discussions/9893]

smart card service / smart card remove 등을 기동하도록 해주면 된다는데

Press the Windows + R keys on your keyboard to open the Run window. Type services. msc and hit Enter.
In the services find the Smart Card service > right-click then click start.

[링크 : https://answers.microsoft.com/en-us/windows/forum/all/smart-card-resource-manager-not-running-solution/bf1b13de-a66a-413a-b62f-22b46344a92e]

일단 해결은 안됨.

저작자표시 (새창열림)

'하드웨어 > rfid_nfc_smartcard' 카테고리의 다른 글

libpcsclite 빌드 + 주의사항 (0)	2025.02.25
우분투용 스마트 카드 리더 유틸리티 (0)	2025.02.25
acr1252u 스마트 카드 리더 (0)	2025.02.18
아내 몰래(?) 회사 몰래 지르기 (0)	2025.02.14
libpcsclite 라이브러리 (0)	2025.02.14

Posted by 구차니

linux can 테스트(가상 CAN IF)

실 장비가 있으면 좋겠지만 없어도

가상 can(virtual can) 장치를 추가해서 테스트 할 수 있다.

$ sudo ip link add dev vcan0 type vcan
$ sudo ifconfig vcan0 up

[링크 : https://ola-page.tistory.com/66] socket can

[링크 : https://hn-log.tistory.com/168] CANable

저작자표시 (새창열림)

'모종의 음모 > CAN' 카테고리의 다른 글

DeviceNet CAN (0)	2025.04.01
candump, cansend와 vcan (0)	2025.02.19
can-utils(cansend, candump) (0)	2025.02.18
can invader (0)	2024.01.09
CAN(controller area network) (0)	2023.10.31

Posted by 구차니

can-utils(cansend, candump)

cansend는 보내고

candump는 받는 녀석이다.

$ cansend can0 canid#userdata

로 하면 특정 canid로 보낼 수 있고

$ cansend --help
cansend - send CAN-frames via CAN_RAW sockets.

Usage: cansend <device> <can_frame>.

<can_frame>:
<can_id>#{data}          for 'classic' CAN 2.0 data frames
<can_id>#R{len}          for 'classic' CAN 2.0 data frames
<can_id>##<flags>{data}  for CAN FD frames

<can_id>:
3 (SFF) or 8 (EFF) hex chars
{data}:
0..8 (0..64 CAN FD) ASCII hex-values (optionally separated by '.')
{len}:
an optional 0..8 value as RTR frames can contain a valid dlc field
<flags>:
a single ASCII Hex value (0 .. F) which defines canfd_frame.flags

Examples:
  5A1#11.2233.44556677.88 / 123#DEADBEEF / 5AA# / 123##1 / 213##311223344 /
  1F334455#1122334455667788 / 123#R / 00000123#R3

candump 에서는 아래와 같이 하면 특정 id로만 확인할 수 있다.

$ candump can0,canid

$ candump --help
candump: invalid option -- '-'
candump - dump CAN bus traffic.

Usage: candump [options] <CAN interface>+
  (use CTRL-C to terminate candump)

Options:
         -t <type>   (timestamp: (a)bsolute/(d)elta/(z)ero/(A)bsolute w date)
         -H          (read hardware timestamps instead of system timestamps)
         -c          (increment color mode level)
         -i          (binary output - may exceed 80 chars/line)
         -a          (enable additional ASCII output)
         -S          (swap byte order in printed CAN data[] - marked with '`' )
         -s <level>  (silent mode - 0: off (default) 1: animation 2: silent)
         -l          (log CAN-frames into file. Sets '-s 2' by default)
         -L          (use log file format on stdout)
         -n <count>  (terminate after reception of <count> CAN frames)
         -r <size>   (set socket receive buffer to <size>)
         -D          (Don't exit if a "detected" can device goes down.
         -d          (monitor dropped CAN frames)
         -e          (dump CAN error frames in human-readable format)
         -x          (print extra message infos, rx/tx brs esi)
         -T <msecs>  (terminate after <msecs> without any reception)

Up to 16 CAN interfaces with optional filter sets can be specified
on the commandline in the form: <ifname>[,filter]*

Filters:
  Comma separated filters can be specified for each given CAN interface:
    <can_id>:<can_mask>
         (matches when <received_can_id> & mask == can_id & mask)
    <can_id>~<can_mask>
         (matches when <received_can_id> & mask != can_id & mask)
    #<error_mask>
         (set error frame filter, see include/linux/can/error.h)
    [j|J]
         (join the given CAN filters - logical AND semantic)

CAN IDs, masks and data content are given and expected in hexadecimal values.
When the can_id is 8 digits long the CAN_EFF_FLAG is set for 29 bit EFF format.
Without any given filter all data frames are received ('0:0' default filter).

Use interface name 'any' to receive from all CAN interfaces.

Examples:
candump -c -c -ta can0,123:7FF,400:700,#000000FF can2,400~7F0 can3 can8

candump -l any,0~0,#FFFFFFFF
         (log only error frames but no(!) data frames)
candump -l any,0:0,#FFFFFFFF
         (log error frames and also all data frames)
candump vcan2,12345678:DFFFFFFF
         (match only for extended CAN ID 12345678)
candump vcan2,123:7FF
         (matches CAN ID 123 - including EFF and RTR frames)
candump vcan2,123:C00007FF
         (matches CAN ID 123 - only SFF and non-RTR frames)

저작자표시 (새창열림)

'모종의 음모 > CAN' 카테고리의 다른 글

candump, cansend와 vcan (0)	2025.02.19
linux can 테스트(가상 CAN IF) (0)	2025.02.18
can invader (0)	2024.01.09
CAN(controller area network) (0)	2023.10.31
mcp2515 can (0)	2023.10.30

Posted by 구차니

mosquitto for windows 계정추가

결국은(?) password_file을 지정해서 mosquitto_passwd 명령을 통해 계정을 추가해주면 끝 인듯

1. password.txt 이름으로 비어있는 파일을 생성하여 Mosquitto가 설치된 폴더에 저장
2. 계정 추가
C:\mosquitto>mosquitto_passwd -b password.txt admin password

3. mosquitto.conf 파일 수정
allow_anonymous false
password_file C:\Program Files\mosquitto\password.txt

[링크 : https://hays99.tistory.com/189]

[링크 : https://mosquitto.org/man/mosquitto_passwd-1.html]

+

2025.02.21

"Program Files" 때문에 공백이 있어서 "로 묶어 줘야 할 줄 알았는데, 해주면 안되도록 구현이 되어있나 보다.

C:\Program Files\mosquitto>mosquitto -c mosquitto.conf -v
1740101165: mosquitto version 2.0.20 starting
1740101165: Config loaded from mosquitto.conf.
1740101165: Error: Unable to open pwfile ""C:\Program Files\mosquitto\password.txt"".
1740101165: Error opening password file ""C:\Program Files\mosquitto\password.txt"".

저작자표시 (새창열림)

'프로그램 사용 > mosquitto' 카테고리의 다른 글

mosquitto qos (0)	2025.04.18
mosquitto service for windows (0)	2025.02.18
CC2531 zigbee - mqtt (0)	2025.01.07
ubuntu MQTT(mosquito) (0)	2024.05.23
mosquitto - MQTT broker (0)	2019.05.15

Posted by 구차니

acr1252u 스마트 카드 리더

윈도우 10에 연결해보니 아래와 같이 나오는데

일단 제조사는 Advanced Card Systems Ltd 이고

SDK를 받아 실행하는데 목록에 안뜬다.. 왜지?

[링크 : https://www.ravirajtech.com/downloads/ACR1252/SDK/]

코드를 뒤져보니

"ACR122" 로 검색하는 소스라 ACR1252 와는 매칭되지 않아 안뜨는거 아닌가 생각된다.

수정하고 리빌드 해봐야하나..

저작자표시 (새창열림)

'하드웨어 > rfid_nfc_smartcard' 카테고리의 다른 글

우분투용 스마트 카드 리더 유틸리티 (0)	2025.02.25
"smart card resource manager is not running" (0)	2025.02.18
아내 몰래(?) 회사 몰래 지르기 (0)	2025.02.14
libpcsclite 라이브러리 (0)	2025.02.14
rfid, smart card reader (0)	2025.02.12

Posted by 구차니

golang 윈도우 서비스 프로그램 작성하기

리눅스에서 일반실행파일을 systemctl에 등록해서 실행하는것과 다르게

윈도우에서는 윈도우 서비스 api를 통해서 구동을 해야 정상적으로 구동된다.

일반적인 네트워크 echo 프로그램을 빌드해서 실행해보니

서비스 등록 문제 없음

서비스 실행 -> 실행중 -> 중지됨 으로 어느정도 시간이 지난후 멈춰버린다.

[링크 : https://pkg.go.dev/golang.org/x/sys/windows/svc]

[링크 : http://golang.site/go/article/116-윈도우즈-서비스-프로그램]

[링크 : http://www.toughman.pe.kr/2020/09/gogolang-언어로-윈도우즈-서비스-프로그램-만들기/]

저작자표시 (새창열림)

'Programming > golang' 카테고리의 다른 글

golang 정적웹 파일 포함하기 (0)	2025.11.24
go vet (golang 정적분석) (0)	2025.10.02
golang tcp socket timeout 주기(listen, read) (0)	2024.04.08
golang reflect (0)	2024.02.20
golang echo i18n (0)	2024.02.19

Posted by 구차니

윈도우 서비스 등록

심심해서(?) go로 작성한 echo 서버를 크로스빌드하고 서비스 등록했는데

"시작중"이 뜨다가 "종료됨"으로 떠버린다.

프로그램이 서비스로 작동하기 위해서는 일반적인 프로그램을 실행하면 안되는건가 싶기도 한데..

빌드는 아래와 같이 하고

$ go mod ninit
$ go mod init echo
$ go mod tidy
$ GOOS=windows go build

[링크 : https://github.com/venilnoronha/tcp-echo-server]

[링크 : https://dadev.tistory.com/entry/GO-Windows-macOS-및-Linux용-Go-프로그램을-교차-컴파일하는-방법]

한번 그냥 실행해서 방화벽 예외 추가해주고, 관리자 권한의 콘솔에서 아래와 같이 입력해주면 끝

C:\Windows\system32>sc create "echo service" binPath= "c:\echo\echo.exe 9000 hello"
[SC] CreateService 성공

C:\Windows\system32>sc delete "echo service"
[SC] DeleteService 성공

[링크 : https://blog.naver.com/battle50/220311915822]

특이하게도 옵션 이름에 =가 붙어야 해서 =" 하면 안된다.

테스트는 리눅스에서 아래와 같이 테스트 하면 끝. telnet에서 ctrl-c,d,z를 다 패스시키니

ctrl-[ 를 이용해서 메뉴로 나와 종료해야 한다.

$ telnet 192.168.220.253 9000
Trying 192.168.220.253...
Connected to 192.168.220.253.
Escape character is '^]'.

hello
d
hello d
^]
telnet> quit
Connection closed.

[링크 : https://superuser.com/questions/486496/how-do-i-exit-telnet]

저작자표시 (새창열림)

'Microsoft > Windows' 카테고리의 다른 글

윈도우 서비스 프로그램 기본 실행 경로(?) (0)	2025.02.21
윈도우 콘솔창(cmd)에서 환경변수 확인하기 (0)	2025.02.21
sdelete for win (0)	2025.02.04
윈도우 11 캡쳐키(prtscr) 캡쳐 프로그램 연동 끄기 (0)	2025.01.05
윈도우 11 인터넷 없이 설치하기 (0)	2024.12.20

Posted by 구차니

mosquitto service for windows

공식 다운로드는 아래인데

[링크 : https://mosquitto.org/download/]

받아도 방화벽 설정은 하나도 안되고 내부에서만 허용되는 설정으로 설치가 된다.

그러니 외부 접속이 필요하면 아래 내용을 참고하여 인바운드 1883/tcp를 허용해주어야 한다.

[링크 : https://velog.io/@foxiq/MQTT-사용]

윈도우 64bit로 설치했을 경우 C:\Program Files\mosquitto\mosquitto.conf 에 설정 파일이 저장된다.

굳이 listener 1883 0.0.0.0 으로 해주진 않아도 외부 접속을 허용하게 되는 것으로 보인다.

# =================================================================
# Listeners
# =================================================================

# Listen on a port/ip address combination. By using this variable
# multiple times, mosquitto can listen on more than one port. If
# this variable is used and neither bind_address nor port given,
# then the default listener will not be started.
# The port number to listen on must be given. Optionally, an ip
# address or host name may be supplied as a second argument. In
# this case, mosquitto will attempt to bind the listener to that
# address and so restrict access to the associated network and
# interface. By default, mosquitto will listen on all interfaces.
# Note that for a websockets listener it is not possible to bind to a host
# name.
#
# On systems that support Unix Domain Sockets, it is also possible
# to create a # Unix socket rather than opening a TCP socket. In
# this case, the port number should be set to 0 and a unix socket
# path must be provided, e.g.
# listener 0 /tmp/mosquitto.sock
#
# listener port-number [ip address/host name/unix socket path]
#listener
listener 1883
allow_anonymous true

+

2025.02.21

포트를 바꿀 경우 -p 로 바꾸어 주고

다른 서버일 경우 -h ip를 추가해주면 된다.

C:\Program Files\mosquitto>mosquitto_sub -p 27839 -t topic -u username -P password

C:\Program Files\mosquitto>mosquitto_pub -p 27839 -t MY -u username -P password -m asdf

+

allow_anonymous true가 없으면 아래 에러가 발생한다.

Connection error: Connection Refused: not authorised.

전체 테스트 과정은 아래와 같다.

윈도우 (서버)	다른 PC/linux (클라이언트)
1. 프로그램 설치
2. 방화벽 설정
3. conf 파일 수정 및 서비스 재기동
4. client 접속 C:\Program Files\mosquitto>mosquitto_sub.exe -t MY_TOPIC	4. client 접속 $ mosquitto_sub -v -h 192.168.0.11 -t MY_TOPIC
5. publish C:\Program Files\mosquitto>mosquitto_pub.exe -t MY_TOPIC -m HELLO
	6. 메시지 확인 HELLO -v 시에는 MY_TOPIC HELLO

---

Just edit Mosquitto configuration file ( /etc/mosquitto/conf.d/mosquitto.conf ) adding these lines...
allow_anonymous true
listener 1883 0.0.0.0

[링크 : https://stackoverflow.com/questions/24556160/mosquitto-client-obtain-refused-connection]

[링크 : https://iotmaker.kr/2021/08/23/mosquitto-remote-access-for-windows/]

[링크 : https://blog.naver.com/loyz/222654739136]

[링크 : https://pros2.tistory.com/137]

저작자표시 (새창열림)

'프로그램 사용 > mosquitto' 카테고리의 다른 글

mosquitto qos (0)	2025.04.18
mosquitto for windows 계정추가 (0)	2025.02.18
CC2531 zigbee - mqtt (0)	2025.01.07
ubuntu MQTT(mosquito) (0)	2024.05.23
mosquitto - MQTT broker (0)	2019.05.15

Posted by 구차니

구차니의 잡동사니 모음

'잡동사니'에 해당되는 글 13848건

candump, cansend와 vcan

'모종의 음모 > CAN' 카테고리의 다른 글

NCSI (Network Controller Sideband Interface)

'하드웨어 > Server Case & board' 카테고리의 다른 글

"smart card resource manager is not running"

'하드웨어 > rfid_nfc_smartcard' 카테고리의 다른 글

linux can 테스트(가상 CAN IF)

'모종의 음모 > CAN' 카테고리의 다른 글

can-utils(cansend, candump)

'모종의 음모 > CAN' 카테고리의 다른 글

mosquitto for windows 계정추가

'프로그램 사용 > mosquitto' 카테고리의 다른 글

acr1252u 스마트 카드 리더

'하드웨어 > rfid_nfc_smartcard' 카테고리의 다른 글

golang 윈도우 서비스 프로그램 작성하기

'Programming > golang' 카테고리의 다른 글

윈도우 서비스 등록

'Microsoft > Windows' 카테고리의 다른 글

mosquitto service for windows

'프로그램 사용 > mosquitto' 카테고리의 다른 글

카테고리

공지사항

태그목록

최근에 올라온 글

최근에 달린 댓글

티스토리툴바