Information for reprogramming of DTV modems General Q&A: Q) Can I use this modem with ILEC's (Verizon/SBC/etc) DSL service? A) NO Q) Can I use this modem with an ISP who will not explicitly support DTV's modems? A) NO Q) Why not?! A) Because DTV modems are really routers, and cannot be turned into bridges. Most ISPs expect a bridge, and will not route you a subnet. Q) Which ISPs support DTV modems? A) At the moment, only us, (Pilosoft), see our webpage at http://www.pilosoft.com. If you are an ISP, and you understand what's involved in supporting DTV modems, and want to be listed here, let me know (alex@pilosoft.com). Q) I'm an ISP. How do I let customers reuse their old modems? A) Read on. General information: DTV modems are essentially routers. They use "RFC1483-bridged" encapsulation (as opposed to PPPoE) for their "WAN" interface (the interface between modem and ISP's router) and ethernet between modem and PC. The "WAN" interface is regular ethernet, normally with /30 netmask. REPROGRAMMING: First, you need to do a "factory reset" of the modem. For that, insert a paperclip into "reset" opening (on X1 modem, its on the front, on X2 modem, on the back, near the power connector). Take out power, and put it back in, WHILE THE PAPERCLIP IS INSERTED. Then, press the paperclip twice very quickly. If you did it correctly, in a few seconds, you'll see "ALARM" light go red on X1, and BOTH front lights go orange on X2. This is the sequence of DTV's modem bootup, simplified for ease of implementation by ISPs. 1) Get a IP address/DNS settings for WAN interface using regular DHCP. It will set LAN IP address to 10.5.1.1. Support: Enable DHCP server on your WAN interface. Recommend giving out a "special" DNS server address, because the modems need certain IPs to resolve onto your network. 2) Now the modem expects either customer or ISP to log into it (using HTTP) and "accept" the DTV service agreement, and enter the phone number to continue signup process. Support: Log the DHCP traffic. As soon as you see reply, you can use the browser to connect to the modem, and accept the "agreement" and enter the phone number. 3. Modem will go either to oss.telocity.com or to velocityport.whoosh.com to pick up its initial configuration. Support: Fake these entries in your DNS. Actual Request will be either http:///Referral/FindMetroOffice.asp?SerialNumber=&MCCode= OR http:///Referral/FindMetroOffice.asp?DSLPhoneNumber=. You need to have web server respond with following info: -cut here- "CorporateOffice_Server=oss.telocity.com", "CorporateOffice_Port=80", "CorporateOffice_FindMetroOffice=/Referral/FindMetroOffice.asp", "CorporateOffice_GetPhoneBySerialNumber=/Referral/GetPhoneSerialNumber.asp", "CorporateOffice_LostLoginName=/Corporate/FindLoginName.asp", "CorporateOffice_LostPassword=/Corporate/FindPassWord.asp", "MetroOffice_Server=cfne.telocity.com", "MetroOffice_Port=80", "MetroOffice_MembershipServer=home.telocity.com", "MetroOffice_MeteringServer=cfne.telocity.com", "MetroOffice_MembershipPort=80", "MetroOffice_MeteringPort=80", "MetroOffice_FirstContactUpdate=/ModemConfiguration/FirstContactUpdate.asp", "MetroOffice_GetConfiguration=/ModemConfiguration/GetConfiguration.asp", "MetroOffice_GetLatestUpdate=/ModemConfiguration/GetLatestUpdate.asp", "MetroOffice_Membership=/Default.asp", "MetroOffice_ModemMetering=/ModemMetering/AddModemMetering.asp", "MetroOffice_SetModemStatus=/ModemConfiguration/SetModemStatus.asp" --cut here-- 4. Modem will now request following URL: http://cfne.telocity.com/ModemConfiguration/GetConfiguration.asp?DSLPhoneNumber=&encrypt=true Support: Reply with following information, most of it is self-explanatory: --cut here-- "ModemId=14834", "DSLPhoneNumber=", "DHCPMaxLease=86400", "DHCPDefaultLease=86400", "DSLNetwork=XXX.0", "DSLNetworkBits=24", "LANNetwork=YYYY", "LANNetworkBits=30", "InterfaceCount=1", "DryCopper=N", "MeteringFrequencySeconds=3600", "DNSCachingServer=10.99.1.4", "HTTPCachingServer=10.99.1.6", "FTPCachingServer=10.99.1.5", "SNMPGetPwd=public", "DNSServer1=", "DNSServer2=", "TimeOffGMT=-28800", "ModemAdminLogin=admin", "ModemAdminPassword=", "SNTP1=192.203.230.10", "SNTP2=16.1.0.4", "SNTP3=128.9.176.15", "DHCPEnable=true", "DNSEnable=true", "SNMPEnable=true", "HTTPRedirEnable=false", "FTPRedirEnable=false", "ImageServer1=cfne.telocity.com", "ImageServer1Port=80", "ImageServer1URI=/ModemConfiguration/TargetUpdates/getlatestupdate.asp", "ImageServer2=cfne.telocity.com", "ImageServer2Port=80", "ImageServer2URI=/ModemConfiguration/TargetUpdates/getlatestupdate.asp", "InetNode1=www.yahoo.com", "ManNode=10.99.1.2", "DCNode=oss.telocity.com", "ImageServerLogInName=admin", "ImageServerPassword=pass", "InetNode2=www.yahoo.com", "InetNode3=www.yahoo.com", "RoutableInterface=Ethernet", , , , , "Manager1=216.66.12.0", "Manager1MaskBits=24", "Manager2=216.227.56.0", "Manager2MaskBits=21", "Manager3=209.100.149.0", "Manager3MaskBits=24", "Manager4=10.99.1.0", "Manager4MaskBits=24", , , "Basic_NAT_Provisioned=OFF", "Basic_NAT_Setting=OFF", "Basic_Firewall_Provisioned=OFF", "Basic_Firewall_Setting=OFF", "BasicALTQControl=96" Now, the interesting things here are: LANNetwork, which should be set to "network" address (aka .0) for /30 network you are giving to customer. For example, if customer is at 1.10.11.97, his gateway will be 1.10.11.98, and you'll need to set LANNetwork to 1.10.11.96. DSLNetwork is the "network" address for the WAN interface, and should match the IP you assigned to the modem with DHCP. Manager* entries should be set to list of IPs allowed to connect to /admin interface on the modem. If you are not an ISP, I WILL NOT HELP YOU CONFIGURE YOUR MODEM TO WORK WITH YOUR ISP'S SERVICE, BECAUSE IT IS NOT POSSIBLE. (See Q&A) If you are an ISP and you cannot understand what I'm talking about, I will be happy to sell you an automated system which will provide all necessary configuration to DTV modems. If you are an ISP and you understood the process, but still have questions, feel free to contact me at alex@pilosoft.com