Qwest/Actiontec/Cisco/Server issues

[Eric Lee Green]

On Thursday 02 January 2003 06:07 am, Don Calfa wrote:
> I'm sure you have but have you tried the 192.168.0.1 address?  Worst
> case you could find a windows machine and run the CD.

The CD is worthless. All it does is pop up a web browser to the 192.168.0.1 
address. 

Regarding the ActionTec modem, badtux.net is being run off of that, but I do 
not attempt to use it as a firewall. I have my own firewalls plugged into it 
(three of them, one for my public network, one for my private network, one 
for my wireless network) and do my own port forwarding etc. This only works 
because I have a subnet block and not a single static IP address. 

The secret: Turn off DMZ. Turn off NAT. Set up a static IP address for the 
modem (e.g. 65.39.86.201 ). *SAVE AND RESET* the modem at this time, because 
otherwise these values will get lost due to bugs in the firmware. SET UP A 
STATIC ROUTE for your subnet, with the proper netmask and etc. for your 
subnet, telling it to forward the subnet between the LAN and the WAN. 

This wastes an address for the Actiontec modem, but was the only way I could 
get it to work.  I just plugged my firewalls into the Actiontec after 
assigning them static IP addresses, and forward ports from there to ports 
internal to my networks. 

Note: I probably forgot a few details -- it's been a few months since I did it 
-- but I do remember that a) it's a royal PITA, and b) it CAN be done, just 
not while using the Actiontec as a firewall. Get some other kind of firewall 
to go on your network side of the Actiontec, such as a Linksys Cable/DSL 
router or an elderly Linux or FreeBSD box with two network cards.

-- 
Eric Lee Green          GnuPG public key at http://badtux.org/eric/eric.gpg
          mailto:eric@badtux.org  Web: http://www.badtux.org