Like the title says, after installing ASL 4.017 everything works fine until I configure and bring up eth1. At which point, if I'm constantly pinging the Internal IP, I can see it respond for a while, then it goes down, and nothing I can do will get it back.
I'll try to give all the info I can.
I'm using 10.1.1.27 for the internal interface (eth0), and a netmask of 255.0.0.0. No Gateway.
I'm using 10.1.1.28 netmask 255.0.0.0 and gateway of 10.1.1.1 on the external interface. But as soon as the card comes up I lose all access to the box except from console.
The box I'm accessing WebAdmin from is staticly set to 10.1.1.111 netmask 255.0.0.0 and gateway 10.1.1.1.
I have installed multiple times today to try to get this to work with no success past the initial setup. After I bring up eth1 via WebAdmin even if I log into the box at the console, and take it down it's too late. No amount of rebooting or ifconfig eth1 up|down will get me access again.
Now, the part that's baffling me most is that I can ping anything I want from the firewall box, including both interfaces, the gateway, and other boxes on the 10.1.1.X network.
I've tried using both cards as eth0 and eth1, and both will work as eth0 just fine, but both cause me to lose access when I turn on eth1. My first card is an on-board SiS card, and the second is a PCI 3COM Fast ethernet, (yes both are 100BaseT).
Please help. The install was painless, and so far I'm really liking ASL, but this is maddening.
--Phlod
This thread was automatically locked due to age.
