Hello Roland, thanks for all your help. I removed the corresponding lines in the LAM source code for now to let us use our longer domain name in DHCP. It seems like this limitation has something to do with Netbios compatibility (which seems to have this 15 char domain name restriction), but is not really a DHCP restriction itself. I am not 100% sure about this, but I just cannot imagine that DHCP would seriously limit domain names to 15 characters, which would be way to short for just about every medium length domain name out there...
I have posted a feature request with some possible improvements for the DHCP interface under http://sourceforge.net/tracker/?func=detail&aid=3038797&group_id=73243&atid=537214 Best regards, Joschi Brauchle On Monday 09 August 2010 20:25:06 Roland Gruber wrote: > Hi Joschi, > > regarding the limit I will not be able to check this for about a week. > Please file a bug report for this issue. > > > Best regards > > Roland > > On 03.08.2010 11:43, Joschi Brauchle wrote: > > Hey, > > > > I reinstalled LAM from the RPM (had the manual installation before) and > > now our previous DHCP configuration is showing up correctly and editing > > is working. > > > > I just have one more smaller problem: > > Our domain name is "lnt.e-technik.tu-muenchen.de", but LAM says the > > domain name must be less than 15 characters... Is there REALLY a limit > > like this? > > > > Best regards, > > Joschi Brauchle > > > > On Tuesday 03 August 2010 10:27:15 Joschi Brauchle wrote: > >> Hello Roland, > >> > >> first of all, thanks for your help. > >> > >> I did change the LDAP suffix from > >> > >> "ou=dhcp,dc=xxx,dc=yyy" to > >> "cn=dhcpserver,ou=dhcp,dc=xxx,dc=yyy" which if of type dhcpServer. > >> > >> Within the dhcpserver, I have the configuration stored as a > >> dhcpServiceDN object. > >> > >> But unfortunately, I still get the error: > >> PHP Fatal error: Call to a member function load_attributes() on a > >> non-object in /srv/www/htdocs/lam.3.1.0/lib/modules.in > >> c on line 1708, referer: https://pollux.lnt.e-technik.tu- > >> muenchen.de/lam.3.1.0/templates/lists/list.php?type=dhcp&norefresh=true > >> > >> when clicking the "edit" button on this configuration. > >> > >> Any further ideas? > >> Thanks very much! > >> > >> -Joschi Brauchle > >> > >> On Thursday 29 July 2010 21:50:21 Roland Gruber wrote: > >>> Hi, > >>> > >>> please note that DHCP requires to use a dhcpServer entry as LDAP > >>> suffix: > >>> > >>> http://www.ldap-account-manager.org/static/doc/manual/ch03s06.html > >>> > >>> > >>> Best regards > >>> > >>> Roland > >>> > >>> On 27.07.2010 13:44, Joschi Brauchle wrote: > >>>> Hello everyone, > >>>> > >>>> I have the following problem when migrating an existing LAM 2.3.0 > >>>> installation to version 3.1.0: > >>>> > >>>> I followed the update procedure in the LAM manual, copying the > >>>> required config files from version 2.3.0 to the 3.1.0 folder, and > >>>> changed the access rights accordingly, so that should be fine. > >>>> > >>>> As our old 2.3.0 LAM did not have the DHCP account type, I added this > >>>> to our setup in the 3.1.0 preferences. > >>>> > >>>> Now comes the problem: > >>>> > >>>> All LAM 3.1.0 account types work fine, UNTIL I click on the "edit" > >>>> button on the DHCP page to edit our DHCP configuration. When I click > >>>> this edit button, I get a blank page in the browser and the Apache2 > >>>> error log reports the following error: > >>>> > >>>> PHP Fatal error: Call to a member function load_attributes() on a > >>>> non-object in /srv/www/htdocs/lam.3.1.0/lib/modules.inc on line 1708, > >>>> referer: https://pollux.lnt.e-technik.tu- > >>>> muenchen.de/lam.3.1.0/templates/lists/list.php?type=dhcp > >>>> > >>>> After this, all other "edit" buttons stop working, e.g. of the user / > >>>> groups / hosts section and they as well give a blank page with Apache2 > >>>> error: > >>>> > >>>> PHP Fatal error: Call to a member function get_cache() on a > >>>> non-object in /srv/www/htdocs/lam.3.1.0/lib/modules/posixAccount.inc > >>>> on line 470, referer: https://pollux.lnt.e-technik.tu- > >>>> muenchen.de/lam.3.1.0/templates/lists/list.php?type=user > >>>> > >>>> When I log out and back in, everything works good again until I edit > >>>> the DHCP configuration. > >>>> > >>>> So do I need to take any special actions before managing existing > >>>> LDAP-DHCP entries with LAM? So far, I just added our LDAP suffix > >>>> "ou=dhcp,dc=xxx,dc=yyy" to the DHCP account type settings. > >>>> > >>>> > >>>> Best regards, > >>>> Joschi Brauchle > >> > >> ------------------------------------------------------------------------ > >> --- --- The Palm PDK Hot Apps Program offers developers who use the > >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> of $1 Million in cash or HP Products. Visit us here for more details: > >> http://p.sf.net/sfu/dev2dev-palm > >> _______________________________________________ > >> Lam-public mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/lam-public > > > > ------------------------------------------------------------------------- > > ----- The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://p.sf.net/sfu/dev2dev-palm > > _______________________________________________ > > Lam-public mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/lam-public ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
