[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Netatalk inconsistencies wired vs. wireless.
On Jun 7, 4:59 pm, A2Aviator <a2avia...@gmail.com> wrote:
> Not sure what this is gonna tell you, the MTU is there, not large
> frame size.
>
> The second one is the wireless.
>
> eth0 Link encap:Ethernet HWaddr 00:0f:1f:13:24:95
> inet6 addr: fe80::20f:1fff:fe13:2495/64 Scope:Link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:22441 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2543 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3211513 (3.2 MB) TX bytes:253693 (253.6 KB)
> Interrupt:18
>
> eth1 Link encap:Ethernet HWaddr 00:12:f0:1d:a8:a9
> inet addr:192.168.0.133 Bcast:192.168.0.255 Mask:
> 255.255.255.0
> inet6 addr: fe80::212:f0ff:fe1d:a8a9/64 Scope:Link
> UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
> RX packets:65319 errors:0 dropped:0 overruns:0 frame:0
> TX packets:42977 errors:0 dropped:4 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:37273725 (37.2 MB) TX bytes:4565567 (4.5 MB)
> Interrupt:17 Base address:0x6000 Memory:fafee000-fafeefff
>
> The screwy thing, there's a Mac 9600 that has no problems being seen
> by everything.
OK, well the only 'lead' I can see there is that later versions of
EtherTalk used multicast traffic instead of broadcast. Have you tried
configuring the wired 'eth0' in either allmulti or promiscuous mode ?
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.
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
Matt