Page 5 of 15 FirstFirst ... 34567 ... LastLast
Results 41 to 50 of 146
  1. #41
    Untangle Ninja Silver Bullet's Avatar
    Join Date
    Sep 2007
    Posts
    1,946

    Default

    Good. I will add the DHCP stuff to the instructions.

    So everything is working then I take it?

  2. #42
    Master Untangler
    Join Date
    Apr 2008
    Posts
    136

    Default

    Sure is had to make those three changes (DHCP in DMZ, and the two I mentioned) and it is golden.

  3. #43
    Untangler
    Join Date
    May 2008
    Posts
    80

    Default Additional WLAN NIC's

    Hello,
    Any other NIC's that are compatible with Untangle 5.2? My untangle server is in a rack, I'd like to have something with an external antenna that can be mounted to the exterior of the rack for better reception.

    Thanks,
    Tim

  4. #44
    Untangle Ninja Silver Bullet's Avatar
    Join Date
    Sep 2007
    Posts
    1,946

    Default

    I think that as long as you get a card that is based on the Atheros chipset then these instructions should work fine for you.

  5. #45
    Untangler geniehost's Avatar
    Join Date
    Jun 2008
    Posts
    72

    Exclamation

    Quote Originally Posted by Silver Bullet View Post
    The Port Forward rule should look EXACTLY like the screen shot... forward to 192.0.2.42.
    I cannot understand why you make the port forward to this IP: 192.0.2.42 ?!

  6. #46
    Untangle Ninja Silver Bullet's Avatar
    Join Date
    Sep 2007
    Posts
    1,946

    Default

    Quote Originally Posted by geniehost View Post
    I cannot understand why you make the port forward to this IP: 192.0.2.42 ?!
    192.0.2.42 is the listening interface in Untangle that handles block pages/administration. In order for the wireless clients to be able to receive the block page or administer the UT server in this setup, the port has to be forwarded to that address and a packet filter rule has to be created to allow the traffic you are forwarding.

    Hope that clears it up for you.

  7. #47
    Untangler geniehost's Avatar
    Join Date
    Jun 2008
    Posts
    72

    Default

    Quote Originally Posted by Silver Bullet View Post
    Now the bridge information is loaded into /etc/network/interfaces automatically by Alpaca.
    I just do it as the instructions, but Alpaca not updating interfaces file!

    please refer to the screenshots


    what I have to do now to create the bridge?

    regards,
    Genie

  8. #48
    Untangle Ninja Silver Bullet's Avatar
    Join Date
    Sep 2007
    Posts
    1,946

    Default

    Run this
    Code:
    cat /etc/network/interfaces
    and post the output. I'm betting that the changes aren't being written there by Alpaca. I ran into this on my last install and just manually entered the info after I saved the config in Alpaca. I think it's a bug but haven't had time to look further into it.

  9. #49
    Untangler geniehost's Avatar
    Join Date
    Jun 2008
    Posts
    72

    Default

    I already post the content of the file as image in my last replay

    but again I will post it here:
    Code:
    ## Fri Jun 13 18:14:11 +0300 2008
    ## Auto Generated by the Untangle Net Alpaca
    ## If you modify this file manually, your changes
    ## may be overriden
    
    auto cleanup
    iface cleanup inet manual
    
    ## Configuration for the loopback interface
    auto lo
    iface lo inet loopback
    
    
    auto br.eth0
    iface br.eth0 inet dhcp
            alpaca_bridge_ports eth2 eth0
            bridge_ageing 900
            alpaca_bridge_mtu 1500
    
    auto ath0
    iface ath0 inet manual
            pre-up wlanconfig ath0 destroy
            pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
            post-down wlanconfig ath0 destroy
    	pre-up iwconfig ath0 channel 11
    	wireless-mode master
    
    auto eth1
    iface eth1 inet static
    	address 10.196.192.200
    	netmask 255.255.255.0
    	mtu 1500
    
    ## This will run any scripts that need to execute when the address changes.
    auto update
    iface update inet manual
    Silver Bullet, thanks for your quick replay

  10. #50
    Untangle Ninja Silver Bullet's Avatar
    Join Date
    Sep 2007
    Posts
    1,946

    Default

    You are going to need to manually edit the /etc/network/interfaces file like so and then reboot the server. Once it finishes rebooting, check ifconfig to make sure that you have a br.eth1 interface and that it is assigned the 10.196.192.200 address.

    replace:
    Code:
    auto eth1
    iface eth1 inet static
    	address 10.196.192.200
    	netmask 255.255.255.0
    	mtu 1500
    with:
    Code:
    auto br.eth1
    iface br.eth1 inet manual
            alpaca_bridge_ports ath0 eth1
            bridge_ageing 900
            alpaca_bridge_mtu 1500
    	address 10.196.192.200
    	netmask 255.255.255.0

Page 5 of 15 FirstFirst ... 34567 ... LastLast

Tags for this Thread

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