Topic: @HOME Cable modem setup

[Stone Linton]

Okay, thanks for the help getting the cdrom to read . . . it was an idiot user error.

I've got everything installed, but not up and running.

I've got Comcast@HOME, out of Maryland.  Running E-Smith V.3.0x.  This machine is suppose to be setup to run as a server/gateway.  The two NICs, one is a D-Link the other is very generic, but both have the RTL8029AS chips.  Top NIC is plugged in to my local hub, lower NIC, my @HOME cable modem.  All lights are on.

During boot, eth0 gets the [OK] but eth1 [FAILED] while tyring to download the DHCP info.  The build-in connectivity test fails, but I read somewhere in the General Discussions that @HOME services with upstream proxying can do this.  I can ping 127.0.0.1 successfully, 192.168.59.1 is successful, but my usually ip and gateway (24.3.16.1) fail.

If I turn off the DHCP client and insert a static ip, the one that has always been assigned to me for two years, then the systems boots without any failures, but still no connectivity.

I really want to get this thing up and running.  Would appreciate any help or advice you guys might have.  I'm not an Unix/Linux person, so step me through slowly.  Thanks.

[Gerald Jansen]

Sounds like a NIC problem. Call me superstitous. However, I always prefer not to mix NICs in any network. The fact that they have the same RealTech chip set doesn't mean they are the same. I have also experienced problems with the RTL8029AS chip set under heavy load. Never could determine if the problem was Hub or NIC related. Just know the collision light flashed like a railway warning light.

[Stone Linton]

It seems to be working now.  I setup the server in LAN server-only mode, no gateway or routing and got that working first. It turns out that eth0 is the lower NIC, then I went in throught the http server manager and changed computer name to the cX-XXXXX name from @HOME and everything worked.

Question, how does one determin which nic is which.  eth0 or eth1 before you get them working?  I've always used windows and oddly enough, always had mixed brands, so never had to figure this out on my own. First time trying to put more than on nic in anything but a home pc with windows 98 (pnp).

Anyone using this e-smith server in a production environment . . . 100 or so users?  Is it a viable alternative to dedicated equipment?

[Charlie Brady]

Stone Linton wrote:

> Question, how does one determin which nic is which.  eth0 or
> eth1 before you get them working?  I've always used windows
> and
> oddly enough, always had mixed brands, so never had to figure
> this out on my own.

If the NIC MAC address is documented, you can tell which is which by running /sbin/ifconfig -a and reading the config, and
matching eth0, eth1 against the numbers you have. Or you can ping a LAN address and see which light flashes. Apaprt from that I don't know how you tell. Mixed brands is a good way of solving the problem, I think.

Charlie

[Elcamino]

I agree on the two different nic issue.  I also think there is nothing wrong with using e-smith in production.  I have a linux box that acts as firewall/gateway for 100+ users.  Its not much hardware wise.  300mhz and 64mb ram.  Our internet pipe is a T1.  Eventually you will learn to like linux.  I have a windows/nt background and have learned to use and appreciate the unix/linux platform.  Scary to think you can have a server up for a year without a reboot.  I have yet to come anywhere near that with any NT box I've had/admined.

[Neal Cohen]

I'd like to set up a server/firewall to allow 3 PC's running Win95 and 98 to share my cable modem.

I have a spare 486/66 16mb Ram and would like to use it as the server.

I've heard linux is a good solution but don't know where to start.  Saw your discussion and hope you can advise me.

[Stone Linton]

One thing, is E-Smith needs PCI NICs, so first, does your 486 have PCI slots?  Second, the manual from E-Smith recommends a minimum of a Pentium 60 with 32 MB Ram.  But, linux is very flexible.

A 486/66 with 16MB . . . maybe that is a little skinny.  Probably run, again, Linux is very flexible.  E-Smith sets up so easily and quickly that I'd just try it, if it doesn't work, look at something like the Linux Router Project.  LRP, no hard drive required, but no proxy service either or other services (JUST ROUTING), boots linux from a single floppy, and should get your three machines the access you want through your cable modem.

[Neal Cohen]

Don'yt have PCI slots on the 486 so will get an inexpensive pentium MB with 32mb of RAM and use a spare P75 chip that's being looking for a home.  Have one Kingston 10/100 PCI and will buy another.

Should I sign up for the distribution CD ROM with the server software on it or try the downloadable?  It sets up easily? - easy as the early win95's?

[Stone Linton]

If you meet all the hardware req. then install and setup is easier and faster than early Win95 machines.  Download or buy . . . $40 . . . its a toss up.  I downloaded then printed a manual . . . for forty bucks I wish now I had just ordered the cd.  But the $40 option has NO support . . . but this forum seems pretty quick and accurate for help.  I didn't want to wait for delivery, but the press printed manual could be nice.  If there was 30-day support, I'd have paid $50-$60, but not $195 for three months.  Either the box is up in running in 6 hours, or I'm off to try something easier.  E-Smith out-of-the-box setup should take less than hour and half . . . with the execption of hardware incompatibilities, this includes setting up accounts and everything . . . READ THE MANUAL first.