Agreed, but what's the trick to permitting broadcasts? The network interface parameters seem to have this enabled:
eth0 Link encap:Ethernet HWaddr 00:16:76:A7:BC:5E
inet addr:128.3.128.30 Bcast:128.3.131.255 Mask:255.255.252.0
inet6 addr: fe80::216:76ff:fea7:bc5e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11205136 errors:0 dropped:0 overruns:0 frame:0
TX packets:1376343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1796814589 (1.6 GiB) TX bytes:398736094 (380.2 MiB)
Memory:e0080000-e00a0000
On Nov 4, 2010, at 8:24 AM, Mark Rivers wrote:
> Hi Eric,
>
> I suspect the problem is that the broadcast messages from the client are not making it through the firewall. I had a similar problem with a Windows firewall.
>
> You can run ethereal on another machine and see if it is seeing the client broadcasts.
>
> Mark
>
--
Eric Norum
[email protected]
- References:
- Firewall (iptables) issues? Eric Norum
- RE: Firewall (iptables) issues? Mark Rivers
- Navigate by Date:
- Prev:
RE: Firewall (iptables) issues? Mark Rivers
- Next:
Re: Firewall (iptables) issues? Matthieu Bec
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Firewall (iptables) issues? Mark Rivers
- Next:
Re: Firewall (iptables) issues? Matthieu Bec
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|