I just solved it! Thanks Andy and Gilles.
Issuing the route command to specify the gateway (which I can also tell
from windows) did it.
Now let's try to replicate the procedure with the 2.4.28 kernel I also
have. In this case I've been having trouble with creation of nas0:
either circular refer
- Original Message -
From: "Alonso y Eydis" <[EMAIL PROTECTED]>
To:
Sent: Thursday, February 09, 2006 9:15 PM
Subject: [speedtouch] Re: RBE encapsulation in Linux
>
> Thanks for your reply Gilles.
>
> As far as what the windows utility says it is a connection type RFC1483
> using a LL
Alonso y Eydis wrote:
> Ok, after 2 days hitting myself against a wall with my little linux
> experience I ran out of ideas.
> I recompiled my 2.6.14.3 kernel with rfc2684 support as a module and
> compiled br2684 utility against it.
> After modprobe speedtch I can create a nas0 successfully usin
Thanks for your reply Gilles.
As far as what the windows utility says it is a connection type RFC1483
using a LLC encapsulation. Can you tell me if this is bridged or routed?
If it were bridged, what should be the corect procedure (kernel
settings, modules to use, etc) to establish the connecto
- Original Message -
From: "Alonso y Eydis" <[EMAIL PROTECTED]>
To:
Sent: Thursday, February 09, 2006 8:34 PM
Subject: [speedtouch] Re: RBE encapsulation in Linux
>
> Ok, after 2 days hitting myself against a wall with my little linux
> experience I ran out of ideas.
> I recompiled my
Ok, after 2 days hitting myself against a wall with my little linux
experience I ran out of ideas.
I recompiled my 2.6.14.3 kernel with rfc2684 support as a module and
compiled br2684 utility against it.
After modprobe speedtch I can create a nas0 successfully using br2684 -b
1 -e 0 -c 0 -a 0.3
Jos� Bernardo Silva wrote:
> Upgrade to latest udev, and add a rule to default-rules so that hotplug won't
> try to load firmware. I had that problem with udev 081 using the wrong
> firmware name, and after solving that I had hotplug and udev fighting to load
> the firmware at the same time.
> One
On Thu, 09 Feb 2006 14:01:16 +0100, Max Stricker wrote
> Hi,
> thanks for your help,
> my problem is that im a realy linux newbie and am not
> able to resolve this problem without help.
> I asked google how to remove udev's firmware_helper
> but i found now good answer.
> Can you please explain it
Hi,
thanks for your help,
my problem is that im a realy linux newbie and am not
able to resolve this problem without help.
I asked google how to remove udev's firmware_helper
but i found now good answer.
Can you please explain it to me?
Thanks for your atention,
Max
Jos� Bernardo Silva wrote:
On Wed, 08 Feb 2006 14:05:23 +0100, Max Stricker wrote
> >Are you using hotplug or udev to load the firmware?
>
> hotplug, and its started correctly:
>
> usb 2-1: new full speed USB device using uhci_hcd and address 2
> usb 2-1: reset full speed USB device using uhci_hcd and address 2
> speedtch
Hi,
the output i postet bevore was the output of dmesg, I can't find any
verbose information.
This is what i become with dmesg:
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: reset full speed USB device using uhci_hcd and address 2
speedtch 2-1:1.0: no stage 1 firmware
11 matches
Mail list logo
