Re: IPtables logging failure (multiple NICs)



Grant,

I did not know that input didn't see all inbound traffic. Hmm. I'll
have to look into that. I don't suppose logging works from there,
then? But then why does it work on eth0? Maybe that's got something
to do with it. I'll give it a whirl and see what it does.

Also, about the one NIC at a time, that's the last thing I did. I
tried to use only the public block interface (eth2) from the machine's
console. Gave me the same problems. What's really strange, is that
everything's fine when it comes through eth0, works just like I want it
to, but only for that interface.

I added the /var/log/iptables to my syslog.conf file. Like I said, it
at least works for one interface, but I'm not sure why it doesn't work
for the others.

John

.



Relevant Pages

  • Re: cant ping or telnet to or from a cat 3550
    ... Logging is enabled but shows nothing at all other than a couple ... Interface FastEthernet0/18, changed state to down ... I am trying to ping from a host on Vlan 9, ... from the switch which also does not work. ...
    (comp.dcom.sys.cisco)
  • [SOLVED!!] Re: can i completely delete and recreate my network interfaces?
    ... PCI-E Fast Ethernet Controller ... recipe to restore my eth0 interface? ... i have just as little success trying to restore the wlan0 wireless ...
    (Fedora)
  • Re: [Fwd: FC9 Network Config]
    ... eth0: negotiated 100baseTx-HD, link ok ... eth1: no link ... eth2 is no link... ... Shutting down interface eth0: ...
    (Fedora)
  • Setting up a PIX 501 from scratch
    ... fixup protocol http 80 ... !--- Enable logging. ... !--- on the inside interface. ... access-group 100 in interface outside ...
    (comp.dcom.sys.cisco)
  • Basic pix configuration
    ... the inside interface is 10.10.10.250 ... fixup protocol http 80 ... access-list acl-in permit tcp host 10.10.10.50 any eq www ... no logging timestamp ...
    (comp.security.firewalls)