Unwanted Broadcast
Hi, I have installed ax25-apps-0.0.6 axt25-tools-0.0.8 and libax25-0.0.10 on kernel 2.4.19 (manfrake 9.0 install)
Ihave FBB,NODE,CLX and CONVERS all running OK.
There are two TNC's connected, one on port AX0 the other on AX1.
Port AX0 rgularly send broadcasts (see below) AX1 does not. As far as I can see both AX0 and AX1 have been defined the same. Any suggestions how to prevent this. They are only short packets (except when I restart the machine, especially after a few hours of it being down), but they shouldn't be there
Thanks
Barry
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 251
IP: len 251 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP
UDP: len 231 netbios-dgm->netbios-dgm Data 223
0000 ..'²,.a....Ñ.. EMEJEOFFFICACACACACACACACACACAAA. ENEEELEHFCEPFFF 0040 ACACACACACACACABO.ÿSMB%..............................7.......... 0080 .........7.V.........H.\MAILSLOT\BROWSE..m.ü..LINUX............. 00C0 ......UªSamba Server 2.2.6pre2. ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 234 IP: len 234 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP UDP: len 214 netbios-dgm->netbios-dgm Data 206 0000 ..'³,.a....À.. EMEJEOFFFICACACACACACACACACACAAA. ABACFPFPENFDECF 0040 CEPFHFDEFFPFPACAB.ÿSMB%..............................&.......... 0080 .........&.V.........7.\MAILSLOT\BROWSE..m.ü..MDKGROUP.......... 00C0 ......UªLINUX.
ax0: fm VE3NAV to VE3PZ ctl SABM+
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 26 lines · barry
Port AX0 rgularly send broadcasts (see below) AX1 does not. As far as I can see both AX0 and AX1 have been defined the same. Any suggestions how to prevent this. They are only short packets (except when I restart the machine, especially after a few hours of it being down), but they shouldn't be there
Thanks
Barry
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 251
IP: len 251 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP
UDP: len 231 netbios-dgm->netbios-dgm Data 2230000 ..'?,.a....?.. EMEJEOFFFICACACACACACACACACACAAA. ENEEELEHFCEPFFF 0040 ACACACACACACACABO.?SMB%..............................7.......... 0080 .........7.V.........H.\MAILSLOT\BROWSE..m.?..LINUX............. 00C0 ......U?Samba Server 2.2.6pre2. ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 234 IP: len 234 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP UDP: len 214 netbios-dgm->netbios-dgm Data 206 0000 ..'?,.a....?.. EMEJEOFFFICACACACACACACACACACAAA. ABACFPFPENFDECF 0040 CEPFHFDEFFPFPACAB.?SMB%..............................&.......... 0080 .........&.V.........7.\MAILSLOT\BROWSE..m.?..MDKGROUP.......... 00C0 ......U?LINUX.
Quoted 1 line
ax0: fm VE3NAV to VE3PZ ctl SABM+
Samba NetBIOS broadcasts, adjust your samba config to change it. Look around the interfaces line so that samba only runs on the interfaces you want.
A network protocol invented by Microsoft, of course its rubbish.
- Craig
Signature · 3 lines
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/ <[email protected]> MIEEE <[email protected]> Debian developer <[email protected]>
Barry,
This looks to me like a Samba broadcast. You can configure the interfaces parameter in smb.conf to specify over which interfaces Samba is allowed. From 'man(5) smb.conf':
interfaces (G)
This option allows you to override the default network inter- faces list that Samba will use for browsing, name registration and other NBT traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable.
hth,
Bob, N7XY
Quoted 35 lines · barry
Hi, I have installed ax25-apps-0.0.6 axt25-tools-0.0.8 and libax25-0.0.10 on kernel 2.4.19 (manfrake 9.0 install)
Ihave FBB,NODE,CLX and CONVERS all running OK.
There are two TNC's connected, one on port AX0 the other on AX1.
Port AX0 rgularly send broadcasts (see below) AX1 does not. As far as I can see both AX0 and AX1 have been defined the same. Any suggestions how to prevent this. They are only short packets (except when I restart the machine, especially after a few hours of it being down), but they shouldn't be there
Thanks
Barry
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV to VE3PZ ctl SABM+
ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 251
IP: len 251 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP
UDP: len 231 netbios-dgm->netbios-dgm Data 2230000 ..'?,.a....?.. EMEJEOFFFICACACACACACACACACACAAA. ENEEELEHFCEPFFF 0040 ACACACACACACACABO.?SMB%..............................7.......... 0080 .........7.V.........H.\MAILSLOT\BROWSE..m.?..LINUX............. 00C0 ......U?Samba Server 2.2.6pre2. ax0: fm VE3NAV-4 to QST ctl UI pid=CC(IP) len 234 IP: len 234 44.135.97.17->44.255.255.255 ihl 20 ttl 64 DF prot UDP UDP: len 214 netbios-dgm->netbios-dgm Data 206 0000 ..'?,.a....?.. EMEJEOFFFICACACACACACACACACACAAA. ABACFPFPENFDECF 0040 CEPFHFDEFFPFPACAB.?SMB%..............................&.......... 0080 .........&.V.........7.\MAILSLOT\BROWSE..m.?..MDKGROUP.......... 00C0 ......U?LINUX.ax0: fm VE3NAV to VE3PZ ctl SABM+
-
Signature · 3 lines
Bob Nielsen, N7XY [email protected] Bainbridge Island, WA IOTA NA-065, USI WA-028S