Very Computer

1. Interface-specific firewall rules with interface aliases

It seems that ipfwadm and aliasing doesn't work very well together.
I've set up my masq box following the configuration given in the
IP-Masquerading mini HOWTO.  When doing a telnet through the masq box
I've got the following entries in the log:

    Sep  6 18:59:53 asgard kernel: IP fw-fwd deny eth0 TCP
    192.168.2.168:2210 143.89.40.159:23 L=44 S=0x10 I=6055 F=0x0040 T=63

Packets from 192.168.2.168 should have come from eth0:0 but it seems
that the kernel can't tell (after all eth0 and eth0:0 are the same
network card physically!).

The masq box is running pre-2.0.31-8.  Could anyone please give me a
clue?

--[ Albert K T Hui ]-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._

                                                           _|      _O_

2. Openserver 5 , AFPS and excel files with long names

3. FTP client inside linux firewall communicating with FTP server inside another linux firewall

4. Help with ftp prob.

5. FTP server behind linux firewall communicating w/ FTP behind linux firewall

6. Suse Linux 7.0 on Powerbook

7. slow pptp for linux firewall clients, fast pptp from Linux firewall

8. UNIX Outline Processor

9. Bridging ethernet interface through wlan interface in linux

10. Linux API to create logical interface on a physical interface?

11. Anyone Successfully run COPS on a Linux Box?

12. Cop this you Linux weenies!

13. Altavista cop-out on Titanic/Linux copy: now it is there, now it isn't