hey linux networking peeps

[solarbird]

I’m finally getting back to working on a new gateway/router server and I’m basically setting up this old-school sort of DMZ, with the rest of our servers hanging off one card, and our internal LAN/DHCP/NAT side hanging off the other. (Using ISC, which Debian seems to like.) And all of that seems to be right from the new server’s perspective, which is yay!

Except there’s no packet forwarding from the DHCP side even though it’s enabled and I’m sure I enabled it and yes the kernel thinks its enabled but it isn’t happening.

Any ideas where to start?

Mirrored from Crime and the Blog of Evil. Come check out our music at:
Bandcamp (full album streaming) | Videos | iTunes | Amazon | CD Baby

Comments

[solarbird]

Details are that exactly nothing is being passed from the local DHCP LAN card to the gateway card. It's acting like IP forwarding is not set, which, as I said, it is set, and the OS agrees that forwarding is set.

The DMZ article I linked above in the main post is exactly what I am trying to set up, but I am not seeing packets forwarded once I've gone through their steps. From that article, I used masquerading setup that results in:

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
MASQUERADE  all  --  192.168.1.0/24      !192.168.1.0/24      

...which I hope is correct, it seems to go along with the sort of thing they were describing.

iptables -L is currently set with no filtering on forwarding (ACCEPT for all).