dd-wrt

DD-WRT print server configuration

When DD-WRT v24-sp1 was released, it advertised USB printer support, but I have been so skeptical that it would actually work, that I didn't even bother trying it until last night.

I followed the second set of instructions on the Printer Sharing wiki page which involve setting up a usb.startup file. After I rebooted the router, the print server was running according to ps and netstat, computers on the network seemed to be ok with connecting to it, and they would send it print jobs, but nothing ever printed.

I undid the usb.startup configuration and followed the instructions for using /jffs/etc/init.d/p910nd and it worked on my Ubuntu Linux and Windows XP machines. I haven't been able to get my MacBook to print yet, but that might be an unfortunate driver issue I can resolve by printing to another computer that's set to share the printer on the network.

Here's a quick re-cap of what I did at the DD-WRT commandline after I enabled JFFS and all USB support in the web interface except USB storage:

ls -la /dev/usb/ (should show lp0)
dmesg | usb (should list a printer)
ipkg update
ipkg -d root install p910nd
vi /jffs/etc/init.d/p910nd

Change the default path to DEFAULT=/jffs/etc/default/p910nd

Add /jffs/etc/init.d/p910nd start to the startup scripts through Administration/Commands in the web interface

/jffs/etc/init.d/p910nd start
netstat -an | grep 9100
ps | grep p910
cd /
umount /jffs
reboot

» deekayen's blog · 1 comment Topics: · ·

DNS hijacking opt-out

CTC was bought by Windstream and as evidence that they've started converting the CTC network to Windstream, when I went to a down website today, I was redirected to ww23.entry-not-found.com. Since it's Windstream branded and other people have reported it, I don't think I've been rooted. I have already complained.

If you're concerned about your DNS having the same problem, for now I apt-get install bind9 and changed my DNS from my dd-wrt box (which is using Windstream DNS servers) to 127.0.0.1.

Then in /etc/hosts I set entry-not-found.com and ww23.entry-not-found.com to resolve to 127.0.0.1.

When I asked Windstream about it, they offered an opt-out alternative:

In response to your concern, Windstream recently implemented a new feature to aid the majority of our customers experiencing issues while browsing websites. When a customer types in an incorrect web address, this feature now redirects the customer to a list of possible websites they were trying to access instead of giving the generic "Page Cannot Be Displayed." Because a majority of our customers thought to believe our service had disconnected, this change was made. However, we have seen a few examples with this that is causing a small part of our customers to be unable to access specific sites. Currently, the only way to bypass this feature is to set the opt out DNS servers into your Local Area Connection. The DNS servers are as follows:

Primary DNS Server: 166.102.165.32
Secondary DNS Server: 207.91.5.32

From the namebench.cfg file of namebench here is the Comcast opt-out list:

68.87.64.146=Comcast East Opt-Out US
68.87.68.162=Comcast Woodstock Opt-Out US
68.87.69.146=Comcast Beaverton Opt-Out US
68.87.71.226=Comcast Chelmsford Opt-Out US
68.87.72.130=Comcast Chicago Opt-Out US
68.87.73.242=Comcast Manassas Opt-Out US
68.87.74.162=Comcast Bonita Springs Opt-Out US
68.87.75.194=Comcast Pittsburgh Opt-Out US
68.87.76.178=Comcast San Jose Opt-Out US
68.87.77.130=Comcast Michigan Opt-Out US
68.87.78.130=Comcast Salt Lake City Opt-Out US
68.87.85.98=Comcast West Opt-Out US

Earthlink:

207.69.188.171=Earthlink Opt-Out US
207.69.188.172=Earthlink Opt-Out US

Verizon:

68.237.161.14=Verizon NY Opt-Out US
68.238.112.14=Verizon NC Opt-Out US


» deekayen's blog · 5 comments · 1 attachment Topics: · · ·
Syndicate content