I realized that in my frustration that I sent out the previous mail
without much supporting detail.
I'm running RH 7.2 w/ the 2.4.19 kernel. Looking at the logs for last
month, we were unable to send mail to these same servers before we
switched to 2.4.19 from RH's kernel and before we switched to the
guestlan, so it doesn't look like the new kernel/network is the
problem.(Again, we can mail to these servers from other boxes, so they
are up) There is some deeper issue here. Our mail admins don't seem
concerned, but it is driving me crazy.
Here's a sample packet from the sniffing problem that I mentioned where
ethereal only picked up ethernet traffic:
15:38:59.162376 40:0:40:6:d5:5d 45:0:0:64:ea:83 8227 100:
af10 8227 c753 0016 b94e eb9b 5f36 d63b
141e 8018 3f60 02b3 0000 0101 080a 0103
e9e9 0760 c65f 8c13 59f6 0a48 c16a ae34
5e2f 879b beef ea7f 414e 128a fc5a 1de1
0920 34d3 0374 e8a5 8a89 d6d7 f60d 5ede
ca5f
I later noticed that it was hipersocket interfaces only that produced
these results and not the iucv interfaces. Is this the "unsniffable"
hipersockets traffic that I've seen mentioned?
TIA,
Michael Lambert
>Hello, again.
>
>Although Alan's suggestion for disabling ECN cleared up the majority of
>our listerv mail problems, there are still a few servers that we can't
>send mail to. We can ping and traceroute them, but no email makes it
>through. I've sniffed the traffic on our end, and it looks like we are
>throwing two syn packets into a brick wall, with no response from them
>at all. As in the other case, we can send mail to these servers from
>other, non-mainframe linux boxes. Why the disparity?
>
>One other question...I was running ethereal on some of our other images,
>and the only output information was Etherent II...no ip, hostnames or
>anything. Our listserv box shows the expected traffic, but not these
>machines that I just installed the same version of ethereal on. Anyone
>have any idea for the cause of the difference?
