> Message: 2 > Date: Mon, 03 Jun 2002 11:08:35 -0600 > From: Matt Russell <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [leaf-user] Bering with Orinoco wireless -- problems > > Looking through the archives (even as of late) it has come to my > attention that many hold the same position on this situation as I do.. > > i have a 400mhz p2 system, 256MB RAM, Bering v1.0 rc2 with a 3com > 3c905c-tx-m pci card, an ISA-to-PCMCIA card, and an Orinoco wireless > "SILVER" card, flash version 6.06 (as reported by > /var/log/syslog). eth0 > is my INTERNAL network (ethernet 3com card) and eth1 is my EXTERNAL > network (Orinoco wireless). > > The card is intialized and configured correctly, that is, i > recieve two > beeps and "ip addr show" reports: > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 brd 127.255.255.255 scope host lo > 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop > link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff > 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc > pfifo_fast qlen 100 > link/ether 00:04:76:e2:6c:6c brd ff:ff:ff:ff:ff:ff > inet 192.0.1.7/24 brd 192.0.1.255 scope global eth0 > 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc > pfifo_fast qlen 100 > link/ether 00:02:2d:08:fc:27 brd ff:ff:ff:ff:ff:ff > inet 65.121.99.173/25 brd 65.121.99.255 scope global eth1 > > iwconfig reports: > eth1 IEEE 802.11-DS ESSID:"BERING" Nickname:"HOME" > Mode:Ad-Hoc Frequency:2.437GHz Cell: 00:02:2D:08:FC:27 > Bit Rate=2Mb/s Tx-Power=15 dBm Sensitivity:1/3 > Retry limit:4 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > i can ping from my internal (eth0) network to the router. i can ping > from the router to the internal (eth0) interface. i can ping > eth1 from > the router (to verify that the ip is indeed being assigned to the > wireless card) > > one thing that i thought of while i was configuring everything (and > something that could very well easily be overlooked) is to change the > ip_forward variable in /etc/network/options to yes. this is > correct, right? > > just for fun i'll include the routing files, so get a deep breath.
<HUGE SNIP> I didn't see an actual question, so will assume it 'just doesn't work'! ;-) If the wireless card is for your connection to your ISP, I would expect that you'd be connecting to a true access point. Accordingly, you would want to set the card to 'managed' rather than 'ad-hoc', or so I would expect. I suspect the ESSID etc. needs to match the wireless network settings. Of course, if you are doing this to provide a private wireless backbone my comments aren't worth much. Ad-hoc mode changed with the firmware right around the version you have. Lucent offers 8.1 now, perhaps it would be worth upgrading - on both ends! If you have mismatched firmware revisions across that ad-hoc change, you wouldn't be getting too far. I had 6.04 which was the old version, but I thought (?) 6.08 or so was where the change to IBSS ad-hoc happened. A scan through the orinocowireless.com site should set you straight on that point. I suspect iwconfig settings are the issue. Channel, Data rate, ESSID etc. I don't have access to my box right now to compare your other settings, but at first glance seem OK. If I've missed your question, sorry. Does any of this help? Brock _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
