Re: IP Masquerading
From: Bob Bob (bcnntp_at_optusnet.com.au)
Date: 02/09/05
- Next message: mjt: "Re: ftp install : failed to connect to ftp server"
- Previous message: ray: "Re: I'm Sick Of SuSE!!!!!!! (Venting!!!!)"
- In reply to: Steve Magoon: "Re: IP Masquerading"
- Next in thread: Steve Magoon: "Re: IP Masquerading"
- Reply: Steve Magoon: "Re: IP Masquerading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 10 Feb 2005 05:24:17 +1100
Hi Steve
Okay on DHCP. I'd suspect that you dhcpd.conf doesnt have the global
information for your subnet. ie what the default route and DNS is. It
also gives that to the Windoze clients. For example mine has this in
part of it.
option domain-name "lse.com.au";
option domain-name-servers 192.168.0.250;
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.243 192.168.0.244;
option routers 192.168.0.250;
}
My main router box being 192.168.0.250. Note that I run a local DNS
(bind) but this may or may not be your case. If you dont you should put
the DNS address in for what the ISP gives you.
You can check these settings on your Windows boxes too. If its W9X do a
start run winipcfg and select the ethernet interface. Look for default
gateway and DNS. In NT4/W2K/WXP/W2K3 open up a CMD box and type
"ipconfig" or "ipconfig /all" (I think). You can also set the route
manually on the Windoze box in a command/cmd box by;
route add 0.0.0.0 mask 0.0.0.0 192.168.0.1
and display it with
route print
Well the routing table in your case should have taken care of itself
with the ethernet interface that was bought up and whatever your
connection to internet is. You shouldnt need any static entries.
Defining eth1 as 192.168.0.1/255.255.255.0 plugs that entry into the
routing table. The internet connection on eth0 you create, initially
sets up 68.34.192.1/255.255.255.255 on the table then because it is also
the default route 0.0.0.0/0.0.0.0 is done as well. The
169.254.0.0/255.255.0.0 looks out of place and may confuse packets bound
for that subnet (as it supersedes the default route entry and infers
that these addresses are on the wire between you and the ISP, but not on
the other side of the ISPs router)
I may not be able to check your iptables this morning. Keep in mind that
if configured so you can read off dropped packets in /var/log/messages.
No you shouldnt see a 192.168.0.1 routing tabel entry. By bringing up
the interface with a 24 bit subnet you have inferred that
192.168.0.1/255.255.255.255 is inside of 192.168.0.0.255.255.255.0
Cheers Bob
Steve Magoon wrote:
> Hey Bob,
>
> I have all the windows boxes set up as DHCP clients, and have a DHCP server
> running on the linux box. The windows boxes seem to be getting their
> assigned IP addresses just fine, in the range 192.168.0.2 - 192.168.0.10, as
> I can ping them from the linux box.
>
> On the IP routing table (below), should there be an entry for eth1 of
> 192.168.0.1 (the IP address I assigned to it with YAST) as a destination?
> Should I add that using route -add?
>
> I'll try to get the iptables list soon...
>
> Thanks for your help,
>
>
- Next message: mjt: "Re: ftp install : failed to connect to ftp server"
- Previous message: ray: "Re: I'm Sick Of SuSE!!!!!!! (Venting!!!!)"
- In reply to: Steve Magoon: "Re: IP Masquerading"
- Next in thread: Steve Magoon: "Re: IP Masquerading"
- Reply: Steve Magoon: "Re: IP Masquerading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
