Re: [e-smith-devinfo] Re: procmail update worked
I'm not sure if this helps anyone, or if it could be used here... but I remember a program that autogenerates .procmail rules. Here is the url: http://www.flug.dk/lg/issue23/procmail.html Maybe this could be used as the basis for a web-based UI ??? This is all WAY past my expertise, and you may all know about the site anyway Hugh Fox Sales Director www.drcauto.com drcauto now hosts support newsgroups: news://news.drcauto.com/drcauto.lt_toolkit news://news.drcauto.com/drcauto.smart_architect news://news.drcauto.com/drcauto.accurender_lt The same groups are accessible via your browser, go to: http://discussion.drcauto.com - Original Message - From: Gordon Rowell [EMAIL PROTECTED] To: Darrell May [EMAIL PROTECTED] Cc: e-smith-devinfo [EMAIL PROTECTED] Sent: Thursday, August 30, 2001 4:17 PM Subject: Re: [e-smith-devinfo] Re: procmail update worked On Thu, Aug 30, 2001 at 03:14:24AM -, Darrell May [EMAIL PROTECTED] wrote: [...] Stephen Noble's done an initial rpm already. We collaborated on creating this HowTo: http://netsourced.com/servers/docs/procmail-howto.html Thanks for that. We've had such a flood of contributed HOWTOs (which is great to see), it's sometimes hard to keep up. Of course could always be expanded upon. Since the .procmailrc has to be edited manually, one thought would be to leave the email panel as it is and just create a customised templates-user-custom/.qmail/e-smithForward20 template. Gordon -- Gordon Rowell[EMAIL PROTECTED] VP Engineering Network Server Solutions Group http://www.e-smith.com Mitel Networks Corporation http://www.mitel.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
At 03:01 AM 30/08/2001 -0500, John Powell wrote: Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. The problem has been side-stepped by giving them fixed IP addresses as you suggest but we also concluded (in the absence of other evidence) the clients pcs were not rewnewing their addresses correctly, either by not coping with NAC or ACK correctly. Interestingly they worked ok under the earlier redhat5.2 version of samba. The wintel boxes on the net have no dhcp problems (which is why we could confidently assign fixed IPs as a workaround). We did try to fix the problem by adding host entries assigning IPs by the MAC (Media Access Controller unique number) addresses of the macs \pun but I guess for the same reason that they made a hash of dynamic dhcp, dhcp hostnaming got simillar errors - ip conflict messages. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
The problem might lay with the macintosh. I believe that system 8.5 fixed numerous bugs with 'Open Transport' (the networking software) and many DHCP issues fixed. Try updating your system softwaer or even better, upgrade to a nweer version such as 8.6 or OS9. James - Original Message - From: Graeme Robinson [EMAIL PROTECTED] To: John Powell [EMAIL PROTECTED]; Trevor Ouellette [EMAIL PROTECTED]; E-Smith Devinfo [EMAIL PROTECTED] Sent: Thursday, August 30, 2001 7:32 PM Subject: Re: [e-smith-devinfo] DHCP Server Problem?? At 03:01 AM 30/08/2001 -0500, John Powell wrote: Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. The problem has been side-stepped by giving them fixed IP addresses as you suggest but we also concluded (in the absence of other evidence) the clients pcs were not rewnewing their addresses correctly, either by not coping with NAC or ACK correctly. Interestingly they worked ok under the earlier redhat5.2 version of samba. The wintel boxes on the net have no dhcp problems (which is why we could confidently assign fixed IPs as a workaround). We did try to fix the problem by adding host entries assigning IPs by the MAC (Media Access Controller unique number) addresses of the macs \pun but I guess for the same reason that they made a hash of dynamic dhcp, dhcp hostnaming got simillar errors - ip conflict messages. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Hi John, Your answer was not wishy-washy at all. Thanks for your input. One client was a computer brought in from another office. The other client computer is an older computer that just had it's hard drive replaced... that's when it couldn't get an IP address. I've double and triplechecked the settings and I just can't figure it out. We have even tried different cables (from a known-good workstation cable). Does anyone know how to uninstall and reinstall the DHCPD component? I've upgraded the server, to no avail. Thanks, Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 2:01 AM To: Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? Trevor, Is there something different about the 2 new machines (not a common OS, etc.)? I can tell you this, the broken clients are not seeing the responses from the server. the DHCPOFFER is the server responding, the client is supposed to accept the offer (and generate a DHCPREQUEST) or reject the offer (DHCPNAK), but obviously is not. The issue is likely to be with how the DHCPOFFER is addressed. Some servers broadcast the DHCPOFFER, some unicast it to the mac address of the requester. I believe the ISC server is a bit unique and broadcasts it (may be the other way around, I would need to sniff a connection to figure that out). I would need to read the RFC for the specifics, but I believe a client is supposed to accept either method, and it is likely your problem is your clients on the 2 broken machines are not accepting the method ISC uses. The simplest fix, of course, is to assign static IPs. The more complex is to see if there is updated DHCP software for your client. Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. Hope this helps, JP --On Wednesday, August 29, 2001 7:48 PM -0600 Trevor Ouellette [EMAIL PROTECTED] wrote: I have a problem with 2 computers that have been introduced to the LAN. The ES server does not provide them with an IP address. It's not a physical network problem (they can see each other and was tested with working network cable, etc.). Here's the strange part... they request an IP address, but never receive one from the ES server. It even shows up in the logs. When I cd /etc/dhcpcd, I get a blinking dhcpc file. Is this normal? Could the DHCP Daemon have something to do with the problem? If you would like more logs, printouts, etc. please just ask... When I do a /etc/rc.d/init.d/dhcpd restart I get: /etc/rc.d/init.d/dhcpd restart Shutting down dhcpd: [ OK ] Starting dhcpd: SIOCADDRT: File exists [ OK ] Below is a SNIP from my log on a server that updates properly: Aug 29 13:36:59 normal dhcpd: DHCPDISCOVER from 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPOFFER on 192.168.1.65 to 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPREQUEST for 192.168.1.65 from 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPACK on 192.168.1.65 to 00:00:b4:be:ee:c6 via eth0 This is from the server that isn't providing proper DHCP IP addresses: Aug 29 19:32:34 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:35 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:40 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:40 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:46 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:46 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:52 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:52 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Notice how they never get the DHCPREQUEST and DHCPACK for the addresses? Trev. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Hi Graeme, So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. The reason I'm bringing this up here, is to just see if this is isolated or if there may be a real issue to look at. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. Trev. -Original Message- From: Graeme Robinson [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 3:33 AM To: John Powell; Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Re: procmail update worked
Hugh Fox [EMAIL PROTECTED] said: I'm not sure if this helps anyone, or if it could be used here... but I remember a program that autogenerates .procmail rules. Here is the url: http://www.flug.dk/lg/issue23/procmail.html Maybe this could be used as the basis for a web-based UI ??? I believe this prgoram requires X11 so not a fit for e-smith. -- Darrell May DMC NETSOURCED.COM http://netsourced.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 2:01 AM To: Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? Trevor, Is there something different about the 2 new machines (not a common OS, etc.)? I can tell you this, the broken clients are not seeing the responses from the server. the DHCPOFFER is the server responding, the client is supposed to accept the offer (and generate a DHCPREQUEST) or reject the offer (DHCPNAK), but obviously is not. The issue is likely to be with how the DHCPOFFER is addressed. Some servers broadcast the DHCPOFFER, some unicast it to the mac address of the requester. I believe the ISC server is a bit unique and broadcasts it (may be the other way around, I would need to sniff a connection to figure that out). I would need to read the RFC for the specifics, but I believe a client is supposed to accept either method, and it is likely your problem is your clients on the 2 broken machines are not accepting the method ISC -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Trevor Ouellette [EMAIL PROTECTED] said: Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. Hi Trevor, I have one question to ask. Did these two workstations ever have a manually set IP address in operation? If they did then my guess is there are some lingering registry entries that are screwing things up for you. If DHCP is working for all other workstations and simply not for these two, I'd suggest the problem _appears_ workstation related. To isolate and determine where the fault is try these two suggestions: Temporarily replace the hard drive and load a fresh copy of WinME/98. Test DHCP and if it works, then it most likely is a WinME/98 registry error. Knowing this your choices would be to dive into the registry and clean things up or simply backup data, reformat and reinstall. To confirm the server is at fault a good test would be to connect the two workstation up to any DHCP capable device (another server, cheap firewall like a DLINK-701) and see if they pick up DHCP from this new server/device. If they do, maybe the server is at fault. If they don't it still points to a workstation fault. Hope this helps. -- Darrell May DMC NETSOURCED.COM http://netsourced.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Thanks Darrell, Regarding your question, 1. The Windows 98 machine had a DHCP address and was working perfectly for a month. The next day, it's not resolving DHCP. It can communicate fine on the network with one other machine, so it's not physical. 2. The Windows ME machine just had it's hard drive replaced due to a crash... guess what, no DHCP IP address. That's why I'm starting to wonder... I will give your suggestions a try today, Darrell. Trev. -Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 9:22 AM To: Trevor Ouellette; E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? Trevor Ouellette [EMAIL PROTECTED] said: Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. Hi Trevor, I have one question to ask. Did these two workstations ever have a manually set IP address in operation? If they did then my guess is there are some lingering registry entries that are screwing things up for you. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. I doubt it, but would rule nothing out. Going by your logs, the client is the one dropping the ball. To make it clearer, the normal init sequence looks like this: C: DHCPDISCOVER (client asking for IP) S: DHCPOFFER (server dishing out an IP) C: DHCPREQUEST (client accepting the offerred IP) S: DHCPACK (server finalizing the process) From your logs, the process gets through to the OFFER, which means it recognizes the client and is offering an IP. The client is not accepting it for some reason, not even NAKing it, which suggests either the client doesn't see the response, or is choking on it for some reason. It does not sound like a server problem. Even if the server is offering up junk, the client should NAK it. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. That is, indeed, strange. Is it possible to get a sniffer like trace of this in action? Ethereal is a fine choice, or any other product with a decent decoded output. You might also want to check out www.isc.com (makers of the DHCP server in e-smith) or a google search and see if they have some hints on known problems with Wintel clients. I don't know of any (ISC's server is generally solid as a rock). JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] Macintosh network printers
I'm using an old Mac as a print server to make an Apple LaserWriter available on my network, and this is visible to a PC running Windows 2000 but not to a Windows 98 system. In the case of the Win 2K machine I access the printer by creating an AppleTalk device port. Is there a way to do this for Windows 98 machines? Secondly, how do I create a print spool for this device under Netatalk running on my e-smith server? I assume I have to modify papd.conf but I'm not clear on the syntax. Also, do I have to install a PPD file and if so, where? I'm assuming I can't do all this somehow through the Printers dialog in the e-smith Administration web pages, because printers there have to be accessible through the Microsoft Windows Network. No? Regards to all, Mark Ottawa, Canada. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.268 / Virus Database: 140 - Release Date: 8/7/2001 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] Has anybody a working IPSEC VPN Connection ?
I read many comments about problems to set up a IPSEC connection between two e-smith server. Has anybody made a working connection ? Michael Jung -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Macintosh network printers
I use Macs and Apple lasers. If you are lucky (you did not mention the printer model) on the back of the printer there is a LPT port, use this to connect to the e-smith. Create a new printer on the e-smith front end and you are done. Your networked Macs and PCs alike will be able to share this printer. Some Apple lasers had ethernet built in. you would need to give the printer a TCP/IP number in the range you are using. Brian Daybreak Info Systems Mark Farey wrote: I'm using an old Mac as a print server to make an Apple LaserWriter available on my network, and this is visible to a PC running Windows 2000 but not to a Windows 98 system. In the case of the Win 2K machine I access the printer by creating an AppleTalk device port. Is there a way to do this for Windows 98 machines? Secondly, how do I create a print spool for this device under Netatalk running on my e-smith server? I assume I have to modify papd.conf but I'm not clear on the syntax. Also, do I have to install a PPD file and if so, where? I'm assuming I can't do all this somehow through the Printers dialog in the e-smith Administration web pages, because printers there have to be accessible through the Microsoft Windows Network. No? Regards to all, Mark Ottawa, Canada. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.268 / Virus Database: 140 - Release Date: 8/7/2001 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] Macintosh network printers
-Original Message- From: b [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 1:38 PM To: [EMAIL PROTECTED] Cc: 'e-smith-devinfo' Subject: Re: [e-smith-devinfo] Macintosh network printers I use Macs and Apple lasers. If you are lucky (you did not mention the printer model) on the back of the printer there is a LPT port, use this to connect to the e-smith. Create a new printer on the e-smith front end and you are done. Your networked Macs and PCs alike will be able to share this printer. Some Apple lasers had ethernet built in. you would need to give the printer a TCP/IP number in the range you are using. Brian Daybreak Info Systems It's a Personal LaserWriter 320 and, no, it doesn't have an LPT port (I wish!), just a serial AppleTalk port. I've installed AppleTalk Bridge (unsupported utility from Apple) and this seems to work fine - it appears on the Ethernet network and can be accessed by my Win 2K machine. The problem is how to access it from a Win 98 machine. Regards, Mark. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.268 / Virus Database: 140 - Release Date: 8/7/2001 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] 5.0 release date?
So much for Release Early, Release Often or however the saying goes!!! Quoting Dan Brown [EMAIL PROTECTED]: Luuk Jansen wrote: With the 4.1 version there was a period of time for users to downloaded the release candidates and test it in their personal configuration. The beta test for 5.0 was restricted, and it doesn't look like they'll have an open beta period. -- Dan Brown, KE6MKS, [EMAIL PROTECTED] Meddle not in the affairs of dragons, for you are crunchy and taste good with ketchup. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
http://www.isc.org/ml-archives/dhcp-server/1999/07/msg00412.html http://www.isc.org/ml-archives/dhcp-server/1999/07/msg00422.html This is from the isc.org list and they are having a similar problem Yes, but that is on a 2 year old beta rev of 2.0 code and that particular problem seemed to have been solved in later beta code (all back in mid-1999). I guess it is easy enough to try out their suggestion of removing the subnet declaration (in /etc/dhcpd.conf), restart dhcpd, have the 2 machines retry dhcp (and fail), then rebuild the conf file using e-smith's expand-template command and restart dhcpd again. I don't think that will buy you much, but it can't hurt to try (stranger things have happened). I really do think you are going to want to get a sniff of this. Taking a close look at the DHCPDISCOVER and DHCPOFFER packets will likely provide some vital clues. If you hurry (I am out of the country for a week starting this Saturday) I would be glad to take a peek at them if you wish. BTW, though I do not think it is the issue, are you sure you are not out of addresses? Though I don't think the server would even respond if it is out of leases, I am not 100% sure of that. I hacked up a perl script I found (just changed the paths to match e-smith's) and it is available at http://www.jrp2.net/clease.pl , the code is documented and has lots of options, but if you run it with -d -s it shows useful info. Warning, it also shows expired leases and does not differentiate them. The lease file itself is pretty self-explanatory (/var/lib/dhcp/dhcpd.leases), but this script makes it a bit easier if you have a lot of entries. JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
