Welcome, Guest. Please login or register.
Did you miss your activation email?
Wednesday 27 November 2024, 10:12:37 pm

Login with username, password and session length

Download the latest community FREE version  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Installation Support
| | |-+  Managed Logins/Office Setup
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Managed Logins/Office Setup  (Read 13896 times)
newwave
Jr. Member
*
Offline Offline

Posts: 2


« on: Tuesday 08 July 2008, 07:10:08 am »

Heya All,

I'm trying to install the Endian Community Edition firewall between our uplinks and the office switches and have gotten most everything working -- but I've got one issue that's forcing me to go back to a non firewalled setup everytime: managed logins on OS X.

Our current network setup has a Netopia router passing out DHCP leases to clients for 192.168.1.80-192.168.1.249 with the router as 192.168.1.1 and the broadcast that shows up under a client's ifconfig output is 19.168.1.255. What I did for minimal reconfiguration of clients, printers, and other network devices is set the Netopia router (uplink) to pass out leases on 192.168.0.80-192.168.0.254 and changed the router to be 192.168.0.1.

This works out and leaves me with the setup:

  Internet -> Netopia (192.168.0.1) -> Endian (192.168.1.1) -> Office

When I initially set this up everything worked fine, people got Internet, and the Endian box was passing out DHCP leases correctly. Everything works great.

The only thing that doesn't work is managed logins under OS X. It appears that after getting a lease from the Endian box, a client thinks it's broadcast should be 192.168.255.255 instead of 192.168.1.255. This is the only difference I can tell between the firewalled vs non-firewalled setup. My limited knowledge of how OS X manages logins and finds an authorative LDAP server leaves me in the dark a bit.

So I guess this breaks down into two questions:

1) Why is the Endian DHCP server telling clients the broadcast is 192.168.255.255 and how do I change this so clients end up with the correct broadcast address of 192.168.1.255?
2) Is there anything that could possibly be filtering managed login requests on the internal network? I have all proxies and filtering turned off including the outgoing firewall (not that I could see this mattering).

Any suggestions are greatly appreciated! Thanks!

Cheers-
  Austin
Logged
newwave
Jr. Member
*
Offline Offline

Posts: 2


« Reply #1 on: Thursday 10 July 2008, 07:18:17 am »

It appears that this may be related to a known bug:
   http://bugs.endian.it/view.php?id=243

I'm attempting to use 2.2 RC1 to see if that doesn't help...

Cheers-
  Austin
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.04 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com