I tried looking for it as a NFS server but it can’t be seen.
Any Ideas on how I can access the attached storage on this router?
Thanks
Steven
I tried looking for it as a NFS server but it can’t be seen.
Any Ideas on how I can access the attached storage on this router?
Thanks
Steven
Hi
Install zenmap (and nmap) and interrogate/scan the router to see what ports are open. Maybe samba or webdav.
Looks like it uses SAMBA with no authentication.
Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-01 16:48 PST
NSE: Loaded 146 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 16:48
Completed NSE at 16:48, 0.00s elapsed
Initiating NSE at 16:48
Completed NSE at 16:48, 0.00s elapsed
Initiating ARP Ping Scan at 16:48
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 16:48, 0.22s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 16:48
Completed Parallel DNS resolution of 1 host. at 16:48, 0.02s elapsed
Initiating SYN Stealth Scan at 16:48
Scanning 192.168.1.1 [1000 ports]
Discovered open port 139/tcp on 192.168.1.1
Discovered open port 80/tcp on 192.168.1.1
Discovered open port 445/tcp on 192.168.1.1
Discovered open port 53/tcp on 192.168.1.1
Discovered open port 443/tcp on 192.168.1.1
Discovered open port 9999/tcp on 192.168.1.1
Discovered open port 49152/tcp on 192.168.1.1
Discovered open port 10000/tcp on 192.168.1.1
Completed SYN Stealth Scan at 16:48, 1.27s elapsed (1000 total ports)
Initiating Service scan at 16:48
Scanning 8 services on 192.168.1.1
Completed Service scan at 16:48, 12.13s elapsed (8 services on 1 host)
Initiating OS detection (try #1) against 192.168.1.1
adjust_timeouts2: packet supposedly had rtt of -175222 microseconds. Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -175222 microseconds. Ignoring time.
NSE: Script scanning 192.168.1.1.
Initiating NSE at 16:48
Completed NSE at 16:48, 30.11s elapsed
Initiating NSE at 16:48
Completed NSE at 16:48, 0.00s elapsed
Nmap scan report for 192.168.1.1
Host is up (0.00050s latency).
Not shown: 992 closed ports
PORT STATE SERVICE VERSION
53/tcp open domain dnsmasq 2.55
| dns-nsid:
|_ bind.version: dnsmasq-2.55
80/tcp open http lighttpd 1.4.39
|_http-favicon: Unknown favicon MD5: AA4962B88D588AC5EA3B5D9B2FED5EF7
| http-methods:
|_ Supported Methods: GET HEAD POST OPTIONS
|_http-server-header: lighttpd/1.4.39
|_http-title: Linksys Smart Wi-Fi
139/tcp open netbios-ssn Samba smbd 3.X - 4.X (workgroup: WORKGROUP)
443/tcp open ssl/http lighttpd 1.4.39
|_http-favicon: Unknown favicon MD5: AA4962B88D588AC5EA3B5D9B2FED5EF7
| http-methods:
|_ Supported Methods: GET HEAD POST OPTIONS
|_http-server-header: lighttpd/1.4.39
|_http-title: Linksys Smart Wi-Fi
| ssl-cert: Subject: commonName=linksyssmartwifi.com/organizationName=Belkin International, Inc./stateOrProvinceName=California/countryName=US
| Subject Alternative Name: DNS:linksyssmartwifi.com, DNS:www.linksyssmartwifi.com, DNS:myrouter.local, DNS:WRT1900AC.home.linksys.com
| Issuer: commonName=linksyssmartwifi.com/organizationName=Belkin International, Inc./stateOrProvinceName=California/countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2017-08-03T23:39:21
| Not valid after: 2027-08-01T23:39:21
| MD5: 1a53 fedf 6cf0 60d2 9af9 1ddc 23d7 6b19
|_SHA-1: 781d 19e8 2ed3 1f9c 6db3 66af 8f3e 8c57 434b 1411
|_ssl-date: TLS randomness does not represent time
445/tcp open netbios-ssn Samba smbd 3.0.28a (workgroup: WORKGROUP)
9999/tcp open upnp TwonkyMedia UPnP (Linux 2.X.X; UPnP 1.0; pvConnect SDK 1.0; SDK 1.1)
10000/tcp open http lighttpd 1.4.39
| http-methods:
|_ Supported Methods: GET HEAD POST OPTIONS
|_http-server-header: lighttpd/1.4.39
|_http-title: 403 - Forbidden
49152/tcp open upnp Portable SDK for UPnP devices 1.6.19 (Linux 3.10.39; UPnP 1.0)
MAC Address: C0:56:27:C0:89:07 (Belkin International)
Device type: general purpose
Running: Linux 3.X
OS CPE: cpe:/o:linux:linux_kernel:3.10
OS details: Linux 3.10, Linux 3.2 - 3.16
Uptime guess: 25.331 days (since Thu Dec 7 08:52:15 2017)
Network Distance: 1 hop
TCP Sequence Prediction: Difficulty=261 (Good luck!)
IP ID Sequence Generation: All zeros
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel:2, cpe:/o:linux:linux_kernel:3.10.39
Host script results:
| nbstat: NetBIOS name: REMON-SEMPAI, NetBIOS user: <unknown>, NetBIOS MAC: <unknown> (unknown)
| Names:
| REMON-SEMPAI<00> Flags: <unique><active>
| REMON-SEMPAI<03> Flags: <unique><active>
| REMON-SEMPAI<20> Flags: <unique><active>
| \x01\x02__MSBROWSE__\x02<01> Flags: <group><active>
| WORKGROUP<1d> Flags: <unique><active>
| WORKGROUP<1e> Flags: <group><active>
|_ WORKGROUP<00> Flags: <group><active>
| smb-os-discovery:
| OS: Unix (Samba 3.0.28a)
| NetBIOS computer name:
| Workgroup: WORKGROUP\x00
|_ System time: 2018-01-02T00:48:29+00:00
| smb-security-mode:
| account_used: guest
| authentication_level: share (dangerous)
| challenge_response: supported
|_ message_signing: disabled (dangerous, but default)
|_smb2-time: Protocol negotiation failed (SMB2)
TRACEROUTE
HOP RTT ADDRESS
1 0.50 ms 192.168.1.1
NSE: Script Post-scanning.
Initiating NSE at 16:48
Completed NSE at 16:48, 0.00s elapsed
Initiating NSE at 16:48
Completed NSE at 16:48, 0.00s elapsed
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 46.27 seconds
Raw packets sent: 1037 (48.028KB) | Rcvd: 1029 (43.592KB)
Hi
So use smbclient with some debug to test the connection…
smbclient -d3 -L //<host>
smbclient -d3 //<host>/<share>
Set it up in YAST and am uploading files to it as we speak with Dolphin using cut and paste.
Can I rsync to it too? Path is smb://remon-sempai/76122BC26E8EE8EA/
That’d be a lot faster.
I assume you’re not worried about permissions etc?
Yes, you could mount it via a terminal then use rsync. For example…
sudo mount -t cifs //remon-sempai/76122BC26E8EE8EA /mnt -o username=user1,file_mode=0777,dir_mode=0777
*Mounted for r/w access as user1
rsync -r -v --progress -s ~/Downloads /mnt/share
I’m thinking it might be more sane for me to have this SAMBA share mount at boot.
Then I’d not have to mount it manually.
Seeing how this version of SAMBA is depreciated I’m starting to think this router “upgrade” wasn’t much of one.
Last firmware update was a long time ago.
Wishing my NAS that did NSF hadn’t died and taken the drives with it.
Hi
Will the router run dd-wrt?
That’s a possibility but I’d rather just have a computer with two nics running a firewall if I’m going to go to that trouble. I could double as a file and Asterisk server.