John Wittenberg wrote:
> Oct 30 19:06:51 firewall kernel: Packet log: input DENY eth0 PROTO=2
> 192.168.100.1:65535 224.0.0.1:65535 L=28 S=0xC0 I=0 F=0x0000 T=1 (#10)
I guess I am wanting to beat this dead horse a few more times. ;-)
After you get your other issues squared away, you can remove this
broadcast message by using the SILENT_DENY variable in the
/etc/network.conf file. That is lrcfg menu Network settings>Network
configuration. I used to get these irritating 224.0.0.1 broadcast
messages all the time on the old @home network. The silent deny is a
very effective was of removing them.
Greg Morgan
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
- [leaf-user] dhclient to dchp server handshaking John Wittenberg
- Re: [leaf-user] dhclient to dchp server handshak... Greg Morgan
- Re: [leaf-user] dhclient to dchp server hand... Greg Morgan
- Re: [leaf-user] dhclient to dchp server ... Greg Morgan
- Re: [leaf-user] dhclient to dchp ser... Greg Morgan
- Re: [leaf-user] dhclient to dchp server handshak... John Wittenberg
- Re: [leaf-user] dhclient to dchp server hand... Charles Steinkuehler
- Re: [leaf-user] dhclient to dchp server ... Erich Titl
- Re: [leaf-user] dhclient to dchp server handshak... Erich Titl
- Re: [leaf-user] dhclient to dchp server handshak... John Wittenberg
