I have did
tcpdump -s0 -w file.cap this shows

tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
191 packets captured
192 packets received by filter
0 packets dropped by kernel

when i capture for port 25 this shows

 tcpdump -ni venet0 -s0 -w file.cap port 25
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
0 packets captured
1 packets received by filter
0 packets dropped by kernel

and regarding to smtp trafic when i connect my load balancer from my php
application this shows
"* 421 4.3.2 No system resources"*
this problem start when i upgrade postfix from  2.3 to 2.10.
in older version of postfix this load balancer server was sending mails
successfully .
due to this relay error how can i put smtp load on load balancer.


On Fri, Sep 7, 2012 at 12:43 PM, Willy Tarreau <w...@1wt.eu> wrote:

> Hi,
>
> On Fri, Sep 07, 2012 at 12:40:38PM +0530, Naval saini wrote:
> >  tcpdump -i venet0 -e host 199.83.x.x
> > tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back
> to
> > cooked socket
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> decode
> > listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96
> > bytes
> > 11:07:38.787889 Out ethertype IPv4 (0x0800), length 252: r22.mtp.org.ssh
> >
> > 117.203.6.14.58397: P 836101525:836101721(196) ack 2820479482 win 17424
> (...)
>
> You need to put this into a file (-s0 -w file.cap) otherwise this is not
> exploitable at all. Also there is no smtp traffic here at all. I suggest
> you limit the capture to port 25 :
>
>    tcpdump -ni veth0 -s0 -w file.cap port 25
>
> Regards,
> Willy
>
>




--
View this message in context: 
http://postfix.1071664.n5.nabble.com/postfix-version-2-10-20120902-relay-issue-tp50315p50347.html
Sent from the Postfix Users mailing list archive at Nabble.com.

Reply via email to