So how does this prove a forgery? ATT Broadband got sold to Comcast recently.

This annoyed a lot of people, whose email addy gets changed for the third time in a year.
Around here the area codes got changed two years ago, and all the zip codes west of Boston
got Can changed 4 years ago. I believe its a conspiracy by the stationary companies.



"jlrogers" wrote in message
. ..
NNTP-Hosting Address: 24.62.237.242
nslookup 24.62.237.242
Canonical name: h00402b431a8d.ne.client2.attbi.com
Addresses: 24.62.237.242
IP block: IP block
Trying 24.62.237.242 at ARIN
Trying 24.62.237 at ARIN
OrgName: AT&T Broadband Northeast
OrgID: ATBN
Address: 27 Industrial Ave
City: Chelmsford
StateProv: MA
PostalCode: 01824
Country: US
NetRange: 24.60.0.0 - 24.63.31.255
CIDR: 24.60.0.0/15, 24.62.0.0/16, 24.63.0.0/19
NetName: ATTB-NE-5
NetHandle: NET-24-60-0-0-1
Parent: NET-24-0-0-0-0
NetType: Direct Allocation
NameServer: NS4.ATTBB.NET
NameServer: NS5.ATTBB.NET
NameServer: NS6.ATTBB.NET
Comment: For abuse contact
Comment: The information for POC handle ZM117-ARIN has been
Comment: reported to be invalid. ARIN has attempted to obtain updated
Comment: data, but has been unsuccessful. To provide current contact
Comment: information, please email .
RegDate:
Updated: 2003-07-03
TechHandle: ZM117-ARIN
TechName: ATT Broadband
TechPhone: +1-978-244-4020
TechEmail:
OrgTechHandle: ZM117-ARIN
OrgTechName: ATT Broadband
OrgTechPhone: +1-978-244-4020
OrgTechEmail:
Dig ...
Authoritative Answer
Recursive queries supported by this server
Query for 242.237.62.24.in-addr.arpa type=255 class=1
242.237.62.24.in-addr.arpa PTR (Pointer)
h00402b431a8d.ne.client2.attbi.com
237.62.24.in-addr.arpa NS (Nameserver) ns1.attbb.net
237.62.24.in-addr.arpa NS (Nameserver) ns2.attbb.net
237.62.24.in-addr.arpa NS (Nameserver) ns3.attbb.net
237.62.24.in-addr.arpa NS (Nameserver) ns4.attbb.net
237.62.24.in-addr.arpa NS (Nameserver) ns5.attbb.net
237.62.24.in-addr.arpa NS (Nameserver) ns6.attbb.net
ns1.attbb.net A (Address) 24.147.1.32
ns2.attbb.net A (Address) 24.129.0.106
ns3.attbb.net A (Address) 24.130.1.47
ns4.attbb.net A (Address) 24.128.1.82
ns5.attbb.net A (Address) 24.130.1.43
ns6.attbb.net A (Address) 24.129.0.103
Fast traceroute 24.62.237.242
Trace 24.62.237.242 ...
1 64.217.255.254 46ms 15ms 16ms TTL: 0
(adsl-64-217-255-254.dsl.rcsntx.swbell.net ok)
2 151.164.162.130 16ms 16ms 15ms TTL: 0
(dist1-vlan130.rcsntx.swbell.net ok)
3 151.164.1.175 16ms 15ms 16ms TTL: 0
(bb2-g1-0.rcsntx.swbell.net ok)
4 144.228.130.185 15ms 16ms 15ms TTL: 0
(sl-gw39-fw-8-0.sprintlink.net ok)
5 144.232.11.62 15ms 16ms 16ms TTL: 0
(sl-bb26-fw-9-0.sprintlink.net ok)
6 144.232.11.41 31ms 15ms 16ms TTL: 0
(sl-bb23-fw-12-0.sprintlink.net ok)
7 192.205.32.53 32ms 16ms 15ms TTL: 0
(sprint-gw.dlstx.ip.att.net bogus rDNS: host not found [authoritative])
8 12.122.12.93 31ms 32ms 16ms TTL: 0
(tbr2-p012402.dlstx.ip.att.net bogus rDNS: host not found
[authoritative])
9 12.122.10.90 47ms 31ms 32ms TTL: 0
(tbr2-p013701.sl9mo.ip.att.net bogus rDNS: host not found
[authoritative])
10 12.122.10.9 47ms 47ms 31ms TTL: 0
(tbr2-p013701.cgcil.ip.att.net bogus rDNS: host not found
[authoritative])
11 12.122.10.105 78ms 62ms 63ms TTL: 0
(tbr2-cl5.cb1ma.ip.att.net bogus rDNS: host not found [authoritative])
12 12.122.11.242 78ms 62ms 62ms TTL: 0
(gbr2-p90.cb1ma.ip.att.net bogus rDNS: host not found [authoritative])
13 12.123.40.141 63ms 63ms 62ms TTL: 0
(gar2-p370.cb1ma.ip.att.net bogus rDNS: host not found [authoritative])
14 12.125.33.34 62ms 62ms 63ms TTL: 0 (No rDNS)
15 24.128.190.61 62ms 63ms 62ms TTL: 0
(bar02-p2-0.lwllhe1.ma.attbb.net ok)
16 24.128.190.58 63ms 63ms 78ms TTL: 0
(bar02-p6-0.lwrnhe1.ma.attbb.net ok)
17 24.128.191.66 63ms 62ms 63ms TTL: 0 (No rDNS)
18 24.128.191.70 63ms 78ms 62ms TTL: 0 (No rDNS)
19 10.213.0.1 78ms 78ms 63ms TTL: 0 (No rDNS)
20 24.62.237.242 109ms 94ms 78ms TTL:106
(h00402b431a8d.ne.client2.attbi.com ok)











"Wally" wrote in message
...
"jlrogers" wrote in message news:ZNMXa.1436

Do a trace and you'll find the header is forged and so is the
routing.

Which header is forged? The IP traces to Comcast, which consistent
with
other headers. How do you know 'the header' is forged, and how did you
find
out?


It came from N. Carolina via MA.

Please show how this is so.


--
Wally
I demand rigidly-defined areas of uncertainty!
www.art-gallery.myby.co.uk