Experimenting with pnethood in KLV

[rockedge]

I started the experiment by compiling nbtscan which is a component used by pnethood borrowed from F96-CE_3 and is 59 Kilobytes.

So far not much luck in getting network scans working yet and I am considering trying to modify the code to work with findsmb instead of nbtscan

[rockedge]

Close to getting a working scan! Something is wrong with the SED statement I think so the data string retrieved by nbtscan is not being parsed correctly.

[Sofiya]

Close to getting a working scan! Something is wrong with the SED statement I think so the data string retrieved by nbtscan is not being parsed correctly.

@rockedge
And where can I get "pnethood", I also want to dig into it

[rockedge]

F96-CE or and Fossapup64 -> /usr/local/apps/pnethood and the .desktop file in /usr/share/applications

This is what I have so far. Also take the nbtscan binary from F96-CE to complete the net scans

Screenshot.jpg (19.77 KiB) Viewed 1893 times

It isn't finding the shares and something called smbmount is missing

See if you can get it going. Can you share the mods to YASSM that you made?

[Sofiya]

I honestly don't know if YASSM works, not verified

[rockedge]

@Sofiya I am working on getting the scanning the LAN for shares, I also need the YASSM search package I think.

[Sofiya]

@Sofiya I am working on getting the scanning the LAN for shares, I also need the YASSM search package I think.

I think this is also needed, took a quick look at the code

[Sofiya]

KLA test
The general partition has been created, the only question is how to delete it now, this is the entire / root partition
it was necessary to register in Samba not / root, but one folder with some name.
hemorrhoids edit files under gtk2dialog

Turning off turned out to be much easier than it looked at first glance

[rockedge]

@Sofiya that look fantastic!

Can you share the pnethood modifications? I have not gotten the find shares function to work in KLV. I am so close to getting it going but I'd save the time bu coping what you did for KLA

[Sofiya]

@Sofiya that look fantastic!

Can you share the pnethood modifications? I have not gotten the find shares function to work in KLV. I am so close to getting it going but I'd save the time bu coping what you did for KLA

connect to samba shares
need to install programs

Code: Select all

cifs-utils -  from the box
nbtscan - from FossapupCE
arp-scan - from the box
peasyport - from FossapupCE
pnethood-0.7.i18n - from FossapupCE

- from FossapupCE

[Sofiya]

YASSM-2.7 scanner

[rockedge]

@Sofiya It appears that my problem in KLV with pnethood not finding the shares even though it is finding the servers, is caused by a difference in operation of smbclient in KLV and Puppy Linux .

the command smbclient -L <servername> -N does not return the correct information in KLV.

pnethood uses nbtscan to identify the Samba servers on the LAN. Then uses a similar smbclient syntax to probe the servers to get the shares available list from each.

The command to smbclient in KLV is not returning any shares. The server list is correctly retrieved by pnethood

In KLV-Airedale-rc15 :

Screenshot(1).jpg (19.09 KiB) Viewed 1893 times

In F96-CE :

Screenshot(5).jpg (28.31 KiB) Viewed 1896 times

[Sofiya]

@Sofiya It appears that my problem in KLV with pnethood not finding the shares even though it is finding the servers, is caused by a difference in operation of smbclient in KLV and Puppy Linux .

the command smbclient -L <servername> -N does not return the correct information in KLV.

pnethood uses nbtscan to identify the Samba servers on the LAN. Then uses a similar smbclient syntax to probe the servers to get the shares available list from each.

The command to smbclient in KLV is not returning any shares. The server list is correctly retrieved by pnethood

it seems that this is how it is because in KLA it works
@Clarity viewtopic.php?p=85821#p85821
mentioned it in the text.

interesting it might be related to the kernel .....

[Sofiya]

@Sofiya It appears that my problem in KLV with pnethood not finding the shares even though it is finding the servers, is caused by a difference in operation of smbclient in KLV and Puppy Linux .

the command smbclient -L <servername> -N does not return the correct information in KLV.

pnethood uses nbtscan to identify the Samba servers on the LAN. Then uses a similar smbclient syntax to probe the servers to get the shares available list from each.

The command to smbclient in KLV is not returning any shares. The server list is correctly retrieved by pnethood

It was possible to mount the share, except that the cmbclient does not display this in pnethood

[rockedge]

@Sofiya yes I also can mount a samba share in KLV in a terminal with smbclient.

This is in a VirtualBox machine with a bridged network adapter using a terminal to connect to the host F96-CE samba and list the shares then quit :

Screenshot(2).jpg (24.14 KiB) Viewed 1832 times

But this line will not work in KLV smbclient -L pedge210 -N

Screenshot(4).jpg (19.3 KiB) Viewed 1820 times

This is how it should look (using f96-CE_4)

Screenshot(6).jpg (26.82 KiB) Viewed 1829 times

[Sofiya]

Yes, I can not understand what is missing in KLV
complains about complains about glib

Code: Select all

 dmesg

[rockedge]

@Sofiya it seems that libsmbclient might be missing and I can not install it. Perhaps it is deprecated?

Screenshot.png (53.6 KiB) Viewed 1815 times

[stemsee]

......"Perhaps it is depreciated?"

like the Great British Pound!
.... or maybe deprecated

[rockedge]

