So here's the problem:

I've been running a server of all kinds (apache, ssh, ftp, etc) on my comcast connection for over a year now. Recently, the modem was having trouble, so they came by and replaced it with a new one (a Scientific Atlanta "Webstar"). The problem is, unlike the previous modems, rather than connecting the router directly to the WAN, it creates a sort of mini-network, giving itself 192.168.1.1 and the router 192.168.1.10 or something. This isn't a problem for the router or for regular net stuff, but when I forward, for example, port 80 in the router to my webserver, all incoming connections show up as coming from 192.168.1.1 rather than their true WAN ip's.

Is there some way i could tweak with the kernel or the net driver or iptables or something (application-specific fixes are okay, but not as optimal since they must be done for each app) so the logs and whatnot show up correctly?

Thanks,
//BHolley

Well, not really... once the incoming packets have passed the modem, the original address is no longer present in the packet's header, so there is no way for "internal" hosts to find it out. Of course it will be in the modem's state tables, but there's no readily available way to get to that.

If this is important to you, better try to get a "dumb" router back, like the one you had earlier.

SOLVED

For anyone who has the same modem/problem, I was able to somehow get rid of this twilight zone between the router and modem by plugging my linux box directly in to the modem, powercycling the modem, and then running dhcpcd on it. I received a real (WAN) ip, then plugged it back into the router, powercycled again to clear the cache, and it worked like a charm.