hawat.thufir@gmail.com wrote:
> Jeroen Geilman wrote:
> ...
> > > I hope to get the VOIP adapter plugged into it tomorrow
> >
> > Ohboy.
> ...
>
> heh. I forgot that last time I did this I was running windows. so,
> right now I'm googling on the linux driver. in the meantime, I'm
> having trouble with my VOIP providers website, at
> <http://www.telnetphone.ca/> in that it keeps reloading; mozilla would
> appear to be caught in some sort of endless loop.
>
> speaking of windows, windows2000 won't boot, for whatever reason. I
> believe I tried re-installing windows (which gums up GRUB, naturally),
> but the re-install didn't work (this was months ago). I might take
> another look at what happened with regards to installing windows on its
> partition.
>
> while the NIC was "magically" recognized and easily configured (I'm
> using eth1 at the moment for the internet connection, which is what I
> just purchased) the VOIP telephone adapter isn't, which I should've
> looked into yesterday. on reboot eth0 gave a "IP identification..," if
> I recall correctly, so the adapter needs a driver. will that require a
> kernel re-compile?
>
> or, do I just use <http://www.asterisk.org/>? I have a PAP2, not a
> mic/speakers setup.
>
> the telephone adapter:
> <http://www.linksys.com/products/product.asp?prid=651&scid=38>
>
>
>
> -Thufir




ah, I forgot about last time I did this, in windows 2000. I had to
enable ICS (Internet Connection Sharing) and buy a crosscable, IIRC.

setup is:

internet -> 802.11b router -> 802.11b network adapter -> eth1 ->
Computer -> eth0 -> PAP2

if that makes sense. the router is not accesible to me, it's my
landlord's.


-Thufir