Re: Routing problem w/wireless ethernet (802.11b)
C. R. Oldham wrote: Greetings, I'm not a newbie with Debian or with networking, so this problem has been extremely frustrating to me. I have an old ThinkPad 760e with an Ositech Jack of Diamonds combo enet/modem card and an Lucent Orinoco gold card. I want to use the unit as a wireless "access point"--basically a router from the wireless ethernet onto my home network and from there out my DSL line to the Internet. I have successfully installed Debian unstable onto it and upgraded the kernel to 2.4.9. The ethernet adapter and the 802.11b adapter both work fine. The 802.11b adapter is in ad-hoc (aka "peer-to-peer") mode. This is the way my network is setup: DSL --- Linux box --switch-- TP 760e --wireless-- Dell Latitude (w2k) Interneteth0: dsleth1, ethernet: 802.11b: 192.168.2.2 192.168.1.151 eth1: 192.168.1.1eth0, 802.11b: 192.168.2.1 The Thinkpad can ping the Linux box at 192.168.1.1 and it can ping the Latitude at 192.168.2.2. It can also reach the general Internet. The Latitude can ping the Thinkpad at both 192.168.2.1 and 192.168.1.151. It *cannot* however, ping the Linux box at 192.168.1.1 or reach the general Internet. IP forwarding is turned on. For various reasons I don't want to use masquerading--I would rather just route. However I was under the impression that this should "just work" without any setup other than ip_forwarding. Here's the routing table on the Thinkpad: Kernel IP routing table DestinationGateway Genmask FlagsMetric Ref Use Iface 192.168.2.0*255.255.255.0 U 0 0 0 eth0 192.168.1.0*255.255.255.0 U 0 0 0 eth1 default192.168.1.1 0.0.0.0 UG 0 0 0 eth1 What am I missing? I know it's something stupid. Thanks in advance! --cro [EMAIL PROTECTED] You need to add a route on the Linux box to tell it how to reach the 192.168.2.0 network otherwise it will try to go through its default gateway which isn't right. Without masqerading on the IBM, packets coming from the Latitude still have their real source address which is on a different network than the Linux box and the Linux box doesn't know how to reach that network by default. I think this should work route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.151
Re: Routing problem w/wireless ethernet (802.11b)
C. R. Oldham wrote: On Thu, 23 Aug 2001, Tim Moss wrote: C. R. Oldham wrote: What am I missing? I know it's something stupid. You need to add a route on the Linux box to tell it how to reach the [...] route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.151 Thank you Tim, that was it. I was confused (amd still am a little) because I wasn't sure how that would help the other machines on the wired net reach the ones on the wireless network. However, installing that route fixes the problem for them as well. (I have some other boxes on the network that I didn't show in the diagram for the sake of brevity and clarity). Thanks again! I've been banging my head against this one for two days. --cro The other wired machines probably have the Linux box as their default gateway so, when they can't reach the Dell on their local network, they send their packets bound for it to their default gateway, which now knows how to get to the Dell. Little bit roundabout but it works.
Re: dwl-650 encryption
Tom Allison wrote: I got this wireless card working with no problems initially. But I'm trying to set up the encryption. I know it says to punch up some 112(?) bit encryption key and enter it somewhere... I might be able to figure out where, but how does one generate a realistic encryption key? Is it just a pile of hex pairs? How many? Are you using the wvlan_cs driver? Last I knew, it doesn't support encryption with cards based on the PrismII chipset (such as Linksys and your D-Link). It's not really a big deal since it's been well documented lately that the WEP encryption is pretty much useless. You could use something like FreeS/WAN (IPSec) for security between your machines (and you'll probably get better performance out the the card too since WEP tends to slow things down).
Re: how to make a serial-console linkup?
A. Demarteau (linux rules!) wrote: hi, I've already done the following: - compiled kernel with console on serial-device - added append= line to lilo.conf wiht console=38400,/dev/ttyS0 - connected cable The format for the lilo.conf entry should be console=device,options console=ttyS0,38400n8
Re: how to make a serial-console linkup?
hi, I've already done the following: - compiled kernel with console on serial-device - added append= line to lilo.conf wiht console=38400,/dev/ttyS0 - connected cable The format for the lilo.conf entry should be console=device,options console=ttyS0,38400n8 thanx, but don't forget the quote around it or lilo will complain. I had the fortmat correct, it's just the client-side setup that keeps me busy now. I generally use minicom on the client. Create a file called minirc.ttyS0 (assuming you're client is connecting from ttS0) with this info: --- pr port /dev/ttyS0 pu baudrate 38400 pu minit pu mreset pu mhangup --- and put it in /etc (or /etc/minicom/ depending on the version you're using). Then launch minicom like this minicom ttyS0 it should connect with the appropriate values for youf lilo on the target machine. Also, don't forget to add the appropriate getty entry in /etc/inittab so you can get a serial login once the system is booted T0:23:respawn:/sbin/getty -L ttyS0 38400 vt100
Re: ssh port-forwarding and UDP-connections
On Mon, 15 Oct 2001 22:00:30 +0200 (CEST) "A. Demarteau (linux rules!)" <[EMAIL PROTECTED]> wrote: > hi, > I need to use a local service form my laptop (remote location). > Thi is an udp connection. > Now I was wondering if it is possible to forward udp-connections over > an > ssh-tunnel. > > I know it's possible for tcp-connections, but this has to be udp. > Any suggestions? > ssh only does TCP forwarding. I think this software is kind of experimental (I've never used it) but it might work for what you need. http://www.math.ualberta.ca/imaging/snfs/
Re: ATI Rage Mobility-P AGP2X Hardware Acceleration
On Thu, 18 Oct 2001 19:24:09 +0800 "Michael Robinson" <[EMAIL PROTECTED]> wrote: > On Wed, Oct 17, 2001 at 08:58:40PM +0200, Michael Thaler wrote: > > I have a Sony Vaio with Ati Rage Mobility. I set up X and it works > > just fine. But yesterday someone mentioned hardware acceleration for > > the ati driver. How can I get dri working for the ati driver? I > > installed tuxracer on my notebook and it was just horrible slow, I > > guess one frame per second or something. Is there a HOWTO or > something > > to get dri working for the ATI Rage Mobility? > > I tried to do the same thing on my Dell i5000e by using the r128 > driver > (which theoretically supports dri). Problem was that the r128 driver > would > periodically crash and lock up the system. I went back to the ati > driver, and > everything is fine, but no dri. > > Can't have everything (yet), I guess. > > -Michael Robinson Not sure if this is what you are looking for but I just installed these on my laptop yesterday and XVideo works now. Other than that, I haven't really had a chance to test much but that seems like a good sign so far. http://dri.sourceforge.net/download.phtml
Re: Routing problem w/wireless ethernet (802.11b)
C. R. Oldham wrote: > Greetings, > > I'm not a newbie with Debian or with networking, so this problem has been > extremely frustrating to me. > > I have an old ThinkPad 760e with an Ositech Jack of Diamonds combo > enet/modem card and an Lucent Orinoco gold card. I want to use the unit > as a wireless "access point"--basically a router from the wireless > ethernet onto my home network and from there out my DSL line to the > Internet. > > I have successfully installed Debian unstable onto it and upgraded the > kernel to 2.4.9. The ethernet adapter and the 802.11b adapter both work > fine. The 802.11b adapter is in ad-hoc (aka "peer-to-peer") mode. > > This is the way my network is setup: > > DSL --- Linux box --switch-- TP 760e --wireless-- Dell Latitude (w2k) > Interneteth0: dsleth1, ethernet: 802.11b: 192.168.2.2 > 192.168.1.151 > eth1: 192.168.1.1eth0, 802.11b: > 192.168.2.1 > > The Thinkpad can ping the Linux box at 192.168.1.1 and it can ping the > Latitude at 192.168.2.2. It can also reach the general Internet. > The Latitude can ping the Thinkpad at both 192.168.2.1 and 192.168.1.151. > It *cannot* however, ping the Linux box at 192.168.1.1 or reach the > general Internet. > > IP forwarding is turned on. > > For various reasons I don't want to use masquerading--I would rather just > route. However I was under the impression that this should "just work" > without any setup other than ip_forwarding. > > Here's the routing table on the Thinkpad: > > Kernel IP routing table > DestinationGateway Genmask FlagsMetric Ref Use Iface > 192.168.2.0*255.255.255.0 U 0 0 0 eth0 > 192.168.1.0*255.255.255.0 U 0 0 0 eth1 > default192.168.1.1 0.0.0.0 UG 0 0 0 eth1 > > What am I missing? I know it's something stupid. > > Thanks in advance! > > --cro > [EMAIL PROTECTED] > You need to add a route on the Linux box to tell it how to reach the 192.168.2.0 network otherwise it will try to go through its default gateway which isn't right. Without masqerading on the IBM, packets coming from the Latitude still have their real source address which is on a different network than the Linux box and the Linux box doesn't know how to reach that network by default. I think this should work route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.151 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Routing problem w/wireless ethernet (802.11b)
C. R. Oldham wrote: > > On Thu, 23 Aug 2001, Tim Moss wrote: > > >>C. R. Oldham wrote: >> >>>What am I missing? I know it's something stupid. >>> >>You need to add a route on the Linux box to tell it how to reach the >> > [...] > > >>route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.151 >> > > Thank you Tim, that was it. > > I was confused (amd still am a little) because I wasn't sure how that > would help the other machines on the wired net reach the ones on the > wireless network. However, installing that route fixes the problem for > them as well. (I have some other boxes on the network that I didn't show > in the diagram for the sake of brevity and clarity). > > Thanks again! I've been banging my head against this one for two days. > > --cro > The other wired machines probably have the Linux box as their default gateway so, when they can't reach the Dell on their local network, they send their packets bound for it to their default gateway, which now knows how to get to the Dell. Little bit roundabout but it works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dwl-650 encryption
Tom Allison wrote: > I got this wireless card working with no problems initially. > But I'm trying to set up the encryption. > I know it says to punch up some 112(?) bit encryption key and enter it > somewhere... > I might be able to figure out where, but how does one generate a > realistic encryption key? Is it just a pile of hex pairs? How many? > > Are you using the wvlan_cs driver? Last I knew, it doesn't support encryption with cards based on the PrismII chipset (such as Linksys and your D-Link). It's not really a big deal since it's been well documented lately that the WEP encryption is pretty much useless. You could use something like FreeS/WAN (IPSec) for security between your machines (and you'll probably get better performance out the the card too since WEP tends to slow things down). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to make a serial-console linkup?
A. Demarteau (linux rules!) wrote: > hi, > I've already done the following: > - compiled kernel with console on serial-device > - added append= line to lilo.conf wiht console=38400,/dev/ttyS0 > - connected cable > The format for the lilo.conf entry should be console=device,options console=ttyS0,38400n8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to make a serial-console linkup?
>>>hi, >>>I've already done the following: >>>- compiled kernel with console on serial-device >>>- added append= line to lilo.conf wiht console=38400,/dev/ttyS0 >>>- connected cable >>> >>> >> >>The format for the lilo.conf entry should be console=device,options >> >>console=ttyS0,38400n8 >> > thanx, but don't forget the quote around it or lilo will complain. > I had the fortmat correct, it's just the client-side setup that keeps me > busy now. > > I generally use minicom on the client. Create a file called minirc.ttyS0 (assuming you're client is connecting from ttS0) with this info: --- pr port /dev/ttyS0 pu baudrate 38400 pu minit pu mreset pu mhangup --- and put it in /etc (or /etc/minicom/ depending on the version you're using). Then launch minicom like this minicom ttyS0 it should connect with the appropriate values for youf lilo on the target machine. Also, don't forget to add the appropriate getty entry in /etc/inittab so you can get a serial login once the system is booted T0:23:respawn:/sbin/getty -L ttyS0 38400 vt100 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ATI Rage Mobility-P AGP2X Hardware Acceleration
On Thu, 18 Oct 2001 19:24:09 +0800 "Michael Robinson" <[EMAIL PROTECTED]> wrote: > On Wed, Oct 17, 2001 at 08:58:40PM +0200, Michael Thaler wrote: > > I have a Sony Vaio with Ati Rage Mobility. I set up X and it works > > just fine. But yesterday someone mentioned hardware acceleration for > > the ati driver. How can I get dri working for the ati driver? I > > installed tuxracer on my notebook and it was just horrible slow, I > > guess one frame per second or something. Is there a HOWTO or > something > > to get dri working for the ATI Rage Mobility? > > I tried to do the same thing on my Dell i5000e by using the r128 > driver > (which theoretically supports dri). Problem was that the r128 driver > would > periodically crash and lock up the system. I went back to the ati > driver, and > everything is fine, but no dri. > > Can't have everything (yet), I guess. > > -Michael Robinson Not sure if this is what you are looking for but I just installed these on my laptop yesterday and XVideo works now. Other than that, I haven't really had a chance to test much but that seems like a good sign so far. http://dri.sourceforge.net/download.phtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh port-forwarding and UDP-connections
On Mon, 15 Oct 2001 22:00:30 +0200 (CEST) "A. Demarteau (linux rules!)" <[EMAIL PROTECTED]> wrote: > hi, > I need to use a local service form my laptop (remote location). > Thi is an udp connection. > Now I was wondering if it is possible to forward udp-connections over > an > ssh-tunnel. > > I know it's possible for tcp-connections, but this has to be udp. > Any suggestions? > ssh only does TCP forwarding. I think this software is kind of experimental (I've never used it) but it might work for what you need. http://www.math.ualberta.ca/imaging/snfs/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: orinoco & DWL-650
Apparently, on Mon, Dec 31, 2001 at 06:57:41AM -0500, Tom Allison wrote: > after moving orinoco.o and orinoco_cs.o to > /lib/modules/2.4.17-10/kernel/drivers/pcmcia/ > and linking them (ln -s ...) to /lib/modules/2.4.17/pcmcia/ > depmod -a give me: I think you also need hermes.o. The kernel pcmcia uses all three. I haven't used the pcmcia-cs package for wireless cards so I'm not sure if it's the same but it might be something to check. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: orinoco & DWL-650
Apparently, on Mon, Dec 31, 2001 at 06:57:41AM -0500, Tom Allison wrote: > after moving orinoco.o and orinoco_cs.o to > /lib/modules/2.4.17-10/kernel/drivers/pcmcia/ > and linking them (ln -s ...) to /lib/modules/2.4.17/pcmcia/ > depmod -a give me: I think you also need hermes.o. The kernel pcmcia uses all three. I haven't used the pcmcia-cs package for wireless cards so I'm not sure if it's the same but it might be something to check.
