Results 1 to 5 of 5
  1. #1
    Untangler
    Join Date
    Jan 2015
    Posts
    97

    Default Change LCX IP - sensible move?

    Hi

    I followed the excellent instructions to install Pihole over here: https://forums.untangle.com/hacks/43...-untangle.html

    I want to change the IP address of the pihole server - given this is running within lcx can I do this and is it sensible!?! I want to either sit it on a new subnet or give it an address on an existing UT internal lan.

    Can I do this?

    I appreciate I am already in the land of the unsupported.

    Thanks in advance.

  2. #2
    Untangler
    Join Date
    Jan 2015
    Posts
    97

    Default

    Hi

    Sorry to post a duplicate and heaven knows why I did not spot the earlier post!

    https://forums.untangle.com/hacks/44...ge-lxc-ip.html

    So - can we add a second container with its own defined IP address - and has that been documented anywhere?

    I want to give the container an address on one of the existing INTERNAL subnets.

    Thanks Guys
    Last edited by BestGear; 12-12-2021 at 04:00 AM.

  3. #3
    Untangler
    Join Date
    May 2008
    Posts
    573

    Default

    I am by no way an expert on this so take it for what it is worth. Looks like lxc uses br.lxc. If you do "ip a" you get this.
    Code:
    5: br.lxc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
        link/ether 9a:05:23:5e:f8:da brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.1/30 brd 192.0.2.3 scope global br.lxc
           valid_lft forever preferred_lft forever
        inet6 fe80::9805:23ff:fe5e:f8da/64 scope link 
           valid_lft forever preferred_lft forever
    So 192.0.2.1/30 only gives three available addresses. .1 is the bridge and .3 is the broadcast address. So not sure what that means exactly but not much room for changing addresses.

    Good luck.
    BestGear likes this.

  4. #4
    Untangler
    Join Date
    Jan 2015
    Posts
    97

    Default

    Quote Originally Posted by donhwyo View Post
    I am by no way an expert on this so take it for what it is worth. Looks like lxc uses br.lxc. If you do "ip a" you get this.
    Code:
    5: br.lxc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
        link/ether 9a:05:23:5e:f8:da brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.1/30 brd 192.0.2.3 scope global br.lxc
           valid_lft forever preferred_lft forever
        inet6 fe80::9805:23ff:fe5e:f8da/64 scope link 
           valid_lft forever preferred_lft forever
    So 192.0.2.1/30 only gives three available addresses. .1 is the bridge and .3 is the broadcast address. So not sure what that means exactly but not much room for changing addresses.

    Good luck.
    Thank you....I need to look into creating another container and assign it to an existing internal lan.....which I assume must be possible.

    I guess I could just continue with the 192.0.2.2 address, but that kinds grates as its not one of the internal lans so to speak1

    Thanks

  5. #5
    Untangler
    Join Date
    Mar 2018
    Location
    Toronto, Ontario
    Posts
    83

    Default

    Quote Originally Posted by BestGear View Post
    Thank you....I need to look into creating another container and assign it to an existing internal lan.....which I assume must be possible.

    I guess I could just continue with the 192.0.2.2 address, but that kinds grates as its not one of the internal lans so to speak1

    Thanks
    Initially, that was my thoughts too that pihole ip be part of the internal lan, then i realized that there is literally no difference from 192.0.2.2 compared to my 192.168.1.x internal lan. It's all cosmetics.

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