--- Jeff Vian <jvian10@xxxxxxxxxxx> wrote:
> On Wed, 2005-08-31 at 12:20 -0700, Antonio Olivares
> wrote:
> >
> > --- Antonio Olivares <olivares14031@xxxxxxxxx>
> wrote:
> >
> > >
> > >
> > > --- Alexander Dalloz <ad+lists@xxxxxxxxx> 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
[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
> 2. 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
>
> 3. 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 . . . . . . . . . . . : 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
> >
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> 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
