Tuesday, May 15, 2007, 08:11 AM - Personal, Networking
Spammers got me again, even with captchas in place.
I don't have time to sit around and delete spam posts all day, so I'm going to have to disable comments, sorry.
[ add comment ] | permalink |
( 2.9 / 117 )Wednesday, May 9, 2007, 02:15 PM - Linux, Programming
When debugging a Java program, breakpoints would cause the program to stop, but instead of showing my source code, it was showing a "source not found" in red. This was working fine before upgrading to feisty.
I tried editing the source lookup path to no avail.
The issue was Eclipse running under the java-gcj VM. I edited my /etc/eclipse/java_home file and placed /usr/lib/jvm/java-1.5.0-sun at the very top and restarted Eclipse. This time it ran under Sun's VM and the problem went away!
[ add comment ] | permalink |
( 2.3 / 193 )Sunday, October 8, 2006, 01:13 AM - Networking
I just had to apt-get install php4-gd. Now capcha are graphical and hopefully that will keep spammers away, for the most part.[ add comment ] ( 6 views ) | permalink |
( 2.9 / 165 )Sunday, October 8, 2006, 12:46 AM - Networking
Sorry everyone, spammers got to my blog and so I've had to temporarily disable comments. Maybe I can set up a captcha or something, then I'll be able to re-enable it.[ add comment ] | permalink |
( 2.7 / 120 )Sunday, March 19, 2006, 12:00 AM - Networking
Problem:
Actiontec GT701-WG DSL Modem has a dumb DNS issue. When you try to connect to a website from a computer running Linux, you may see "Trying 1.0.0.0" in the status bar and a failure to resolve the hostname.
Cause:
The router, which runs busybox Linux, has a DNS server program called dproxy that has a bug that exhibits itself when you try to resolve hosts from a Linux machine with IPv6 turned on. Unfortunately, you cannot disable the dproxy program and the router always sends its own IP address as the nameserver to a client that obtains an IP address via DHCP.
Fix:
Well, you could hard-code the nameservers on your computer or router that connects to the DSL modem. But here is a solution that I came up with two years ago for hard-coding the nameservers into the DSL modem itself. (Unfortunately, you have to employ this technique each time your Actiontec loses power.)
The solution is also presented below in case the link ever breaks:
!!! Actiontec GT701-WG DNS problem temporary solution: !!!
Normally I don't answer my own post, but I've found a "temporary"
solution here. This solution will __bypass the dproxy__ completely. The
only drawback I can see to this method is that you lose the ability to
access your modem at http://dslmodem.home/. Well, I'm not going to lose
sleep over _that_! I guess you also lose the DNS caching on the modem,
but hey, no big deal.
1. Telnet into your modem (username admin, password admin).
2. Change the dns line in your /etc/udhcpd.conf from this:
opt dns 192.168.0.1 206.81.128.1
to something like this:
opt dns 206.81.128.1 205.171.3.65
(where the two IP addresses are the IP addresses of the DNS servers
found in the /etc/resolv.conf).
3. Do _NOT_ kill udhcpd
- If you do it will restart and overwrite udhcpd.conf, losing your
changes.
4. Do a DHCP release, renew on the router/computer connected to your
modem.
Note: You won't find vi or emacs on your busybox, so you might have to
use cat (cat > udhcpd.conf) like I did, and recreate the file line by
line (about 10 lines long).
So, as you can see, we took out 192.168.0.1 from the dns that is sent to
a DHCP request, so whatever connects to your modem will no longer use
the modem as a dns proxy/gateway. Say goodbye to "Trying 1.0.0.0..."
Note:
I can't believe it has been over two years and this problem still hasn't been fixed! Shame on you Actiontec (and QWest). If anyone knows of a firmware update that fixes this problem, please let me know.
[ 10 comments ] ( 7066 views ) | permalink |
( 3 / 213 )Back Next
