ReachView web interface password

[ecomesana (Enrique Comesana)]

Is there a way to configure any kind of authentication to the reachview web interface.

I am setting a Reach RS+ running as base and connected to a Wifi to obtain RTK corrections. Others users are working in this network and I would like to set some basic authentication to access to the Reach View interface to avoid “accidental” changes of the configurartion.

Is there a way to achieve this? Thanks for any help or advice.

Regards
Enrique

Simple system report

app version: 2.18.0-r0
'wifi_status, interface: wlan0':
- wifi_mode: infrastructure
- ip: 192.168.137.121
  is_added: true
  is_connected: true
  is_visible: false
  mac_address: 28:ED:E0:D6:8E:01
  security: wpa-psk
  ssid: WIFIPC
  uuid: b8f79668-a128-44b8-a348-6987eba27c2d
base mode:
  base coordinates:
    accumulation: '1'
    antenna offset:
      east: '0'
      north: '0'
      up: '0'
    coordinates:
    - '0'
    - '0'
    - '0'
    format: llh
    mode: single-and-hold
  output:
    enabled: true
    format: rtcm3
    path: tcpsvr://:9000#rtcm3
    type: tcpsvr
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1010':
      enabled: true
      frequency: '1'
    '1097':
      enabled: false
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: false
  enabled: false
  pin: '***'
correction input:
  input2:
    enabled: true
    format: rtcm3
    path: hintd:***@ergnss-tr.ign.es:2101/FKP3
    send position to base: 'off'
    type: ntripcli
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RTCM3
    started: true
    version: null
  correction:
    format: RTCM3
    started: true
    version: null
  interval: 24
  overwrite: true
  raw:
    format: UBX
    started: true
    version: null
  solution:
    format: LLH
    started: true
    version: null
lora:
  air rate: '2.6'
  frequency: 868000
  output power: '6'
position output:
  output1:
    enabled: false
    format: nmea
    path: bluetooth
    type: bluetooth
  output2:
    enabled: false
    format: llh
    path: :9001
    type: tcpsvr
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh_ext
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '15'
  glonass ar mode: 'on'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: static
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '35'
  update rate: '5'

[bide]

There is no support for this at the moment. Reach is expected to be operating on a local, trusted network.

If you want to expose your corrections on an untrusted network, then you should put a computer or a router in between and only forward the TCP port necessary for the corrections.

If you are good with Linux command line, then you could potentially SSH into Reach and add some firewall rules to block the other open ports (:80, etc.). But that is just an idea - not something that there is any support for.

[ecomesana (Enrique Comesana)]

Ok, thanks a lot for the info.

Since there is no password support, is there a way to change the port/interface where ReachView is listening. I am thinking on configuring a reverse proxy to serve ReachView, and then I can configure the authentication on it and add firewall rules to the ReachView port.

I already logged on using SSH, and I was navigating the Reach system, but I could not find any configuration files related with ReachView.

Thanks again.