This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New install - can't get past firewall

New install of ASL 4 on an AMD with RealTek 8139 (eth0) and 3COM 3c905 (eth1). eth0 is statically set, and eth1 got its address successfully from dhcp. Did all nine updates so its now 4.009.

Install was easy, webadmin looks good. Put in one rule Inside Network_ Any Any Allow. Route table looks good, and the firewall can get out no problem. Point the client to this box for the default gateway, and I can't get past it. What else is there in life? Firewall, rule, route tables, and that's it right? None of the proxies have been turned on. Any troubleshooting recommendations would be appreciated.

This thread was automatically locked due to age.

Parents

0 William Warren over 22 years ago

first off..are you using dhcp in hte ASL? If so are you having ASL tell your dhcp clients the gateway ip is the ASL box?

I have a rule in the packet iflter that says From Private networks(rfc1918) -->any server-->any service--->allow.

then i have a masquerade setup in the network/NAT masquerading setup as follows:
rule type: masquerading
network: internal_network
interface: cmodem(my name for me cable modem connection)

I have other port filetering rules in place for this new rpc worm and other things..that is jsut the basic i started with..

everyone behind the ASL box can surf just fine..

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 William Warren over 22 years ago

first off..are you using dhcp in hte ASL? If so are you having ASL tell your dhcp clients the gateway ip is the ASL box?

I have a rule in the packet iflter that says From Private networks(rfc1918) -->any server-->any service--->allow.

then i have a masquerade setup in the network/NAT masquerading setup as follows:
rule type: masquerading
network: internal_network
interface: cmodem(my name for me cable modem connection)

I have other port filetering rules in place for this new rpc worm and other things..that is jsut the basic i started with..

everyone behind the ASL box can surf just fine..

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 krashe over 22 years ago in reply to William Warren

Good question. The ASL box is not serving DHCP, but its external nic is getting its address via DHCP. I have Masqerading on for Network External_Interface_ the external nic as well.

The 1 client is statically set to use the ASL box for its default gateway.
Cancel
Vote Up 0 Vote Down

Cancel
0 William Warren over 22 years ago in reply to krashe

try turning on the dhcp server and having your client reconnect(reboot if needed) and see if that fixes it..in the dhcp section set the dns servers to the astaro box internal ip and the gateway to the astaro boxes internal ip..then have clients reconnect(reboot if needed) and see if that fixes it.

also make usre you have all proxy settings set to direct connection..[:)]

Owner: Emmanuel Technology Consulting

http://etc-md.com

Former Sophos SG(Astaro) advocate/researcher/Silver Partner

PfSense w/Suricata, ntopng,

Other addons to follow
Cancel
Vote Up 0 Vote Down

Cancel
0 krashe over 22 years ago in reply to William Warren

First let me say thanks, and your prompt replys are astounding.

I tried turning on dhcp and having the client get its addresses as you recommended. No luck. Even rebooted.

The problem however is solved. It was the Masquerade. I had the Network set to External when its supposed to be Internal_Network_. I was thinking of it from the wrong angle.

Thanks again for your prompt replys.
Cancel
Vote Up 0 Vote Down

Cancel