Re: [leaf-user] My Dachstein not quite up and running

[Ray Olszewski]

Several specifics below. But first a general one: looking at changes to config files helps us understand what you are trying to do, and sometimes we can spot an error that way. But it also helps to know what you are actually doing ... that is, how the router's underlying configuration really is set. For that reason, when you run into these problems, you should look at the real settings that the config files create, with (in this instance)

netstat -nr
ipchains -nvL

At 05:46 PM 2/7/03 -0800, Chris Low wrote:

> >It needs to be 192.168.1.2 to match the address the mail is being
> >forwarded to.
> I'll give it a try.

Didn't work. Still can only send, not receive.

In case you don't already know this ... sending and receiving mail operate very differently. You don't even need to run an SMTP daemon to send mail. All the configuration issues you are addressing relate to the ability to receive mail.

In addition to reviewing the firewall rulesets, you could work on this one by using telnet to connect to (internally, from between the routers) 192.168.1.2 25 or (from the Internet)208.57.96.254 25 . I just tried the second, with this result:

autovcr@waverly:~$ telnet 208.57.96.254 25
Trying 208.57.96.254...

autovcr@waverly:~$ ping 208.57.96.254
PING 208.57.96.254 (208.57.96.254): 56 data bytes
64 bytes from 208.57.96.254: icmp_seq=0 ttl=245 time=37.6 ms
64 bytes from 208.57.96.254: icmp_seq=1 ttl=245 time=38.0 ms

--- 208.57.96.254 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 37.6/37.8/38.0 ms
autovcr@waverly:~$

(The ping part is just to confirm that the problem isn't just Internet connectivity.) This failure implies that the handoff from ISP router to LEAF router to Exchange server is failing somewhere along the line.

I did notice this typo in a prior message:

The exchange server is now 10.10.10.2
... and ...
INTERN_SERVERS="tcp_$192.168.1.2_smtp_10.10.10.200_smtp"

The two IP addresses are different; they need to be the same (I don't know which is right, or if the trpo was just in the message or indicates an actual configuration problem).

> >Have you loaded the portfw module???
is it listed in the "lsmod" command?

Yep.

module pages used by
ip_masq_portfw 2416 0 (unused)

Here's something else fun to work on while we're at it: I tried putting other machines behind the firewall today since the office was empty (office retreat, except for me!) and only the NT box, and the Exchange server (Running Windows 2000 server) can browse the web. Our windows 98se, windows me, and windows 95 computers can't. They log into the server fine, get an ip address fine, just no web. They can ping the firewall (both interfaces) and the ISP's router (also both interfaces) but when I ping something like www.yahoo.com it comes back with "unknown host". Any ideas on this one?

This is almost surely a DNS problem. When your hosts got their DHCP assignments from the ISP's router, they rceived in them the IP addresses of the DNS servers they are supposed to use. Unless you added that information to the LEAF router's dhcpd config file, it is not providing the DNS settings. Fix this and the particular problem you are describing here will go away.


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html