Ok this is admittedly OT, but when you want network advice you go to where network gurus hang... When popping mail from my primary mail server (Linux) from my linux laptop a simple mail check takes 15 seconds to connect when using a wireless nic (802.11g) and 1 second using the hardwired nic. Popping my backup mailserver (also linux) which is sitting RIGHT BESIDE the primary takes one second regardless of how the laptop is connected. Web browsing and all other internet connections are virtually instantaneous, so the wireless seems not to blame. Popping either from a different box takes one second. Only the wireless nic popping one specific mailserver is slow. Yes Shorewall is on all machines (even the laptop) but I don''t think its involved. Shorewall clear and/or stop commands make no difference). Settings of the MUA (Kmail) is the same for each account. What would make popping mail via a wireless nic slow from on server but fast to another with the same connection.? -- John Andersen - NORCOM http://www.norcomsoftware.com/
Your mail server attempts a reverse DNS lookup and finds no registration for your wireless ip or no reachable dns servers for that subnet (maybe). --- Ligiu Uiorean System Engineer Lasselsberger Ceramics Division Romania ligiu.uiorean@ro.lasselsberger.com tel. +40-740-116.117 -----Original Message----- From: shorewall-users-bounces@lists.shorewall.net [mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of John Andersen Sent: Friday, May 06, 2005 8:37 AM To: shorewall-users@lists.shorewall.net Subject: [Shorewall-users] OT: Why slow mail-check on wireless? Ok this is admittedly OT, but when you want network advice you go to where network gurus hang... When popping mail from my primary mail server (Linux) from my linux laptop a simple mail check takes 15 seconds to connect when using a wireless nic (802.11g) and 1 second using the hardwired nic. Popping my backup mailserver (also linux) which is sitting RIGHT BESIDE the primary takes one second regardless of how the laptop is connected. Web browsing and all other internet connections are virtually instantaneous, so the wireless seems not to blame. Popping either from a different box takes one second. Only the wireless nic popping one specific mailserver is slow. Yes Shorewall is on all machines (even the laptop) but I don''t think its involved. Shorewall clear and/or stop commands make no difference). Settings of the MUA (Kmail) is the same for each account. What would make popping mail via a wireless nic slow from on server but fast to another with the same connection.? -- John Andersen - NORCOM http://www.norcomsoftware.com/ _______________________________________________ Shorewall-users mailing list Post: Shorewall-users@lists.shorewall.net Subscribe/Unsubscribe: https://lists.shorewall.net/mailman/listinfo/shorewall-users Support: http://www.shorewall.net/support.htm FAQ: http://www.shorewall.net/FAQ.htm
No, I don''t think its dns because the wireless Access point obtains an IP from the same cable modem as my laptop does when connected with cat-5. In both cases they get a resolvable reverse. Both machines have the -R set on qpopper (no reverse lookup). When I tellnet to port 110 on the mail server (with wireless) there is a 10 to 15 second delay before the mail server responds with the OK message. Connection is immediate, but the OK is delayed. When I telnet to the same server when on cat-5 the OK comes back instantly. So the delay is evident even without an actual mail check, but only if I am on a wireless nic. Nothing I have seen suggests this is in anyway related to Shorewall, and I wouldn''t bother the list with this except today seems rather an un-busy day. On Friday 06 May 2005 02:21 am, Uiorean Ligiu A. wrote:> Your mail server attempts a reverse DNS lookup and finds no registration > for your wireless ip or no reachable dns servers for that subnet > (maybe). > > --- > Ligiu Uiorean > System Engineer > Lasselsberger Ceramics Division > Romania > ligiu.uiorean@ro.lasselsberger.com > tel. +40-740-116.117 > > -----Original Message----- > From: shorewall-users-bounces@lists.shorewall.net > [mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of John > Andersen > Sent: Friday, May 06, 2005 8:37 AM > To: shorewall-users@lists.shorewall.net > Subject: [Shorewall-users] OT: Why slow mail-check on wireless? > > Ok this is admittedly OT, but when you want network advice you go to > where network gurus hang... > > When popping mail from my primary mail server (Linux) from my linux > laptop a simple mail check takes 15 seconds to connect when using > a wireless nic (802.11g) and 1 second using the hardwired nic. > > Popping my backup mailserver (also linux) which is sitting RIGHT BESIDE > the primary takes one second regardless of how the laptop is connected. > > Web browsing and all other internet connections are virtually > instantaneous, > so the wireless seems not to blame. > > Popping either from a different box takes one second. > > Only the wireless nic popping one specific mailserver is slow. > > Yes Shorewall is on all machines (even the laptop) but I don''t think its > involved. Shorewall clear and/or stop commands make no difference). > > Settings of the MUA (Kmail) is the same for each account. > > What would make popping mail via a wireless nic slow from on > server but fast to another with the same connection.?-- John Andersen - NORCOM http://www.norcomsoftware.com/
John Andersen wrote:> > So the delay is evident even without an actual mail check, but only > if I am on a wireless nic. > > Nothing I have seen suggests this is in anyway related to > Shorewall, and I wouldn''t bother the list with this except today > seems rather an un-busy day. > >Then I suggest that you use Ethereal or tcpdump to monitor ALL traffic to/from your POP server while you are trying to connect. Maybe you''ll see some traffic that isn''t being responded to. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key