Linksys RT31P2 and Sender Policy Framework verification

Posts: 27 · Vonage Forum Junior Joined: Jun 08, 2005 Posts: 27

I use a Mozilla Thunderbird (email client) extension that performs client-side Sender Policy Framework (SPF) verification of my received e-mail messages. It has worked great.

In July, I replaced my Linksys BEFVP41 with a Linksys RT31P2 because of my new usage of Vonage services. The only difference between the two devices is one acts as a VPN server and the other acts as a voice terminal adapter. All data network routing functions and configuration are the same.

Since that time, the SPF verification has not worked from my home. I can take my laptop to any other public network, and the SPF verification works.

The only thing that I can deduce is that the Linksys RT31P2 is blocking port 53/tcp, which is how SPF communicates with public DNS servers. However, I cannot validate this deduction.

Has anyone experienced the same or similiar problem? Is there a way to validate the port 53/tcp blocking?

Thanks in advance for your help.

Posts: 1 · New Forum Member Joined: Oct 06, 2005 Posts: 1

Hi,
Did you found a way around this problem? I have a similar one, kind of silly actually. I used to access a radio station every day (mp3 streaming, shoucast server) until they decided to stream from port 53 (!). If I am connected through the RT31P2 router I can not even access the shoutcast server from my web browser, but if I get connected to the cable modem directly everithing works like a charm. It is certainly a problem of the handling of reuests to port 53 on the linksys router.

I have looked at the web configuration utility for the router but I can not find a way of getting around this.

Any ideas? Thanks.

Posts: 27 · Vonage Forum Junior Joined: Jun 08, 2005 Posts: 27

I have found no solution yet.

I did some extensive testing using the DIG command from my network and had no problems. All DIG results were positive, so it just added to my confusion. You would think that if port 53 is being blocked at the router, no port 53 functions or access would work successfully. However, the DIG tests conflicted with that assumptions.

Bottomline - I have no idea what's going on with this particular problem. However, I continue to confirm that I have no issues when I am using any other network but my own.

Thanks.