Thunar in KLV can connect with smb:// and I think the libsmbclient is part of Thunar's connectivity ability to Samba shares on a LAN.

But this bug in the Void Linux repo version is causing the failure to list the shares and is the one thing stopping pnethood from operating as expected!

It is exactly what @Clarity was posting earlier in the KLV-Airedale-rc15 topic thread describing the problem with smbclient.

[Sofiya]

in KLA does not give errors on gtk2dialog and libglib

[wiak]

@Sofiya it seems that libsmbclient might be missing and I can not install it. Perhaps it is deprecated?

Yes it is an empty link at Void Packages right now. I suspect they are compiling a new version. Not sure what is going on, but certainly not available at the moment even though it is listed as 'current'. Hopefully that issue will resolve itself soon or you should post to the Void forum about it.

What happens if you just try to install package samba? Are there error messages regarding libsambaclient?

I note Void Linux samba client issues some years ago:


https://github.com/void-linux/void-packages/pull/17544
https://github.com/void-linux/void-packages/pull/27166
Odd if they didn't bother fixing it though... Immediately above link suggests fixed?

[wiak]

Note:
https://github.com/void-linux/void-packages/pull/27166

I've renamed libsmbclient to samba-libs and made it assume all of the core samba libraries used by both the clients in smbclient and the servers in samba. We could try to split this further, but there are a lot of interdependencies and I'm not sure it's worth the effort.

[wiak]

I'm not sure which KLV version I have just now - not the latest since taking a break.

However, after upgrading the system using xbps-install -Syu, I just did xbps-remove of samba-libs and dependencies and also smbclient and cleared out /var/cache/xbps.

Then I tried re-installing smbclient and that seemed to install fine (and it pulled in samba-libs as a dependency).

I also note that inside /usr/lib there is libsmbclient.so.0.7.0 (around 1.5 MB file).

[Sofiya]

Further examination of the Nethood code showed that we need a utility " ifconfig " .
when looking at the /usr/bin files, it turned out that it is a link to " net-tools-ifconfig " . in KLA it goes with a link to busybox, deleted that link and do it on busybox, during the test it showed that it stopped swearing at gtk2dialog

we get the download but still something is missing anyway

Code: Select all

 dmesg

[Sofiya]

smbclient still doesn't give the desired result.

[Sofiya]

gtkdialog GTK+3
may be able to fix the smbclient in the future

[Clarity]

Hello @Sofiya
ifconfig (deprecated) = ip addr (active)

Just a note

[Sofiya]

Hello @Sofiya
ifconfig (deprecated) = ip addr (active)

Just a note

because of such obsolescence, many things break

[rockedge]

@Sofiya I made a bug report at GitHub on the Void Linux repo -> https://github.com/void-linux/void-pack ... sues/43355
and also made a post on the new Void Linux forum -> https://voidforums.com/viewtopic.php?t=254

It appears that smbclient is being looked at now...........

[rockedge]

Some more interesting command line Network scan commands:

Code: Select all

# nmblookup -S __SAMBA__
192.168.254.13 __SAMBA__<00>
Looking up status of 192.168.254.13
	PEDGE210        <00> -         B <ACTIVE> 
	PEDGE210        <03> -         B <ACTIVE> 
	PEDGE210        <20> -         B <ACTIVE> 
	..__MSBROWSE__. <01> - <GROUP> B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1d> -         B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00

# nmblookup __SAMBA__
192.168.254.13 __SAMBA__<00>
# nmblookup '*'
192.168.254.135 *<00>
192.168.254.13 *<00>
192.168.254.17 *<00>
192.168.254.15 *<00>
192.168.254.121 *<00>
# nmblookup -S '*'
192.168.254.135 *<00>
Looking up status of 192.168.254.135
	PUPT110         <00> -         B <ACTIVE> 
	PUPT110         <03> -         B <ACTIVE> 
	PUPT110         <20> -         B <ACTIVE> 
	..__MSBROWSE__. <01> - <GROUP> B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1d> -         B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00

192.168.254.13 *<00>
Looking up status of 192.168.254.13
	PEDGE210        <00> -         B <ACTIVE> 
	PEDGE210        <03> -         B <ACTIVE> 
	PEDGE210        <20> -         B <ACTIVE> 
	..__MSBROWSE__. <01> - <GROUP> B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1d> -         B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00

192.168.254.15 *<00>
Looking up status of 192.168.254.15
	OPTIPLEX        <00> -         B <ACTIVE> 
	OPTIPLEX        <03> -         B <ACTIVE> 
	OPTIPLEX        <20> -         B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00

192.168.254.17 *<00>
Looking up status of 192.168.254.17
	OPTICAM         <00> -         B <ACTIVE> 
	OPTICAM         <03> -         B <ACTIVE> 
	OPTICAM         <20> -         B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00

192.168.254.121 *<00>
Looking up status of 192.168.254.121
	KLVDELL         <00> -         B <ACTIVE> 
	KLVDELL         <03> -         B <ACTIVE> 
	KLVDELL         <20> -         B <ACTIVE> 
	WORKGROUP       <00> - <GROUP> B <ACTIVE> 
	WORKGROUP       <1e> - <GROUP> B <ACTIVE> 

	MAC Address = 00-00-00-00-00-00