Static IP problem
Posted: 16 Oct 2008, 14:06
Got my Bubba 2 today. My present home setup is:
1. an ADSL modem.
2. a very old (1996) laptop with two NIC's, running Debian Sarge, connected to 1 and 3.
3. an Ethernet switch.
4. two desktop computers, one running Ubuntu Hardy, one running Debian Sid, both connected to 3.
All addresses in the system are static (no DHCP), through /etc/hosts files.
The laptop does firewall, mailserver, and Web server (Apache) duties. It is getting very old and a bit flaky, and I bought the Bubba to replace it. I do not want to enable any administrative access to the system from the outside world, but I would like to be able to telnet from a desktop machine to the Bubba. In my present setup this is done by xinetd configuration (allowing telnet access to the laptop only from the LAN).
What is the best strategy for replacement? What I did was: just plug the LAN port of the Bubba 2 into the switch. I hoped to be able to transfer data from the old laptop to the Bubba first, before employing it as the actual gateway. But so far it seems I ended up in a quagmire. When I call "pump" from the Sid machine, I can connect to the Bubba (although no longer to the Internet), but it now refuses to let me do administration using the "admin" username and the "admin" password. I must have messed up something. Any way to set it back to defaults? And then, what would the best migration strategy be in my case?
1. an ADSL modem.
2. a very old (1996) laptop with two NIC's, running Debian Sarge, connected to 1 and 3.
3. an Ethernet switch.
4. two desktop computers, one running Ubuntu Hardy, one running Debian Sid, both connected to 3.
All addresses in the system are static (no DHCP), through /etc/hosts files.
The laptop does firewall, mailserver, and Web server (Apache) duties. It is getting very old and a bit flaky, and I bought the Bubba to replace it. I do not want to enable any administrative access to the system from the outside world, but I would like to be able to telnet from a desktop machine to the Bubba. In my present setup this is done by xinetd configuration (allowing telnet access to the laptop only from the LAN).
What is the best strategy for replacement? What I did was: just plug the LAN port of the Bubba 2 into the switch. I hoped to be able to transfer data from the old laptop to the Bubba first, before employing it as the actual gateway. But so far it seems I ended up in a quagmire. When I call "pump" from the Sid machine, I can connect to the Bubba (although no longer to the Internet), but it now refuses to let me do administration using the "admin" username and the "admin" password. I must have messed up something. Any way to set it back to defaults? And then, what would the best migration strategy be in my case?