Mailinglist Archive: opensuse (5100 mails)
| < Previous | Next > |
Re: [SLE] HowTo connect dhcpd and dhcp-client
- From: Leendert Meyer <leen.meyer@xxxxxxx>
- Date: Mon, 7 Jun 2004 09:59:26 +0200
- Message-id: <200406070959.26595.leen.meyer@xxxxxxx>
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
> On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
> > On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
> > > I managed to get a connection between dhcp-server and dhcp-client. But
> > > I do not manage to get an internet connection for the client. eth1 is
> > > the dhcp-server where as eth0 gets the internet connection from the ISP
> > > as dhcp-client.
> > >
> > > Here is my dchp-dump output from the server for eth1.
> > >
> > > The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
> >
> > No, ;) the dhcp server sends a reply with those data. The question is if
> > that package is received by the client. dhcp-dump on the client would
> > reveil that.
>
> The dhcp-dump for the client never showed anything.
Sorry, my question was stupid. dhcp-dump does not run when the network is
down. ;)
> > BTW, can you setup a static ip# on the client?
> When I log in from the client on the server via ssh it works with a
> static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host?
> Do I have to configure the firewalls on both machines differently for dhcp?
Perhaps turn the firewalls of during testing. If all works well, you can turn
them on. If consequently something breaks, you know it's the firewall. ;) You
probably need the firewall later to reach the WWW, because of its
masquerading/NATting.
> On the server it does IP forwarding and masquerading and allows ssh and
As your dhcp server also serves as a router, you have to turn on IP forwarding
in /etc/sysconfig/sysctl:
IP_FORWARD="yes"
cat /proc/sys/net/ipv4/ip_forward should output a single '1'. If not, set it
manually with:
echo '1' > /proc/sys/net/ipv4/ip_forward
If you have put the firewall down on the host, then check this.
> On the client I use the setings I always use to get internet
> connections. It's a laptop and has been connected to various networks
> with this configuration. So I guess I still make a mistake on the
> server, right?
AFAICS: Right.
Well, that is, unless you hand out your ip# conditionally, in which case the
client has to fullfill a certain condition (e.g. send a client-id). But you
hand them out unconditionally, so no worries about that.
BTW, no need to CC me, I'm on the list. ;)
Cheers,
Leen
> On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
> > On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
> > > I managed to get a connection between dhcp-server and dhcp-client. But
> > > I do not manage to get an internet connection for the client. eth1 is
> > > the dhcp-server where as eth0 gets the internet connection from the ISP
> > > as dhcp-client.
> > >
> > > Here is my dchp-dump output from the server for eth1.
> > >
> > > The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
> >
> > No, ;) the dhcp server sends a reply with those data. The question is if
> > that package is received by the client. dhcp-dump on the client would
> > reveil that.
>
> The dhcp-dump for the client never showed anything.
Sorry, my question was stupid. dhcp-dump does not run when the network is
down. ;)
> > BTW, can you setup a static ip# on the client?
> When I log in from the client on the server via ssh it works with a
> static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host?
> Do I have to configure the firewalls on both machines differently for dhcp?
Perhaps turn the firewalls of during testing. If all works well, you can turn
them on. If consequently something breaks, you know it's the firewall. ;) You
probably need the firewall later to reach the WWW, because of its
masquerading/NATting.
> On the server it does IP forwarding and masquerading and allows ssh and
As your dhcp server also serves as a router, you have to turn on IP forwarding
in /etc/sysconfig/sysctl:
IP_FORWARD="yes"
cat /proc/sys/net/ipv4/ip_forward should output a single '1'. If not, set it
manually with:
echo '1' > /proc/sys/net/ipv4/ip_forward
If you have put the firewall down on the host, then check this.
> On the client I use the setings I always use to get internet
> connections. It's a laptop and has been connected to various networks
> with this configuration. So I guess I still make a mistake on the
> server, right?
AFAICS: Right.
Well, that is, unless you hand out your ip# conditionally, in which case the
client has to fullfill a certain condition (e.g. send a client-id). But you
hand them out unconditionally, so no worries about that.
BTW, no need to CC me, I'm on the list. ;)
Cheers,
Leen
| < Previous | Next > |