Actiontec modems - Revision history

Levi: Some useless but interesting background

2010-06-23T23:47:28Z

Some useless but interesting background

2010-02-25T21:44:04Z

Added network-manager solution

2008-07-19T00:29:55Z

Added dhclient solution

2007-07-17T17:23:32Z

bind9 solution

2007-07-13T19:19:55Z

Static ip solution

2007-05-09T01:17:48Z

2007-05-09T00:34:15Z

2007-04-03T20:47:01Z

2007-04-01T06:25:40Z

2006-05-24T00:57:23Z

← Older revision		Revision as of 23:47, 23 June 2010
Line 1:		Line 1:
−	Linux boxes have difficulty connecting through Actiontec modems. The problem is that the modem supplies its own IP address as one of the nameservers, and it is apparenly non-standard enough so this will not work with our boxen.	+	Linux boxes have difficulty connecting through Actiontec modems. The problem is that the modem supplies its own IP address as one of the nameservers, and it is apparenly non-standard enough so this will not work with our boxen. This is actually a bug in the actiontec firmware as evidenced by the contents of /etc/udhcpd.conf on one of the modems.
		+	# cat /etc/udhcpd.conf
		+	start 192.168.0.2
		+	end 192.168.0.254
		+	interface br0
		+	opt router 192.168.0.1
		+	opt domain domain.actdsltmp
		+	opt dns 192.168.0.1 205.171.3.25
		+	opt subnet 255.255.255.0
		+	opt lease 86400
		+	conflict_time 86400
		+	lease_file /var/tmp/udhcpd.leases
		+

	==Static ip solution==		==Static ip solution==

@@ Line 24: / Line 24: @@
 Open /etc/dhcp3/dhclient.conf
-<code> sudo nano /etc/dhcp3/dhclient.conf </code>
+ sudo nano /etc/dhcp3/dhclient.conf
 Find this section
@@ Line 41: / Line 41: @@
 </pre>
 On an actiontec modem you should be able to look up what your dns servers should be through the web interface at 192.168.0.1
 [[Category:Tech support]]

← Older revision		Revision as of 00:29, 19 July 2008
Line 21:		Line 21:
	apt-get install resolvconf		apt-get install resolvconf

		+	==dhclient.conf method==
		+	Open /etc/dhcp3/dhclient.conf
		+
		+	<code> sudo nano /etc/dhcp3/dhclient.conf </code>
		+
		+	Find this section
		+	<pre>
		+	#prepend domain-name-servers 127.0.0.1;
		+	request subnet-mask, broadcast-address, time-offset, routers,
		+	domain-name, domain-name-servers, host-name,
		+	netbios-name-servers, netbios-scope, interface-mtu;
		+	</pre>
		+	and edit it so it looks like this (remove the '#' from 'prepend', put your dns server in place of 127.0.0.1 and remove 'domain-name-servers' from 'request'
		+	<pre>
		+	prepend domain-name-servers yourdnsserver1, yourdnsserver2;
		+	request subnet-mask, broadcast-address, time-offset, routers,
		+	domain-name, host-name,
		+	netbios-name-servers, netbios-scope, interface-mtu;
		+	</pre>
		+	On an actiontec modem you should be able to look up what your dns servers should be through the web interface at 192.168.0.1
	[[Category:Tech support]]		[[Category:Tech support]]

@@ Line 11: / Line 11: @@
 ==bind9 solution==
   apt-get install bind9
   echo 'supersede domain-name-servers 127.0.0.1;' >> /etc/dhclient.conf

@@ Line 6: / Line 6: @@
 You need to edit /etc/network/interfaces to set the static IP
-Edit /etc/resolv.conf to set the nameservers
+Edit /etc/resolv.conf to set the nameservers on a Debian box.  On Ubuntu, both IP and DNS can be set with System>Administration>Networking.
 [[ISP setup info]]

@@ Line 1: / Line 1: @@
 Linux boxes have difficulty connecting through Actiontec modems.  The problem is that the modem supplies its own IP address as one of the nameservers, and it is apparenly non-standard enough so this will not work with our boxen.
-Solution:  Set the linux box to a static IP in 192.168.0.x range, with a gateway of 192.168.0.1 and subnet mask of 255.255.255.0, and give it static dns address(es). The DNS address will vary from one ISP to another, but may generally be found by searching on google for "<ISP name> DNS server".
+==Static ip solution==
 You need to edit /etc/network/interfaces to set the static IP
@@ Line 9: / Line 10: @@
 [[ISP setup info]]
-;Another solution
+==bind9 solution==
   apt-get install bind9
   echo 'supersede domain-name-servers 127.0.0.1;' >> /etc/dhclient.conf

← Older revision		Revision as of 06:25, 1 April 2007
Line 8:		Line 8:

	[[ISP setup info]]		[[ISP setup info]]
		+
		+
		+	;Another solution
		+	apt-get install bind9
		+	echo 'supersede domain-name-servers 127.0.0.1;' >> /etc/dhclient.conf
		+	dhclient


	[[Category:Tech support]]		[[Category:Tech support]]

← Older revision		Revision as of 00:57, 24 May 2006
Line 2:		Line 2:

	Solution: Set the linux box to a static IP in 192.168.0.x range, with a gateway of 192.168.0.1 and subnet mask of 255.255.255.0, and give it static dns address(es). The DNS address will vary from one ISP to another, but may generally be found by searching on google for "<ISP name> DNS server".		Solution: Set the linux box to a static IP in 192.168.0.x range, with a gateway of 192.168.0.1 and subnet mask of 255.255.255.0, and give it static dns address(es). The DNS address will vary from one ISP to another, but may generally be found by searching on google for "<ISP name> DNS server".
		+
		+	You need to edit /etc/network/interfaces to set the static IP
		+
		+	Edit /etc/resolv.conf to set the nameservers

	[[ISP setup info]]		[[ISP setup info]]