a few important issues

[cylent]

to begin i dont know where to put this so i'll have the admins decide.

anyways. i started to use untangle and hope to stick with it.

a few issues i need sorting before i get any further.

i would like to have untangle do the most basic tasks it offers. mostly i want to monitor people's surfing and all activities however a few issues stand.

• there is currently no speed limiting for captive portal users. pfsense and endian have that and so do some others. this would be really necessary.
  also a live usage monitor is also necessary. when bandwidth is limited how do i know who is doing what?

• then theres the issue of the reports. i have to know what each user visited. i cant enforce blocking porn sites on a 100+ users and blame everyone for visiting www.xxx.com ... specifics are very important.
  i dont have any extra server to setup for AD or Radius so it has to all be done on the same box. any solution to this is greatly appreciated?

i would like to purchase as little apps as possible because budget is limited.

please... anyone help and with details pls. thanks!

[WebFooL]

cylent,
The Captive portal is new to untangle. just bin with us since 7.0 so improvements to it is coming in every rls.

You can monitor all active sessions form the terminal with "jnettop" or "iftop".
If i have read right we should see a webgui active session in the new QOS system that is coming.

If you use Untangle as DNS and DHCP it should Nmap all your Computernames in the report or is that feature gone? Else you can manually add then under Settings on report.

[dmorris]

moving to feedback.

1) neat idea, can you post some screenshots of the other implementations you have seen that you like?

2) you need directory connector to get reports by "user" be it AD or captive portal.

[YeOldeStonecat]

If you use Untangle as DNS and DHCP it should Nmap all your Computernames in the report or is that feature gone? Else you can manually add then under Settings on report.

One issue with that though, while it's fine for home peer to peer networks, Untangle is aimed at SMB, (Small to Medium Business), and with SMB networks, the higher percentage of them will have Windows Servers running the networks..which means Active Directory. With AD, you need to have your servers and workstations use the IP(s) of the Domain Controller(s) for DNS. Not the routers IP or ISPs DNS. Most of us also prefer to have DHCP running from a DC, for better DNS registration and updates.

[WebFooL]

One issue with that though, while it's fine for home peer to peer networks, Untangle is aimed at SMB, (Small to Medium Business), and with SMB networks, the higher percentage of them will have Windows Servers running the networks..which means Active Directory. With AD, you need to have your servers and workstations use the IP(s) of the Domain Controller(s) for DNS. Not the routers IP or ISPs DNS. Most of us also prefer to have DHCP running from a DC, for better DNS registration and updates.

If there is a AD environment that the user should use Directory connector and the login script.
but in this case he had no AD or other boxes.

[sky-knight]

One issue with that though, while it's fine for home peer to peer networks, Untangle is aimed at SMB, (Small to Medium Business), and with SMB networks, the higher percentage of them will have Windows Servers running the networks..which means Active Directory. With AD, you need to have your servers and workstations use the IP(s) of the Domain Controller(s) for DNS. Not the routers IP or ISPs DNS. Most of us also prefer to have DHCP running from a DC, for better DNS registration and updates.

But you can still do this.

Configure all workstations on an IP reservation in Untangle's DHCP service
Configure the username to IP mapping options in the reports.

Poof... reports have the option of using name or address on the next run.

You want it automatic? Get the AD connector, run AD, and move forward.

[Bai Shen]

One issue with that though, while it's fine for home peer to peer networks, Untangle is aimed at SMB, (Small to Medium Business), and with SMB networks, the higher percentage of them will have Windows Servers running the networks..which means Active Directory. With AD, you need to have your servers and workstations use the IP(s) of the Domain Controller(s) for DNS. Not the routers IP or ISPs DNS. Most of us also prefer to have DHCP running from a DC, for better DNS registration and updates.

Can you elaborate on that? I'm not quite sure what you mean.

Thanks.

[proactivens]

Most people prefer their DHCP and DNS services to be offered from the domain controller, not the router. It provides a single point of network management and user management.

[Bai Shen]

Most people prefer their DHCP and DNS services to be offered from the domain controller, not the router. It provides a single point of network management and user management.

Ah, okay. The way he stated things made it seem like more than that.