On Wednesday 05 March 2008 04:18:55 [EMAIL PROTECTED] wrote:
> I presume you also setting up bridging between eth1 and ath0 as per
> http://www.linux.com/feature/55617 (and NOT to eth0)
>
> I would assume then you should have an IP address configured on device br0,
> and this is also the interface ARP entries of your clients appear (view
> with arp -a)
>
> If this is not the case we might need more info (not having played with
> Linux bridging for a while)
>
> Regards, Martin
>
> On Tue, Mar 4, 2008 at 1:52 PM, Carlo Sogono <[EMAIL PROTECTED]>
>
> wrote:
> > I have built my own wireless AP with Ubuntu 7.10 and an Atheros-based
> > wireless card. My problem is that I can't access any of the Samba shares
> > with my wireless clients...they can all search for the server, get
> > prompted for a login then it just hangs and eventually times out.
> >
> > The same clients, when using their LAN ports to connect to the same
> > server are able to do everything. I have experimented with the smb.conf
> > file to include the wireless AP's device (ath0), subnet and even
> > allowing it to bind on all interfaces. During those times, samba *does*
> > bind on the device/device's IP when doing 'netstat -tln'.
> >
> > I have also checked my firewall settings. The rules I have for my local
> > LAN on eth1 is identical to ath0 so I don't see a problem there. In fact
> > I can do everything on my wireless clients except Samba.
> >
> > Here are some details of my setup:
> > Ubuntu 7.10 server
> > eth0 - ADSL modem; running pppoe
> > eth1 - local LAN
> > ath0 - wireless LAN
> > madwifi drivers for Atheros chips
> > hostapd to handle WPA2+PSK authentication
> > iptables for IP filtering
> >
> > Am I missing something here? Thanks in advance.

Carlo
<heh heh smiling> you choose the card access point rather than a $100 router 
say a dlink 640T which JustWorks(tm). This mess is what you wanted ...
James
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to