> I've got my DL box accessing my DSL account just fine, I can ping
> destinations. I've set up a Fedora Core 2 box to connect to it, but I
> can't get the connection between the FC2 and the DL to actuate. I've
> tested all the hardware involved, and I don't believe there is any
> problem with that. On the DL box eth0 accesses the DSL account. eth1
> is configured in "setup" to be a DHCP server. The FC2 eth0 is
> configured to be a DHCP client. Yet I get this in dmesg on the FC2
> machine after an unsuccessful try to connect:
>
> ...
> I feel like I'm missing something very simple. I'm a networking newbie,
> can anyone help me understand what I'm leaving out, or where I can
> look? Is there some kind of further config of the DHCP server on the DL
> machine that I need to do? What services need to be turned on to get the
> NAT working, so that the inner network can access the Web through the
> DSL line? I've looked at so many manuals, and they all have very
> different, incompatible stories, and I'm stumped. I just want to share
> the DSL line between two computers on the inner LAN.
Very often it is something very simple. The trick is finding which
simple thing it is, since there are a lot of possibilities! :-)
Let's start with the most basic. Are you sure the dhcpd server is
running on your DL box? (did you reboot or start it manually after
configuring it?)
Is it possible the dhcp server is firewalled out?
Is the dhcpd.conf (config) correct?
Check your message logs on DL. ALT-F10 by default.
- BS

Hi,
I've got my DL box accessing my DSL account just fine, I can ping
destinations. I've set up a Fedora Core 2 box to connect to it, but I
can't get the connection between the FC2 and the DL to actuate. I've
tested all the hardware involved, and I don't believe there is any
problem with that. On the DL box eth0 accesses the DSL account. eth1
is configured in "setup" to be a DHCP server. The FC2 eth0 is
configured to be a DHCP client. Yet I get this in dmesg on the FC2
machine after an unsuccessful try to connect:
Sep 25 13:35:33 pa kernel: eth0: Setting full-duplex based on MII #1
link partner capability of 45e1.
Sep 25 13:35:33 pa dhclient: sit0: unknown hardware address type 776
Sep 25 13:35:34 pa dhclient: sit0: unknown hardware address type 776
Sep 25 13:35:36 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 7
Sep 25 13:35:43 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
Sep 25 13:35:51 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 11
Sep 25 13:36:02 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
Sep 25 13:36:10 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 10
Sep 25 13:36:20 pa dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 17
Sep 25 13:36:37 pa dhclient: No DHCPOFFERS received.
On the DL machine, I have this in dmesg:
eth0: link up, 100Mbps, full duplex, lpa 0x45E1
eth1: link up, 100Mbps, full duplex, lpa 0x45E1
CSLIP <some copyright stuff>
PPP <some copyright stuff>
divert: not allocating divert_blk for non-ethernet device eth0
eth1: no IPv6 routers present
eth0: no IPv6 routers present
I feel like I'm missing something very simple. I'm a networking newbie,
can anyone help me understand what I'm leaving out, or where I can
look? Is there some kind of further config of the DHCP server on the DL
machine that I need to do? What services need to be turned on to get the
NAT working, so that the inner network can access the Web through the
DSL line? I've looked at so many manuals, and they all have very
different, incompatible stories, and I'm stumped. I just want to share
the DSL line between two computers on the inner LAN.

Dave Mullen wrote:
>Hey folks,
>
>I just wanted to bounce something off of you guys, since my knowledge of
>firewalling isn't nearly as good as others.
>
>The project I'm working on is building a replacement firewall that we can
>modify easier. Our old firewall was based on RH 8.0, and used a config file
>from /etc/sysconfig/ iptables.
>
>Now that I'm moving to Devil Linux with this project, the new(er) netfilter
>(iptables new name) is setting up its rules from /etc/init.d/ firewall.rules.
>
>Now generally, I think it would be pretty easy to setup the standard:
>-A PREROUTING -p tcp -m tcp --dport 137 -j DROP
>into the new script, with simply:
>${IPTABLES} -A PREROUTING -p tcp -m tcp --dport 137 -j DROP
>
>So, that's easy and fine, but what would I do with this part of a config?
>
>*nat
>:PREROUTING ACCEPT [224:14748]
>:POSTROUTING ACCEPT [15:191]
>:OUTPUT ACCEPT [45:371]
>:NLOGNDROP - [0:0]
>:NCORPORATEFLTER - [0:0]
>:NATIT - [0:0]
>:NEWVPNFLTER - [0:0]
>
>Any thoughts? Am I just missing a really easy way to tell netfilter to load
>the old iptables conf from the same directory?
>
>Thanks in advance!
>
>Dave Mullen
>
>
I'm not an expert but that looks like the output from the
"iptables-save" command, which can be loaded with the "iptables-restore"
command, which DL does support...
Tim