[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Netatalk inconsistencies wired vs. wireless.



On Jun 7, 6:35 pm, A2Aviator <a2avia...@gmail.com> wrote:
> On Jun 7, 12:37 am, mdj <mdj....@gmail.com> wrote:
>
> > Your wireless interface is passing all multicast traffic up the chain,
> > where your wired one is filtering out anything not specifically
> > intended for that host, so an 'ifconfig eth0 allmulti' would ensure
> > they're configured the same way.
>
> I just tried 'em both- same thing. Only sees the Mac, and only the Mac
> sees it.
>
> > Also, how is the IIgs being bridged? with a dedicated device or
> > LocalTalk bridging on a Mac ? It'd be good to isolate that bridge as a
> > problem mode or not, if that's possible with your equipment.
>
> Dedicated ... I have 7 of them. The IIgs sees the Mac's, just not the
> netatalk server unless it's connected to the backbone via wireless.

And the backbone is the same ethernet switch for all hosts? As in, the
the wireless bridge (I assume it's in bridge mode) is connected to the
same physical switch?

If that's the case, you might be running into a bridging problem
inside the switch itself... ie. it's possible that certain classes of
broadcast traffic are not being passed between the (probably logically
seperate) gigabit and 10/100 switches inside the multi purpose switch.

Assuming your wireless bridge has only 10/100 uplink, I'd try coercing
the linux boxes wired ethernet into 10 or 100 mode and see if that
helps.

That's the only other variable I can think of between the wired and
wireless. There has to be one somewhere... Hopefully this gives you a
few ideas.

Matt