Re: smtp port [message #39367 is a reply to message #37531] |
Sat, 10 April 2010 10:09 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
Dreamland69
Messages: 3 Registered: July 2008 Location: Laatvia
|
Junior Member |
|
|
LauraW wrote on Thu, 24 September 2009 01:17 | hello
my vps's refuses to contact all remote smtp ports (25), all other ports cause no problem and work perfectly well, iptable isnt loaded , and the command work great on harware node ??? i have had to use smtp relay http://www.smtp.com for now until this is fixed, and while it works just fine it is costing me a bit extra. So is this due to some sort of misconfiguration? how can i check? Thanks very much in advance for your time and help!
|
The same story. Debian Lenny - howtoforge.com "OpenVZ on Debian Lenny", three VN with Debian 4.0 with ISPConfig hosting control panels. All services on VH is accessable except smtp (port 25).
01. Routing rules
On HN: ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
ip route list table all
85.xxx.99.215 dev venet0 scope link
85.xxx.99.216 dev venet0 scope link
85.xxx.99.217 dev venet0 scope link
85.xxx.99.128/25 dev eth0 proto kernel scope link src 85.xxx.99.214
default via 85.xxx.99.129 dev eth0
broadcast 85.xxx.99.128 dev eth0 table local proto kernel scope link src 85.xxx.99.214
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
local 85.xxx.99.214 dev eth0 table local proto kernel scope host src 85.xxx.99.214
broadcast 85.xxx.99.255 dev eth0 table local proto kernel scope link src 85.xxx.99.214
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255
local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::226:18ff:fecd:e83d via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255
On VH: ip rule list
-bash: ip: command not found
02. Netfilter configuration
On HN:
iptables -t nat -L && iptables -t filter -L && iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
On VH:
iptables -t nat -L && iptables -t filter -L && iptables -t mangle -L
iptables v1.3.6: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
How to?
[Updated on: Sat, 10 April 2010 10:36] Report message to a moderator
|
|
|