VOIP with a linksys PAP2

[THUFIR HAWAT]

On 6/13/05, Kevin J. Cummings <cummings at kjchome.homeip.net> wrote:
...
> eth1 is neither UP, nor has any IP address information  (no IPADDR, no
> NETMASK, no BROADCAST) so TCP/IP will not work over it.  Furthermore,
> regardless of what may be attached to the network it is plugged into,
> none of your routing referes to it (probably a side effect of not being
> configured!  B^)
> 

what's meant by "configured"?  I ask because I've used eth1 to connect
to the internet.  after physically installing eth1 and rebooting I was
presented with a menu and selected, IIRC, DHCP.

> > thank you all so much for the help here :)
> 
> If you have no devices on the eth1 network which will be DHCP servers,
> you'll either have to run one on your Linux computer for it, or you'll
> have to configure the TCP/IP staticly (ie, pick a private subnet network
> address for it, and configure the network interface at boot time, and
> configure all devices on that network so that they all have different
> address in the same subnet.  Basic TCP/IP administration, this is what
> we used to do before there was a DHCP standard!)
> 
> I'm pretty sure that if you run system-config-network (as root) you'll
> see that the eth1 interface is *NOT* active.  However, don't despair,
> its the right tool to configure that interface for you!
> 


right, and "menu-->system tools-->network device control" also seems
to bring this up.  isn't DHCP preferable because it's less fragile?

I don't understand "If you have no devices on the eth1 network which
will be DHCP servers..." when on the eth1 network will be a hub and
the VOIP PAP2.  is the PAP2 or the hub a DHCP server?  I'd think not,
but don't know.


thanks,

Thufir