dhcp drakwizard suggestions (was Re: [Cooker] Re: problem for resolving domain names after connecting a LAN)
Comment is at the bottom --- David Walser <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Quoting David Walser <[EMAIL PROTECTED]>: > > > > > >>[EMAIL PROTECTED] wrote: > >> > >>>Quoting David Walser <[EMAIL PROTECTED]>: > >>> > >>> > >>> > I would just make sure you: > 1) Don't have any IP set as a GATEWAY > 2) are only running the dhcp server on the > ethernet interface > >>> > >>> > >>>Thanks David. > >>>For 1), I do not think so. > >>>For 2) how can I check it ? > >>> > >>>I had a look to /etc/dhcpd.conf > >> > >>Yeah, it's not set there. I'm gonna guess your > ethernet interface is > >>eth0, so in the file /etc/sysconfig/dhcpd you > should have a line: > >>INTERFACES="eth0" > >> > > > > > > I'll try that, thanks. > > Probably this will be a feature request for the > next version of drakwizard ;) > > Cheers > > Eric > > Yes, of course! Why the heck didn't I think of > that!? > > Warly, if the above mentioned thing isn't > configurable with drakwizard, > it should be. Sorry I didn't think of it earlier > (luckily this guy did). Just to reiterate the suggestion, the dhcp server wizard should let you pick what network interface the server should listen on, and write /etc/sysconfig/dhcpd Also, a couple things I just noticed. It defaults to wanting to supply addresses in the 192.168.0.100 and up range, but if your IP isn't in that range it complains about that. Why can't it just detect that first and give a sane default? Also, it shouldn't write the /etc/dhcpd.conf file if you hit Cancel before finishing the wizard. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
Re: [Cooker] Re: problem for resolving domain names after connecting a LAN
- Original Message - From: "David Walser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 11:31 PM Subject: [Cooker] Re: problem for resolving domain names after connecting a LAN > Eric Fernandez wrote: > > David : just a question about my problem. I try to understand what is > > incompatible between PPP and DHCP. I read that doing a little RTFM : > > "Important: You SHOULD NOT use the DHCP server within IPNetRouter to > > configure your client machines when using this single ethernet setup. If you > > do so, your IPNetRouter gateway becomes a DHCP server for the entire > > cable/DSL modem network and your Internet connection may be terminated by > > your service provider." > > That much is true. Whether that's causing the problem you're > complaining about or not, I want to fix that so you don't get in trouble :o) > > > Is it the problem I have ? Actually, it does not terminate my connection, > > but simply seems to prevents me to reach the DNS server of my ISP. But is > > the issue the fact that my dhcp server is trying to assign an IP number > > through the ISP network ? > > I don't know. That's what I'm trying to find out. > > Hi David I tried to reproduce the bug yesterday, and no ! It worked fine ! Without any change in /etc/dhcpd.conf file. Apparently my ISP had trouble this week end, and they said their DNS server had up and down periods. It is strange coincidence however I had the problem each time I plugged the other computer. Actually I used the "route" command to check what default route was used, and the ISP server name was correctly used on ppp0, whereas eth0 route was correctly using the attributed adress to the network machine. Anyway, it is probably good to add an option for it, but consider that it may work correctly now. I'll try it again and check with "route" in case of new problems. After RTFM, I feel more confident with networking now :) Cheers Eric
Re: [Cooker] Re: problem for resolving domain names after connecting a LAN
David : just a question about my problem. I try to understand what is incompatible between PPP and DHCP. I read that doing a little RTFM : "Important: You SHOULD NOT use the DHCP server within IPNetRouter to configure your client machines when using this single ethernet setup. If you do so, your IPNetRouter gateway becomes a DHCP server for the entire cable/DSL modem network and your Internet connection may be terminated by your service provider." Is it the problem I have ? Actually, it does not terminate my connection, but simply seems to prevents me to reach the DNS server of my ISP. But is the issue the fact that my dhcp server is trying to assign an IP number through the ISP network ? Thanks Eric
Re: [Cooker] Re: problem for resolving domain names after connecting a LAN
- Original Message - From: "David Walser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 10:14 AM Subject: [Cooker] Re: problem for resolving domain names after connecting a LAN > > I hope you had interfaces in all caps. eee... I'll try it again > > > BTW, should I open a bug report for it ? > > For what specifically? It works for me. Just for the feature request actually, so that it would be in the records :) Thanks Eric
Re: [Cooker] Re: problem for resolving domain names after connecting a LAN
Quoting David Walser <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: > > Quoting David Walser <[EMAIL PROTECTED]>: > > > > > >>I would just make sure you: > >>1) Don't have any IP set as a GATEWAY > >>2) are only running the dhcp server on the ethernet interface > > > > > > Thanks David. > > For 1), I do not think so. > > For 2) how can I check it ? > > > > I had a look to /etc/dhcpd.conf > > Yeah, it's not set there. I'm gonna guess your ethernet interface is > eth0, so in the file /etc/sysconfig/dhcpd you should have a line: > INTERFACES="eth0" > I'll try that, thanks. Probably this will be a feature request for the next version of drakwizard ;) Cheers Eric > > >
Re: [Cooker] Re: problem for resolving domain names after connecting a LAN
Quoting David Walser <[EMAIL PROTECTED]>:
> I would just make sure you:
> 1) Don't have any IP set as a GATEWAY
> 2) are only running the dhcp server on the ethernet interface
Thanks David.
For 1), I do not think so.
For 2) how can I check it ?
I had a look to /etc/dhcpd.conf
here it is :
[EMAIL PROTECTED] zeb]$ cat /etc/dhcpd.conf
# default file for dhcpd
# replace 192.168.1.101 by the IP adress of the server (same server for
# all services in this config file)
default-lease-time 36000;
max-lease-time 144000;
ddns-update-style ad-hoc;
not authoritative;
subnet 192.168.1.0 netmask 255.255.255.0{
range 192.168.1.102 192.168.1.254;
option domain-name "zebdomain";
option domain-name-servers 192.168.1.101;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
ddns-updates on;
ddns-domainname "zebdomain";
ddns-rev-domainname "in-addr.arpa";
}
Starngely, this does occur only when I plug B. If no other machine is plugged to
A it works, even if dhcpd is loaded.
Cheers
Eric
