Dunno if there's a mail list problem, as there are no posts on this since the
9th, but...
1. mode master is when you're setting up an access point, managed when
connecting to an AP.
2. You can most certainly have ath0 and eth0 on the same subnet, but just don't
have them up and running at the same time! - ifconfig ath0/eth0 up/down is your
friend here. However, I'm not too sure how you're routing your wireless network
onto the same subnet as your hardwired one. It's certainly confusing as most
AP's are routers as well, so will be passing requests upstream - probably to
your router, whereas you may be expecting the wireless network to extend your
hardwired one?
I use a minipci card with the same chipset on my lappie, and this is how mine
is set up ( at present, access is to the internet alone, not my wired network ):
ifconfig ath0
ath0 Link encap:Ethernet HWaddr 00:02:xx:20:xx:02
inet addr:192.168.xx.xxx Bcast:192.168.xx.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:242 errors:4276 dropped:0 overruns:0 frame:4276
TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:200
RX bytes:30045 (29.3 KiB) TX bytes:29142 (28.4 KiB)
Interrupt:3 Memory:e0ec0000-e0ed0000
iwconfig ath0
ath0 IEEE 802.11g ESSID:"MyESSID"
Mode:Managed Frequency:2.437 GHz Access Point: 00:02:6F:32:A8:65
Bit Rate:11 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:myen-crypt-ke Security mode:restricted
Power Management:off
Link Quality=26/94 Signal level=-69 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
route ( set up from dhcp server on the AP )
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.xx.0 * 255.255.255.0 U 0 0 0 ath0
default 192.168.xx.254 0.0.0.0 UG 0 0 0 ath0
( my AP routes directly to my adsl router from the 192.168.xx.0/24 net ).
/etc/network/interfaces ( debian system )
auto ath0
iface ath0 inet dhcp
pre-up /sbin/iwpriv ath0 mode 3
pre-up /sbin/iwconfig ath0 essid "MyESSID" key myencryptke channel 6
Sorry, con't convert to suse, but this all works fine. MadWIFI drivers are
still in beta, and are released daily, so don't worry too much about the
reported error levels on the card.
HTH,
Steve
On Fri, 09 Dec 2005 12:44:07 +1300
Nick Rout <[EMAIL PROTECTED]> wrote:
>
> On Fri, 09 Dec 2005 10:06:06 +1300
> Roger Searle wrote:
>
> > i believe "managed" equals "connect to an access point". the other
> > option being "ad-hoc" which means "connect to another computer without
> > access point". ip address statically or via dhcp is independent of this.
> >
> > yesterday i was reading a good article on the novell site about
> > configuring wireless cards in suse (unfortunately i can't locate it
> > right now), which confirmed the option to use is "managed".
> >
> > yast also offers a "master" option - i don't know what that means.
> >
> > roger
>
>
> yes the above is my understanding too. master may be, i think, when you
> want your computer to be the access point.
> >
> >
> --
> Nick Rout <[EMAIL PROTECTED]>
>
