On 1/25/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Dr. Edgar Alwers wrote these words on 01/25/06 15:43 CST:
>
> > This was it. Thank you and Jeremy very much for your comments and
> > help.Introducing a "ifconfig.eth1" with the data of the old ifconfig.eth0
> > did
> > the job. I now will tr
On 1/25/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> Now, I've been meaning to get wireless-tools into the book for a
> *long* time. One thing or another keeps coming up that I end up
> doing instead.
>
> So, hurry up and create that hint so one of us BLFS Editors can
> copy it and put it in t
Dr. Edgar Alwers wrote these words on 01/25/06 15:43 CST:
> This was it. Thank you and Jeremy very much for your comments and
> help.Introducing a "ifconfig.eth1" with the data of the old ifconfig.eth0 did
> the job. I now will try to add all my experiences and perhaps they add to a
> BLFS-Hint
On Wednesday 25 January 2006 16:53, Randy McMurchy wrote:
> Well, it should be all downhill from here for you. :-)
>
> I'm *guessing* that the wireless is *right now* configured as eth1.
> (from the message above). You'll need to do everything you did for
> eth0 to get eth1 working on your network.
