Dear folks, Recently at work, the network administrators changed from static ip's to dhcp. They made changes to use static dhcp using the mac address of the machines connected to the network. Before I could connect to the network using something like
[root@rio ~]# ifconfig eth0 10.154.20.157 netmask 255.255.248.0 [root@rio ~]# route add default gateway 10.154.16.1 [root@rio ~]# echo nameserver 10.128.0.4 >> /etc/resolv.conf
Here's the info of that machine's connection after system administrator connected the machine using mac address.
[root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2511 errors:0 dropped:0 overruns:0 frame:0 TX packets:1766 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1405141 (1.3 MiB) TX bytes:307686 (300.4 KiB) Interrupt:11 Base address:0xae00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:51 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3718 (3.6 KiB) TX bytes:3718 (3.6 KiB)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@rio ~]#
Now I cannot get network access. Even with dhcp enabled. The network identifies the mac address of the machine and assigns the same ip throughout.
I want to add an extra NIC/LAN card to this machine call it eth1 and use the machine as a host for a small network so that I can use/share the internet access with other machines. I ask for advice/help on this issue. I have read the following
http://www.tldp.org/HOWTO/DHCP/index.html
and
http://www.linux-mag.com/2000-04/networknirvana_01.html
but I am not sure how to begin. I have not placed the nic card yet on the machine but I will do so tomorrow. The machine has Fedora Core 3 with an everything install. What do I need to setup a mini dhcp server from this machine?
Thanks in advance,
Antonio
__________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail
On Sun, 2005-08-28 at 17:51 -0700, Antonio Olivares wrote:
Dear folks, Recently at work, the network administrators changed from static ip's to dhcp. They made changes to use static dhcp using the mac address of the machines connected to the network. Before I could connect to the network using something like
[root@rio ~]# ifconfig eth0 10.154.20.157 netmask 255.255.248.0 [root@rio ~]# route add default gateway 10.154.16.1 [root@rio ~]# echo nameserver 10.128.0.4 >> /etc/resolv.conf
Here's the info of that machine's connection after system administrator connected the machine using mac address.
[root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2511 errors:0 dropped:0 overruns:0 frame:0 TX packets:1766 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1405141 (1.3 MiB) TX bytes:307686 (300.4 KiB) Interrupt:11 Base address:0xae00
[root@rio ~]#
Now I cannot get network access. Even with dhcp enabled. The network identifies the mac address of the machine and assigns the same ip throughout.
Are you getting a gateway route added? Are you getting a DNS server provided?
The gateway would need to be in the same (new) class C address space and the static gateway entry would need to be removed.
I want to add an extra NIC/LAN card to this machine call it eth1 and use the machine as a host for a small network so that I can use/share the internet access with other machines. I ask for advice/help on this issue. I have read the following
http://www.tldp.org/HOWTO/DHCP/index.html
and
What are the contents of /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network ? That is where you enable the necessary settings for hostname, gateway, etc when doing static IPs, and the settings are different to use dhcp.
but I am not sure how to begin. I have not placed the nic card yet on the machine but I will do so tomorrow. The machine has Fedora Core 3 with an everything install. What do I need to setup a mini dhcp server from this machine?
Right now you are trying to set up a dhcp client so this machine has access to the internet via eth0. A dhcp server is also simple, but is not a factor in the problem you are describing.
When you set up the dhcp server you will need to restrict it to answering only on the appropriate interface and set the appropriate address range. You will also have a routing issue to handle.
Adding a second nic may have some surprises. It may get the name eth0 and the existing one may become eth1, depending on the order devices are probed.
Thanks in advance,
Antonio
--- Jeff Vian jvian10@charter.net wrote:
On Sun, 2005-08-28 at 17:51 -0700, Antonio Olivares wrote:
Dear folks, Recently at work, the network administrators changed from static ip's to dhcp. They made
changes
to use static dhcp using the mac address of the machines connected to the network. Before I could connect to the network using something like
[root@rio ~]# ifconfig eth0 10.154.20.157 netmask 255.255.248.0 [root@rio ~]# route add default gateway
10.154.16.1
[root@rio ~]# echo nameserver 10.128.0.4 >> /etc/resolv.conf
Here's the info of that machine's connection after system administrator connected the machine using
mac
address.
[root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136
Bcast:10.154.19.255
Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2511 errors:0 dropped:0 overruns:0 frame:0 TX packets:1766 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1405141 (1.3 MiB) TX
bytes:307686
(300.4 KiB) Interrupt:11 Base address:0xae00
[root@rio ~]#
Now I cannot get network access. Even with dhcp enabled. The network identifies the mac address
of
the machine and assigns the same ip throughout.
Are you getting a gateway route added? Are you getting a DNS server provided?
The gateway would need to be in the same (new) class C address space and the static gateway entry would need to be removed.
I want to add an extra NIC/LAN card to this
machine
call it eth1 and use the machine as a host for a
small
network so that I can use/share the internet
access
with other machines. I ask for advice/help on
this
issue. I have read the following
http://www.tldp.org/HOWTO/DHCP/index.html
and
http://www.linux-mag.com/2000-04/networknirvana_01.html
What are the contents of /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network ?
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp BROADCAST=10.154.23.255 IPADDR=10.154.17.34 NETMASK=255.255.248.0 NETWORK=10.154.16.0 ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes GATEWAY=10.154.16.1 IPV6INIT=no [olivares@rio ~]$ cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=rio [olivares@rio ~]$
That is where you enable the necessary settings for hostname, gateway, etc when doing static IPs, and the settings are different to use dhcp.
but I am not sure how to begin. I have not placed
the
nic card yet on the machine but I will do so
tomorrow.
The machine has Fedora Core 3 with an everything install. What do I need to setup a mini dhcp
server
from this machine?
Right now you are trying to set up a dhcp client so this machine has access to the internet via eth0. A dhcp server is also simple, but is not a factor in the problem you are describing.
When you set up the dhcp server you will need to restrict it to answering only on the appropriate interface and set the appropriate address range. You will also have a routing issue to handle.
Adding a second nic may have some surprises. It may get the name eth0 and the existing one may become eth1, depending on the order devices are probed.
I have added the second nic. The system detects it as eth1. Thanks Jeff for replying. Now, I will try some of the reading that I previously did and if I get stuck will ask for more advice/help.
Kind Regards,
Antonio
Thanks in advance,
Antonio
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Am Mo, den 29.08.2005 schrieb Antonio Olivares um 15:08:
You are using DHCP, so remove what I mark
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp BROADCAST=10.154.23.255 delete IPADDR=10.154.17.34 delete NETMASK=255.255.248.0 delete NETWORK=10.154.16.0 delete ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes GATEWAY=10.154.16.1 delete (even with static IP configuration the GATEWAY
setting mostly ever has to be in /etc/sysconfig/network)
IPV6INIT=no [olivares@rio ~]$ cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=rio
These data are assigned by the DHCP server. Please see my other reply: not only your IP changed but too the subnet got smaller. Maybe the gateway changed too, but that should be done automatically by receiving the IP data from the DHCP server.
Alexander
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Mo, den 29.08.2005 schrieb Antonio Olivares um 15:08:
You are using DHCP, so remove what I mark
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp BROADCAST=10.154.23.255 delete IPADDR=10.154.17.34 delete NETMASK=255.255.248.0 delete NETWORK=10.154.16.0 delete ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes GATEWAY=10.154.16.1 delete (even with static IP
configuration the GATEWAY
setting mostly ever has to be in /etc/sysconfig/network)
IPV6INIT=no [olivares@rio ~]$ cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=rio
These data are assigned by the DHCP server. Please see my other reply: not only your IP changed but too the subnet got smaller. Maybe the gateway changed too, but that should be done automatically by receiving the IP data from the DHCP server.
Alexander
-- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 20:05:16 up 7 days, 16:48, load average: 0.05, 0.08, 0.10
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
First of all, I would like to say thanks to Jeff and Alexander for helping me out with this issue. I have made the changes suggested but I get a big error message. I am confused a bit, but the problem is a smaller one than before.
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes IPV6INIT=no [olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1 # 3Com Corporation 3c905 100BaseTX [Boomerang] DEVICE=eth1 ONBOOT=yes BOOTPROTO=dhcp HWADDR=00:60:97:C5:2A:C3 NETMASK=255.255.255.0 USERCTL=yes PEERDNS=no GATEWAY=eth0 TYPE=Ethernet IPADDR=192.168.100.1 [olivares@rio ~]$
[root@rio ~]# service dhcpd start dhcpd: unrecognized service [root@rio ~]# kedit & [1] 4457 [root@rio ~]# Link points to "/tmp/ksocket-root" Link points to "/tmp/kde-root" kbuildsycoca running... Reusing existing ksycoca
[root@rio ~]# netstat -r -n Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0 [root@rio ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0 [root@rio ~]# rpm -qa | grep dhcp dhcpv6_client-0.10-8 [root@rio ~]# route add -host 255.255.255.255 dev eth1 [root@rio ~]# cat /etc/dhcpd.conf # # Global Settings #
# Turn on Dynamic DNS: ddns-domainname "domain.lan"; ddns-update-style interim; ddns-updates on;
# Don't allow clients to update DNS, make the server do it # based on the hostname passed by the DHCP client: deny client-updates; allow unknown-clients;
# # 10.0.0.0/255.255.255.0 Scope Settings # subnet 10.0.0.0 netmask 255.255.255.0 {
# Range of DHCP assigned addresses for this scope range 10.0.0.100 10.0.0.200; # 1 day default-lease-time 86400; # 2 days max-lease-time 172800;
# Configure the client's default Gateway: option subnet-mask 255.255.255.0; option broadcast-address 10.0.0.255; option routers 10.0.0.2;
# Configure the client's DNS settings: option domain-name "domain.lan"; option domain-name-servers 10.0.0.1;
}[root@rio ~]# touch /var/state/dhcpd/dhcpd.leases touch: cannot touch `/var/state/dhcpd/dhcpd.leases': No such file or directory [root@rio ~]# cd /var/ [root@rio var]# ls account crash empty lib lock mail opt run tmp cache db gdm local log nis preserve spool yp [root@rio var]# mkdir state [root@rio var]# cd state/ [root@rio state]# ls [root@rio state]# mkdir dhcp [root@rio state]# cd dhcp/ [root@rio dhcp]# ls [root@rio dhcp]# cd .. [root@rio state]# ls dhcp [root@rio state]# cd .. [root@rio var]# cd .. [root@rio /]# ls bin dev home lib media mnt proc sbin srv tmp var boot etc initrd lost+found misc opt root selinux sys usr [root@rio /]# touch /var/state/dhcpd/dhcpd.leases touch: cannot touch `/var/state/dhcpd/dhcpd.leases': No such file or directory [root@rio /]# touch /var/state/dhcp/dhcpd.leases [root@rio /]# cd /usr/sbin/ [root@rio sbin]# dhcpd -d -f -bash: dhcpd: command not found [root@rio sbin]# dhcp -d -f -bash: dhcp: command not found [root@rio sbin]# cd /home/olivares/ [root@rio olivares]# ls c dhcp-3.0.1-44_FC3.i386.rpm Downloads netbeans-4.0 c.0502161545 Documents Firefox_wallpaper.png tmp Desktop Documents.tar.gz j2re1.4.2_06 vpd.properties [root@rio olivares]# rpm -ivh dhcp-3.0.1-44_FC3.i386.rpm warning: dhcp-3.0.1-44_FC3.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 Preparing... ########################################### [100%] 1:dhcp ########################################### [100%] [root@rio olivares]# dhcpd -d -f [root@rio olivares]# chkconfig dhcpd on
running system-config-services, I got the following message.
-------------------------------------------------------
dhcpd failed. The error was: Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help.
Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting. [FAILED]
Best Regards,
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Antonio Olivares kirjoitti viestissään (lähetysaika tiistai, 30. elokuuta 2005 01:26):
[root@rio ~]# service dhcpd start dhcpd: unrecognized service
dhcpd is the DHCP _server_. Do you want to use this machine as the DHCP server for your network?
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
The error message should be quite clear, if you really want to run a DHCP server, you must edit dhcpd.conf to suit your needs.
--- Markku Kolkka markkuk@tuubi.net wrote:
Antonio Olivares kirjoitti viestissään (lähetysaika tiistai, 30. elokuuta 2005 01:26):
[root@rio ~]# service dhcpd start dhcpd: unrecognized service
dhcpd is the DHCP _server_. Do you want to use this machine as the DHCP server for your network?
Yes, I do. I am getting closer and close to solving this. Here's what I have done.
I went to http://fedoranews.org/blog/?p=666 and tried to use this as a reference. Now things are looking brighter. I changed /etc/dhcpd.conf to mirror the one in the above website changing the domain names to other ones as specified.
[root@rio sbin]# service dhcpd start Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help.
Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting.
[FAILED] [root@rio sbin]# service dhcpd start Starting dhcpd: [ OK ] [1]+ Done kedit /etc/dhcpd.conf [root@rio sbin]#
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
The error message should be quite clear, if you really want to run a DHCP server, you must edit dhcpd.conf to suit your needs.
You are right. We are getting there as from above replies.
-- Markku Kolkka markku.kolkka@iki.fi
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Best Regards,
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
--- Antonio Olivares olivares14031@yahoo.com wrote:
--- Markku Kolkka markkuk@tuubi.net wrote:
Antonio Olivares kirjoitti viestissään
(lähetysaika
tiistai, 30. elokuuta 2005 01:26):
[root@rio ~]# service dhcpd start dhcpd: unrecognized service
dhcpd is the DHCP _server_. Do you want to use
this
machine as the DHCP server for your network?
Yes, I do. I am getting closer and close to solving this. Here's what I have done.
I went to http://fedoranews.org/blog/?p=666 and tried to use this as a reference. Now things are looking brighter. I changed /etc/dhcpd.conf to mirror the one in the above website changing the domain names to other ones as specified.
[root@rio sbin]# service dhcpd start Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help.
Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting.
[FAILED][root@rio sbin]# service dhcpd start Starting dhcpd:
[ OK ][1]+ Done kedit /etc/dhcpd.conf [root@rio sbin]#
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not
what
you want, please write a subnet declaration in your dhcpd.conf file for the network
segment
to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not
what
you want, please write a subnet declaration in your dhcpd.conf file for the network
segment
to which interface eth0 is attached. **
Not configured to listen on any interfaces!
The error message should be quite clear, if you really want to run a DHCP server, you must edit dhcpd.conf to
suit
your needs.
You are right. We are getting there as from above replies.
-- Markku Kolkka markku.kolkka@iki.fi
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Best Regards,
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
I modified dhcpd.conf to
[root@rio sbin]# cat /etc/dhcpd.conf ddns-update-style interim;
default-lease-time 600; max-lease-time 7200;
subnet 192.168.100.0 netmask 255.255.255.0 { option routers 192.168.100.1; option subnet-mask 255.255.255.0; option domain-name-servers 6355-1.example.com, 6355-2.example.com; range 192.168.100.2 192.168.100.20; } [root@rio sbin]#
apparently everything is working, but I cannot get into internet from Windows 98 SE machine using dhcp to access it. Should I change the subnetmask?
Should I rename domain-name-servers or just omit that line?
Kind Regards,
Antonio
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--- Antonio Olivares olivares14031@yahoo.com wrote:
--- Antonio Olivares olivares14031@yahoo.com wrote:
--- Markku Kolkka markkuk@tuubi.net wrote:
Antonio Olivares kirjoitti viestissään
(lähetysaika
tiistai, 30. elokuuta 2005 01:26):
[root@rio ~]# service dhcpd start dhcpd: unrecognized service
dhcpd is the DHCP _server_. Do you want to use
this
machine as the DHCP server for your network?
Yes, I do. I am getting closer and close to
solving
this. Here's what I have done.
I went to http://fedoranews.org/blog/?p=666 and tried to use this as a reference. Now things are looking brighter. I changed /etc/dhcpd.conf to mirror the one in the above website changing the domain names to other ones as specified.
[root@rio sbin]# service dhcpd start Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the
README
about submitting bug reports and requests for help.
Please do not under any circumstances send
requests
for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting.
[FAILED][root@rio sbin]# service dhcpd start Starting dhcpd:
[ OK ][1]+ Done kedit
/etc/dhcpd.conf
[root@rio sbin]#
No subnet declaration for eth1
(192.168.100.1).
** Ignoring requests on eth1. If this is not
what
you want, please write a subnet declaration in your dhcpd.conf file for the network
segment
to which interface eth1 is attached. **
No subnet declaration for eth0
(10.154.19.136).
** Ignoring requests on eth0. If this is not
what
you want, please write a subnet declaration in your dhcpd.conf file for the network
segment
to which interface eth0 is attached. **
Not configured to listen on any interfaces!
The error message should be quite clear, if you really want to run a DHCP server, you must edit dhcpd.conf to
suit
your needs.
You are right. We are getting there as from above replies.
-- Markku Kolkka markku.kolkka@iki.fi
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
Best Regards,
Antonio
Start your day with Yahoo! - make it your home
page
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
I modified dhcpd.conf to
[root@rio sbin]# cat /etc/dhcpd.conf ddns-update-style interim;
default-lease-time 600; max-lease-time 7200;
subnet 192.168.100.0 netmask 255.255.255.0 { option routers 192.168.100.1; option subnet-mask 255.255.255.0; option domain-name-servers 6355-1.example.com, 6355-2.example.com; range 192.168.100.2 192.168.100.20; } [root@rio sbin]#
I do not know how to approach this now. Apparently everything is working. [root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1087 errors:0 dropped:0 overruns:0 frame:0 TX packets:453 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:379721 (370.8 KiB) TX bytes:87477 (85.4 KiB) Interrupt:11 Base address:0xae00
eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::260:97ff:fec5:2ac3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:111 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15629 (15.2 KiB) TX bytes:3500 (3.4 KiB) Interrupt:11 Base address:0xec00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:51 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3718 (3.6 KiB) TX bytes:3718 (3.6 KiB)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@rio ~]# [root@rio ~]# chkconfig dhcpd --list dhcpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off [root@rio ~]# [root@rio ~]# service dhcpd status dhcpd (pid 3398) is running... [root@rio ~]#
Kind Regards,
Antonio
apparently everything is working, but I cannot get into internet from Windows 98 SE machine using dhcp to access it. Should I change the subnetmask?
Should I rename domain-name-servers or just omit that line?
Kind Regards,
Antonio
=== message truncated ===
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Am Di, den 30.08.2005 schrieb Antonio Olivares um 1:45:
apparently everything is working, but I cannot get into internet from Windows 98 SE machine using dhcp to access it. Should I change the subnetmask?
No.
Should I rename domain-name-servers or just omit that line?
domain-name-servers should be IP addresses. Which to use I can't judge, but maybe the 2 of your ISP may be best choice.
Antonio
Make sure you have forwarding set on on the gateway host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it does not, then activate it in /etc/sysctl.conf and run "sysctl -p". Make too sure the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing device]
Alexander
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Di, den 30.08.2005 schrieb Antonio Olivares um 1:45:
apparently everything is working, but I cannot get into internet from Windows 98 SE machine using
dhcp to
access it. Should I change the subnetmask?
No.
Should I rename domain-name-servers or just omit
that
line?
domain-name-servers should be IP addresses. Which to use I can't judge, but maybe the 2 of your ISP may be best choice.
Antonio
Make sure you have forwarding set on on the gateway host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it does not, then activate it in /etc/sysctl.conf and run "sysctl -p". Make too sure the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing device]
eth0 is the incoming connection should eth1 be the outgoing. I'm a little confused but getting there.
Alexander
-- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 10:14:51 up 8 days, 6:58, load average: 0.15, 0.26, 0.29
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward 1 [root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name [root@rio ~]# [root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name [root@rio ~]# [root@rio ~]# iptables -A POSTROUTING -o eth1 -j MASQUERADE iptables: No chain/target/match by that name [root@rio ~]# iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE [root@rio ~]# service dhcpd status dhcpd (pid 4917) is running... [root@rio ~]# service iptables save\
[root@rio ~]# service iptables save Saving firewall rules to /etc/sysconfig/iptables: [ OK ] [root@rio ~]# service network restart Shutting down interface eth0: [ OK ] Shutting down interface eth1: [ OK ] Shutting down loopback interface: [ OK ] Disabling IPv4 packet forwarding: [ OK ] Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface eth1: [ OK ] [root@rio ~]# touch /var/state/dhcpd/dhcpd.leases [root@rio ~]# service dhcpd status dhcpd (pid 4917) is running... [root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6848 errors:0 dropped:0 overruns:0 frame:0 TX packets:4031 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3177302 (3.0 MiB) TX bytes:901591 (880.4 KiB) Interrupt:11 Base address:0xae00
eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::260:97ff:fec5:2ac3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:515 errors:0 dropped:0 overruns:0 frame:0 TX packets:114 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:74818 (73.0 KiB) TX bytes:19234 (18.7 KiB) Interrupt:11 Base address:0xec00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:52 errors:0 dropped:0 overruns:0 frame:0 TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3794 (3.7 KiB) TX bytes:3794 (3.7 KiB)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@rio ~]#
I have made most changes that Jeff and Alexander have provided and I know that I am close as possible to getting this thing going. I tried to connect to the internet from within Windows 98 machine and I get a DNS error and cannot connect. However, the ipconfig /all, ipconfig /release_all and ipconfig /renew_all give the following
iprelease gives
Windows 98 IP Configuration
0 Ethernet adapter :
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
1 Ethernet adapter :
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
Windows 98 IP Configuration
Host Name . . . . . . . . . : 4280 LAB 21.domain.lan
DNS Servers . . . . . . . . :
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
0 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
1 Ethernet adapter :
Description . . . . . . . . : 3Com 3C90x Ethernet Adapter
Physical Address. . . . . . : 00-C0-4F-73-25-42
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.100.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . : 192.168.100.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 08 30 05 7:22:21 AM
Lease Expires . . . . . . . : 08 31 05 7:22:21 AM
Windows 98 IP Configuration
Host Name . . . . . . . . . : 4280 LAB 21.domain.lan
DNS Servers . . . . . . . . :
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
0 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
1 Ethernet adapter :
Description . . . . . . . . : 3Com 3C90x Ethernet Adapter
Physical Address. . . . . . : 00-C0-4F-73-25-42
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.100.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . : 192.168.100.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 08 30 05 7:22:21 AM
Lease Expires . . . . . . . : 08 31 05 7:22:21 AM
It is probably something with the settings. Apparently everything looks ok but connection not good. Thanks for all suggestions and help provided.
Kind Regards,
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Am Di, den 30.08.2005 schrieb Antonio Olivares um 15:02:
Make sure you have forwarding set on on the gateway host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it does not, then activate it in /etc/sysctl.conf and run "sysctl -p". Make too sure the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing device]
eth0 is the incoming connection should eth1 be the outgoing. I'm a little confused but getting there.
The device given with -o <device> has to be the public net device.
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward 1
Ok.
[root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name
Sorry, my fault. Above should have been for the NAT table (by default iptables takes the filter table):
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
I have made most changes that Jeff and Alexander have provided and I know that I am close as possible to getting this thing going. I tried to connect to the internet from within Windows 98 machine and I get a DNS error and cannot connect.
The NATed client has to know a valid DNS server and it's gateway is the NAT gateway host.
However, the ipconfig /all, ipconfig /release_all and ipconfig /renew_all give the following
Windows 98 IP Configuration
1 Ethernet adapter :
Description . . . . . . . . : 3Com 3C90x Ethernet Adapter
Physical Address. . . . . . : 00-C0-4F-73-25-42
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.100.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . : 192.168.100.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 08 30 05 7:22:21 AM
Lease Expires . . . . . . . : 08 31 05 7:22:21 AM
So eth1 on the Fedora machine is your inner (LAN) network device and eth0 for NAT.
It is probably something with the settings. Apparently everything looks ok but connection not good. Thanks for all suggestions and help provided.
Is the LAN client able to ping IP 10.154.19.136? Is it able to ping IP 64.233.183.99?
Antonio
Alexander
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Di, den 30.08.2005 schrieb Antonio Olivares um 15:02:
Make sure you have forwarding set on on the
gateway
host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it does
not,
then activate it in /etc/sysctl.conf and run "sysctl -p". Make too
sure
the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing
device]
eth0 is the incoming connection should eth1 be the outgoing. I'm a little confused but getting
there.
The device given with -o <device> has to be the public net device.
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward 1
Ok.
[root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name
Sorry, my fault. Above should have been for the NAT table (by default iptables takes the filter table):
# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE The device that comes in is eth0 and the one that is acting as the output is eth1 should the above command be changed to eth1?
I have made most changes that Jeff and Alexander
have
provided and I know that I am close as possible to getting this thing going. I tried to connect to the internet from within
Windows
98 machine and I get a DNS error and cannot
connect.
The NATed client has to know a valid DNS server and it's gateway is the NAT gateway host.
However, the ipconfig /all, ipconfig /release_all
and
ipconfig /renew_all give the following
Windows 98 IP Configuration
1 Ethernet adapter :
Description . . . . . . . . : 3Com 3C90x Ethernet Adapter
Physical Address. . . . . . : 00-C0-4F-73-25-42
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.100.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . : 192.168.100.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 08 30 05 7:22:21 AM
Lease Expires . . . . . . . : 08 31 05 7:22:21 AM
So eth1 on the Fedora machine is your inner (LAN) network device and eth0 for NAT.
It is probably something with the settings. Apparently everything looks ok but connection not good. Thanks for all suggestions and help
provided.
Is the LAN client able to ping IP 10.154.19.136? Is it able to ping IP 64.233.183.99?
Antonio
Alexander
-- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 15:34:40 up 8 days, 12:18, load average: 0.08, 0.07, 0.08
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
The configuration is not working in Windows98. I do not know how to mess with the settings. I should try tomorrow with a livecd like DSL/feather linux because the machine has only 32MB of ram.
[root@rio ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0 [root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fea6:1928/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3709 errors:0 dropped:0 overruns:0 frame:0 TX packets:1160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1076413 (1.0 MiB) TX bytes:179791 (175.5 KiB) Interrupt:11 Base address:0xae00
eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::260:97ff:fec5:2ac3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:171 errors:0 dropped:0 overruns:0 frame:0 TX packets:98 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17772 (17.3 KiB) TX bytes:11736 (11.4 KiB) Interrupt:11 Base address:0xec00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:95 errors:0 dropped:0 overruns:0 frame:0 TX packets:95 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6570 (6.4 KiB) TX bytes:6570 (6.4 KiB)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@rio ~]#
Thanks for all helpful advice and suggestions. I will report back as I continue with this problem.
Kind Regards,
Antonio
P.S. I have installed webmin but I get an error message
The connection to rio.10000 has terminated unexpectedly . Some data may be tranferred.
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
On Tuesday 30 August 2005 07:06 pm, Antonio Olivares wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
snip
Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Did you add rules for forwarding S.A iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
--- jludwig wralphie@comcast.net wrote:
On Tuesday 30 August 2005 07:06 pm, Antonio Olivares wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
iptables -A POSTROUTING -o eth0 -j
MASQUERADE snip
Start your day with Yahoo! - make it your home
page
Did you add rules for forwarding S.A iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
I did not do it that way because I just followed the previous directions to use # iptables -A POSTROUTING -o eth0 -j MASQUERADE
Apparently the server is working, but the windows 98 machine does not connect to internet from it. I will test tomorrow with a live cd like DSL/Feather Linux/Slax to check again. The eth0 device gets dhcp from the server according to its MAC address and the eth1 is the one that should be issuing the dhcp addresses at random and I wonder if the previous command should be # iptables -A POSTROUTING -o eth1 -j MASQUERADE
In the case that it does not work, I will send /etc/dhcpd.conf, and other information that is needed.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Kind Regards,
Antonio
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--- jludwig wralphie@comcast.net wrote:
On Tuesday 30 August 2005 07:06 pm, Antonio Olivares wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
iptables -A POSTROUTING -o eth0 -j
MASQUERADE snip
Start your day with Yahoo! - make it your home
page
Did you add rules for forwarding S.A iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
I have tried to connect from slax live cd and it does not connect. I have done the following:
[root@rio ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0 [root@rio ~]# service dhcpd status dhcpd (pid 3899) is running... [root@rio ~]# service network restart Shutting down interface eth0: [ OK ] Shutting down interface eth1: [ OK ] Shutting down loopback interface: [ OK ] Disabling IPv4 packet forwarding: [ OK ] Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface eth1: [ OK ] [root@rio ~]# iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE [root@rio ~]# service iptables save Saving firewall rules to /etc/sysconfig/iptables: [ OK ] [root@rio ~]# service network restart Shutting down interface eth0: [ OK ] Shutting down interface eth1: [ OK ] Shutting down loopback interface: [ OK ] Disabling IPv4 packet forwarding: [ OK ] Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface eth1: [ OK ] [root@rio ~]# service dhcpd status dhcpd (pid 3899) is running... [root@rio ~]# touch /var/state/dhcpd/dhcpd.leases [root@rio ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0 [root@rio ~]#
What should I do so that the problem gets fixed?
TIA
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
--- Antonio Olivares olivares14031@yahoo.com wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Di, den 30.08.2005 schrieb Antonio Olivares um 15:02:
Make sure you have forwarding set on on the
gateway
host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it
does
not,
then activate it in /etc/sysctl.conf and run "sysctl -p". Make too
sure
the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing
device]
eth0 is the incoming connection should eth1 be
the
outgoing. I'm a little confused but getting
there.
The device given with -o <device> has to be the public net device.
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward 1
Ok.
[root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name
Sorry, my fault. Above should have been for the
NAT
table (by default iptables takes the filter table):
=== message truncated ===
I'm trying continually to solve this issue and I have tried with a windows2000 machine and I get this
[olivares@rio ~]$ cat /media/floppy/win2000info.txt
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : teacher-0by6j7s Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : domain.lan Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) Physical Address. . . . . . . . . : 00-01-03-DD-7D-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DHCP Server . . . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 10.154.16.130 Lease Obtained. . . . . . . . . . : Wednesday, August 31, 2005 12:10:34PM Lease Expires . . . . . . . . . . : Thursday, September 01, 2005 12:10:34 PM [olivares@rio ~]$
what do I need to edit? how do I find out what is wrong?
Kind Regards and TIA,
Antonio
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
Am Mi, den 31.08.2005 schrieb Antonio Olivares um 21:20:
I'm trying continually to solve this issue and I have tried with a windows2000 machine and I get this
[olivares@rio ~]$ cat /media/floppy/win2000info.txt
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . :teacher-0by6j7s Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : domain.lan Description . . . . . . . . . . . : 3ComEtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) Physical Address. . . . . . . . . : 00-01-03-DD-7D-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DHCP Server . . . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 10.154.16.130 Lease Obtained. . . . . . . . . . : Wednesday, August 31, 2005 12:10:34PM Lease Expires . . . . . . . . . . : Thursday, September 01, 2005 12:10:34 PM [olivares@rio ~]$
what do I need to edit? how do I find out what is wrong?
Kind Regards and TIA,
Antonio
Did you answer whether you can reach / ping the IP 10.154.16.130 of your Fedora host, and the IP of google.com?
DNS Servers . . . . . . . . . . . :10.154.16.130
Do you have setup a DNS server on your Fedora host? So far I only remember to have see DHCP discussion.
Alexander
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Mi, den 31.08.2005 schrieb Antonio Olivares um 21:20:
I'm trying continually to solve this issue and I
have
tried with a windows2000 machine and I get this
[olivares@rio ~]$ cat
/media/floppy/win2000info.txt
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . :teacher-0by6j7s Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . :
Broadcast
IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :domain.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :domain.lan
Description . . . . . . . . . . . : 3ComEtherLink XL 10/100 PCI For Complete PC Management
NIC
(3C905C-TX) Physical Address. . . . . . . . . : 00-01-03-DD-7D-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DHCP Server . . . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 10.154.16.130 Lease Obtained. . . . . . . . . . :
Wednesday,
August 31, 2005 12:10:34PM Lease Expires . . . . . . . . . . :
Thursday,
September 01, 2005 12:10:34 PM [olivares@rio ~]$
what do I need to edit? how do I find out what is wrong?
Kind Regards and TIA,
Antonio
Did you answer whether you can reach / ping the IP 10.154.16.130 of your Fedora host, and the IP of google.com?
I cannot ping any website. Maybe I did not configure the server correctly. Does the /etc/dhcp.conf do that automatically or do I have to create another file?
DNS Servers . . . . . . . . . . . :10.154.16.130
Do you have setup a DNS server on your Fedora host? So far I only remember to have see DHCP discussion.
No, I did not setup a DNS server on the Fedora Host? I setup dhcpd to run and make a DHCP server that should take care of this? I thought that by setting up DHCP server would take care of DNS by itself, what do I have to do?
Thank all users who have replied and are giving a helpful hand.
Alexander
-- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 22:01:28 up 9 days, 18:45, load average: 0.09, 0.18, 0.17
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
Best Regards,
Antonio
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Am Mi, den 31.08.2005 schrieb Antonio Olivares um 23:37:
Did you answer whether you can reach / ping the IP 10.154.16.130 of your Fedora host, and the IP of google.com?
I cannot ping any website. Maybe I did not configure the server correctly. Does the /etc/dhcp.conf do that automatically or do I have to create another file?
So you even can not ping the IP of the outgoing device of your Fedora gateway? Or just external IPs? At least your internal network has to function.
DNS Servers . . . . . . . . . . . :10.154.16.130
Do you have setup a DNS server on your Fedora host? So far I only remember to have see DHCP discussion.
No, I did not setup a DNS server on the Fedora Host? I setup dhcpd to run and make a DHCP server that should take care of this? I thought that by setting up DHCP server would take care of DNS by itself, what do I have to do?
You posted a dhcpd.conf where you defined
option domain-name-servers 6355-1.example.com, 6355-2.example.com;
The setting of your Windows host does not reflect that (while name servers should be called by their IP, not names).
Antonio
Alexander
On Wed, 2005-08-31 at 12:20 -0700, Antonio Olivares wrote:
--- Antonio Olivares olivares14031@yahoo.com wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Di, den 30.08.2005 schrieb Antonio Olivares um 15:02:
Make sure you have forwarding set on on the
gateway
host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it
does
not,
then activate it in /etc/sysctl.conf and run "sysctl -p". Make too
sure
the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j MASQUERADE
[eth0 should be in your case the outgoing
device]
eth0 is the incoming connection should eth1 be
the
outgoing. I'm a little confused but getting
there.
The device given with -o <device> has to be the public net device.
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward 1
Ok.
[root@rio ~]# iptables -A POSTROUTING -o eth0 -j MASQUERADE iptables: No chain/target/match by that name
Sorry, my fault. Above should have been for the
NAT
table (by default iptables takes the filter table):
=== message truncated ===
I'm trying continually to solve this issue and I have tried with a windows2000 machine and I get this
Reading thru what you have below, this seems to most certainly be a routing/firewalling/masquerading issue on the linux box.
From the windows box try this and let us know the results.
1. ping 192.168.100.1 2. ping 10.154.19.136
3. If both those work, then try a ping to 10.154.19.130 (the address you have assigned as DNS server) if #1 works but #2 and/or #3 do not then this is an issue with the routing/firewalling/masquerading on the Linux server.
Per the contents you posted below this no longer seems an issue with dhcp since the data is properly being assigned.
[olivares@rio ~]$ cat /media/floppy/win2000info.txt
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . :teacher-0by6j7s Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : domain.lan Description . . . . . . . . . . . : 3ComEtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) Physical Address. . . . . . . . . : 00-01-03-DD-7D-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DHCP Server . . . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 10.154.16.130 Lease Obtained. . . . . . . . . . : Wednesday, August 31, 2005 12:10:34PM Lease Expires . . . . . . . . . . : Thursday, September 01, 2005 12:10:34 PM [olivares@rio ~]$
what do I need to edit? how do I find out what is wrong?
Kind Regards and TIA,
Antonio
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
--- Jeff Vian jvian10@charter.net wrote:
On Wed, 2005-08-31 at 12:20 -0700, Antonio Olivares wrote:
--- Antonio Olivares olivares14031@yahoo.com
wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Di, den 30.08.2005 schrieb Antonio Olivares
um
15:02:
Make sure you have forwarding set on on
the
gateway
host:
$ cat /proc/sys/net/ipv4/ip_forward
must print out "1" (without quotes). If it
does
not,
then activate it in /etc/sysctl.conf and run "sysctl -p". Make
too
sure
the gateway does NAT by an iptables rule like:
iptables -A POSTROUTING -o eth0 -j
MASQUERADE
[eth0 should be in your case the outgoing
device]
eth0 is the incoming connection should eth1
be
the
outgoing. I'm a little confused but getting
there.
The device given with -o <device> has to be
the
public net device.
[root@rio ~]# cat
/proc/sys/net/ipv4/ip_forward
1
Ok.
[root@rio ~]# iptables -A POSTROUTING -o
eth0 -j
MASQUERADE iptables: No chain/target/match by that name
Sorry, my fault. Above should have been for
the
NAT
table (by default iptables takes the filter table):
=== message truncated ===
I'm trying continually to solve this issue and I
have
tried with a windows2000 machine and I get this
Reading thru what you have below, this seems to most certainly be a routing/firewalling/masquerading issue on the linux box.
From the windows box try this and let us know the
results.
- ping 192.168.100.1
[olivares@rio floppy]$ cat ping1
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time<10ms TTL=64 Reply from 192.168.100.1: bytes=32 time<10ms TTL=64 Reply from 192.168.100.1: bytes=32 time<10ms TTL=64 Reply from 192.168.100.1: bytes=32 time<10ms TTL=64
Ping statistics for 192.168.100.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
- ping 10.154.19.136
[olivares@rio floppy]$ cat ping2
Pinging 10.154.19.136 with 32 bytes of data:
Reply from 10.154.19.136: bytes=32 time<10ms TTL=64 Reply from 10.154.19.136: bytes=32 time<10ms TTL=64 Reply from 10.154.19.136: bytes=32 time<10ms TTL=64 Reply from 10.154.19.136: bytes=32 time<10ms TTL=64
Ping statistics for 10.154.19.136: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
- If both those work, then try a ping to
10.154.19.130
[olivares@rio floppy]$ cat ping3
Pinging 10.154.19.130 with 32 bytes of data:
Request timed out. Request timed out. Reply from 10.154.19.136: Destination host unreachable. Request timed out.
Ping statistics for 10.154.19.130: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms [olivares@rio floppy]$
(the address you have assigned as DNS server) if #1 works but #2 and/or #3 do not then this is an issue with the routing/firewalling/masquerading on the Linux server.
Per the contents you posted below this no longer seems an issue with dhcp since the data is properly being assigned.
[olivares@rio ~]$ cat
/media/floppy/win2000info.txt
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . :teacher-0by6j7s Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . :
Broadcast
IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :domain.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :domain.lan
Description . . . . . . . . . . . : 3ComEtherLink XL 10/100 PCI For Complete PC Management
NIC
(3C905C-TX) Physical Address. . . . . . . . . : 00-01-03-DD-7D-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DHCP Server . . . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 10.154.16.130 Lease Obtained. . . . . . . . . . :
Wednesday,
August 31, 2005 12:10:34PM Lease Expires . . . . . . . . . . :
Thursday,
September 01, 2005 12:10:34 PM [olivares@rio ~]$
what do I need to edit? how do I find out what is wrong?
Kind Regards and TIA,
Antonio
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the
tour:
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Just in case I will submit /etc/dhcpd.conf to see if you can find errors in it because I have been modifying it many times.
[olivares@rio floppy]$ cat /etc/dhcpd.conf # # Global Settings #
# Turn on Dynamic DNS: ddns-domainname "rio"; ddns-update-style interim; ddns-updates on;
# Don't allow clients to update DNS, make the server do it # based on the hostname passed by the DHCP client: deny client-updates; allow unknown-clients;
# 1 day default-lease-time 86400;
# 2 days max-lease-time 172800;
# Configure the client's default Gateway: option subnet-mask 255.255.255.0; option broadcast-address 192.168.100.255; option routers 192.168.100.1; # Configure the client's DNS settings: option domain-name "rio"; option domain-name-servers 10.154.16.130, 10.128.0.4; option netbios-name-servers 192.168.100.1;
# Range of DHCP assigned addresses for this scope subnet 192.168.100.0 netmask 255.255.255.0 { range 192.168.100.1 192.168.100.100; range 192.168.100.150 192.168.100.200; }
Best Regards,
Antonio
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Antonio, Just a little advice. I have done the same same setup. I have used an old 500 Mhz machine using fedora 2. If you only want the machine for routing, I would recommend getting shorewall firewall, and webmin. Webmin makes managing your settings much easier than maually editing files, and shorewall does routing from an abstraction of iptables with easier configuration files.
On 8/29/05, Antonio Olivares olivares14031@yahoo.com wrote:
--- Markku Kolkka markkuk@tuubi.net wrote:
Antonio Olivares kirjoitti viestissään (lähetysaika tiistai, 30. elokuuta 2005 01:26):
[root@rio ~]# service dhcpd start dhcpd: unrecognized service
dhcpd is the DHCP _server_. Do you want to use this machine as the DHCP server for your network?
Yes, I do. I am getting closer and close to solving this. Here's what I have done.
I went to http://fedoranews.org/blog/?p=666 and tried to use this as a reference. Now things are looking brighter. I changed /etc/dhcpd.conf to mirror the one in the above website changing the domain names to other ones as specified.
[root@rio sbin]# service dhcpd start Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1 http://192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136 http://10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.org http://ftp.isc.org, please get the latest from ftp.isc.org http://ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org http://ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help.
Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting.
[FAILED] [root@rio sbin]# service dhcpd start Starting dhcpd: [ OK ] [1]+ Done kedit /etc/dhcpd.conf [root@rio sbin]#
No subnet declaration for eth1 (192.168.100.1 http://192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136 http://10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
The error message should be quite clear, if you really want to run a DHCP server, you must edit dhcpd.conf to suit your needs.
You are right. We are getting there as from above replies.
-- Markku Kolkka markku.kolkka@iki.fi
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Best Regards,
Antonio
Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
On Mon, 2005-08-29 at 15:26 -0700, Antonio Olivares wrote:
--- Alexander Dalloz ad+lists@uni-x.org wrote:
Am Mo, den 29.08.2005 schrieb Antonio Olivares um 15:08:
You are using DHCP, so remove what I mark
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp BROADCAST=10.154.23.255 delete IPADDR=10.154.17.34 delete NETMASK=255.255.248.0 delete NETWORK=10.154.16.0 delete ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes GATEWAY=10.154.16.1 delete (even with static IP
configuration the GATEWAY
setting mostly ever has to be in /etc/sysconfig/network)
IPV6INIT=no [olivares@rio ~]$ cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=rio
These data are assigned by the DHCP server. Please see my other reply: not only your IP changed but too the subnet got smaller. Maybe the gateway changed too, but that should be done automatically by receiving the IP data from the DHCP server.
Alexander
-- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 20:05:16 up 7 days, 16:48, load average: 0.05, 0.08, 0.10
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
First of all, I would like to say thanks to Jeff and Alexander for helping me out with this issue. I have made the changes suggested but I get a big error message. I am confused a bit, but the problem is a smaller one than before.
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet HWADDR=00:50:2c:a6:19:28 USERCTL=no PEERDNS=yes IPV6INIT=no
Good, that looks right for a dhcp client.
[olivares@rio ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1 # 3Com Corporation 3c905 100BaseTX [Boomerang] DEVICE=eth1 ONBOOT=yes BOOTPROTO=dhcp HWADDR=00:60:97:C5:2A:C3 NETMASK=255.255.255.0 USERCTL=yes PEERDNS=no GATEWAY=eth0 TYPE=Ethernet IPADDR=192.168.100.1
NO. You said this would be a dhcp server for the attached network. You should set a static IP on this interface.
BOOTPROTO=none NETWORK=192.168.100.0 BROADCAST=192.168.100.255
Do not set the gateway. That line should be removed (it is invalid anyway).
After this, the config for your dhcp server should be the main part that is needed. Make certain the dhcp server is handing out addresses in the 192.168.100 network, and that it ONLY answers to requests on eth1. Your dhcp config should pass the gateway address (this interface), dns server, IP, and netmask (and hostname if you want) to the machines on this subnet.
Last, but not least, you will need to set up NAT and ip forwarding so the machines on the eth1 interface will be able to reach the other side of this host and receive replies.
[olivares@rio ~]$
[root@rio ~]# service dhcpd start dhcpd: unrecognized service [root@rio ~]# kedit & [1] 4457 [root@rio ~]# Link points to "/tmp/ksocket-root" Link points to "/tmp/kde-root" kbuildsycoca running... Reusing existing ksycoca [root@rio ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.154.19.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.154.19.1 0.0.0.0 UG 0 0 0 eth0
Good, only one subnet on eth1, and the default route on eth0
[root@rio ~]# rpm -qa | grep dhcp dhcpv6_client-0.10-8 [root@rio ~]# route add -host 255.255.255.255 dev eth1 [root@rio ~]# cat /etc/dhcpd.conf # # Global Settings #
# Turn on Dynamic DNS: ddns-domainname "domain.lan"; ddns-update-style interim; ddns-updates on;
# Don't allow clients to update DNS, make the server do it # based on the hostname passed by the DHCP client: deny client-updates; allow unknown-clients;
# # 10.0.0.0/255.255.255.0 Scope Settings # subnet 10.0.0.0 netmask 255.255.255.0 {
# Range of DHCP assigned addresses for thisscope range 10.0.0.100 10.0.0.200; # 1 day default-lease-time 86400; # 2 days max-lease-time 172800;
# Configure the client's default Gateway: option subnet-mask 255.255.255.0; option broadcast-address 10.0.0.255; option routers 10.0.0.2; # Configure the client's DNS settings: option domain-name "domain.lan"; option domain-name-servers 10.0.0.1;
You are assigning the interface eth1 an address in the 192.168.100.X network with netmask of 255.255.255.0 You must serve out addresses with the same netmask and network.
Something like the following _________________________________________________________ subnet 192.168.100.0 netmask 255.255.255.0 { # Range of DHCP assigned addresses for this scope range 192.168.100.100 192.168.100.200; # 1 day default-lease-time 86400; # 2 days max-lease-time 172800;
# Configure the client's default Gateway: option subnet-mask 255.255.255.0; option broadcast-address 192.168.100.255; option routers 192.168.100.1;
# Configure the client's DNS settings: option domain-name "domain.lan"; option domain-name-servers XXX.XXX.XXX.XXX; _________________________________________________________
The domain-name-servers will be the same as your host uses for it's own DNS server, thus the client requests will be just passed on through. Or it will be this host and you can run a caching name server for your subnet. That probably is not needed.
}[root@rio ~]# touch /var/state/dhcpd/dhcpd.leases touch: cannot touch `/var/state/dhcpd/dhcpd.leases': No such file or directory [root@rio ~]# cd /var/ [root@rio var]# ls account crash empty lib lock mail opt run tmp cache db gdm local log nis preserve spool yp [root@rio var]# mkdir state [root@rio var]# cd state/ [root@rio state]# ls [root@rio state]# mkdir dhcp [root@rio state]# cd dhcp/ [root@rio dhcp]# ls [root@rio dhcp]# cd .. [root@rio state]# ls dhcp [root@rio state]# cd .. [root@rio var]# cd .. [root@rio /]# ls bin dev home lib media mnt proc sbin srv tmp var boot etc initrd lost+found misc opt root selinux sys usr [root@rio /]# touch /var/state/dhcpd/dhcpd.leases touch: cannot touch `/var/state/dhcpd/dhcpd.leases': No such file or directory [root@rio /]# touch /var/state/dhcp/dhcpd.leases [root@rio /]# cd /usr/sbin/ [root@rio sbin]# dhcpd -d -f -bash: dhcpd: command not found [root@rio sbin]# dhcp -d -f -bash: dhcp: command not found [root@rio sbin]# cd /home/olivares/ [root@rio olivares]# ls c dhcp-3.0.1-44_FC3.i386.rpm Downloads netbeans-4.0 c.0502161545 Documents Firefox_wallpaper.png tmp Desktop Documents.tar.gz j2re1.4.2_06 vpd.properties [root@rio olivares]# rpm -ivh dhcp-3.0.1-44_FC3.i386.rpm warning: dhcp-3.0.1-44_FC3.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 Preparing... ########################################### [100%] 1:dhcp ########################################### [100%] [root@rio olivares]# dhcpd -d -f [root@rio olivares]# chkconfig dhcpd on
running system-config-services, I got the following message.
dhcpd failed. The error was: Starting dhcpd: Internet Systems Consortium DHCP Server V3.0.1 Copyright 2004 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 leases to leases file.
No subnet declaration for eth1 (192.168.100.1). ** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. **
No subnet declaration for eth0 (10.154.19.136). ** Ignoring requests on eth0. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0 is attached. **
Not configured to listen on any interfaces!
You MUST not allow dhcp communications on eth0 since that network already has a dhcp server.
If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help.
If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help.
Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
exiting. [FAILED]
Best Regards,
Antonio
HTH Jeff
Am Mo, den 29.08.2005 schrieb Antonio Olivares um 2:51:
Recently at work, the network administrators changed from static ip's to dhcp. They made changes to use static dhcp using the mac address of the machines connected to the network. Before I could connect to the network using something like
[root@rio ~]# ifconfig eth0 10.154.20.157 netmask 255.255.248.0 [root@rio ~]# route add default gateway 10.154.16.1 [root@rio ~]# echo nameserver 10.128.0.4 >> /etc/resolv.conf
Why did you do that manually and not let the network scripts do their job?
Here's the info of that machine's connection after system administrator connected the machine using mac address.
[root@rio ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:A6:19:28 inet addr:10.154.19.136 Bcast:10.154.19.255 Mask:255.255.255.0
You hopefully have seen that things changed here: not only the IP address, but too the subnet mask changed from 255.255.248.0 to 255.255.255.0. Said that your next posting shows in ifcfg-eth0 "NETMASK=255.255.248.0" which does not reflect this change.
Now I cannot get network access. Even with dhcp enabled. The network identifies the mac address of the machine and assigns the same ip throughout.
Antonio
Alexander
-
Alexander Dalloz -
Antonio Olivares -
Jeff Vian -
jludwig -
Markku Kolkka -
Todd Nine