Re: [44net] IP Protocol Filtering

(Please trim inclusions from previous messages) _______________________________________________ Greetings; I have noticed that some of the internal routing within comcast hasn't been as stable lately as it once was, and have especially noticed extremely high latency between comcast.net and other cable based networks such as rr.com from doing non-ipencap traces. This of course would affect any ipencap frames trying to use the same path. In regards to the thread that's _unnecessarily_ spawned off from this same one, there's a huge difference between a protocol and a service. ISP can filter protocols as most do OSPF, and some may indeed charge for an OSPF based peer. I've yet, however, to see an ISP charge for a protocol that a potential VPN would run on... I would think that would kill corporate-based accounts for them. -- 73 de Brian Rogers - N1URO email: <n1uro(a)n1uro.ampr.org> Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont. _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net