Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27
  1. #21
    Newbie
    Join Date
    Jul 2009
    Location
    Vermont
    Posts
    3

    Default

    Let's see if this helps Fogozito...

    After I got ssh going I did the following;

    I logged into Untangle web console to add a Packet Filter.

    config,
    Networking,
    Advanced (upper right hand corner),
    Packet Filter

    I then added this rule.

    Destination Port: 5432
    Protocol: tcp
    Source Interface: internal

    Then I ssh into untangle and changed the postgres.conf file so the server was listening on my internal nic.

    #------------------------------------------------------------------------------
    # CONNECTIONS AND AUTHENTICATION
    #------------------------------------------------------------------------------

    # - Connection Settings -

    listen_addresses = 'localhost,10.1.0.1' # what IP address(es) to listen
    on;
    # comma-separated list of addresses;
    # defaults to 'localhost', '*' = all
    # (change requires restart)
    port = 5432 # (change requires restart)
    max_connections = 100 # (change requires restart)

    NOTE: 10.1.0.1 is the IP of my internal nic and you should change this to yours

    Then I changed the pg_hba.conf file to allow a connection from my internal network.

    # IPv4 local connections:
    host all all 127.0.0.1/32 trust
    host all all 10.1.0.1/22 trust

    Now restart postgres
    /etc/init.d/ postgreql-8.3 restart

    Run netstat –an | grep 5432 to make sure that the server is listening.

    Then I used pgAdim III to create an user call root and give that user a good password.

    I then went back to pg_hba.conf and changed it so only root can login from my internal nic.

    # IPv4 local connections:
    host all all 127.0.0.1/32 trust
    host all root 10.1.0.1/22 trust


    When all is said and done you should have the server listening on local and your internal nic, but only root is able to login on your internal nic.

    Note: All files I changed for postgres are found in /etc/postgresql/8.3/main/

  2. #22
    Untanglit
    Join Date
    Feb 2009
    Location
    Alsace, France
    Posts
    26

    Default

    Would these instructions work on the 7.4 version of prostgres.conf?

  3. #23
    Newbie
    Join Date
    Jul 2009
    Location
    Vermont
    Posts
    3

    Default

    I have only done it with 7.3, so I am not sure... sorry

  4. #24
    Untanglit
    Join Date
    Jul 2009
    Location
    Bangkok
    Posts
    16

    Question

    Does anyone have an easy to use script to get this done in Untangle 7? I'm still struggling getting the report data out in some way, maybe this can work.

  5. #25
    Master Untangler GhostyDog's Avatar
    Join Date
    Jul 2007
    Posts
    154

    Default

    Quote Originally Posted by doubleduh View Post
    Does anyone have an easy to use script to get this done in Untangle 7? I'm still struggling getting the report data out in some way, maybe this can work.
    Maybe this should be a feature of untangle without having to hack about the config?

    It'd be nice to have an extra tab under reports where you can just 'switch on' the functionality to connect to the db remotely.

  6. #26
    Untangle Ninja dwasserman's Avatar
    Join Date
    Jun 2008
    Location
    Argentina
    Posts
    4,375

    Default

    I propose an idea:
    Let us agree on which tools to use, and create a common script repository, with tipical querys (per user, per day, per mail account, etc, its a big cube of information), and how to automate and schedule them.
    I propose use OBDC and cristal report, because generate better presentations, but , obviously is open to others tool, i am not a script guru.
    If we can add multiple efforts in one way, is better for all.

  7. #27
    Untanglit
    Join Date
    Feb 2009
    Location
    Alsace, France
    Posts
    26

    Default

    I'm a hopeless DBA (in a former life), so I'm going to suggest that at least we be able to suggest SQL queries that would work. From that point, people could use those queries in pretty much whatever tool they wanted to... though I understand that simply dumping a larger subset of the data and using other non-SQL-oriented tools may be prefered by those who don't enjoy coding SQL queries.

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2