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

Internal Network can not get out.

Hi,

I had once installed and was working fine. I just did a new installation with 3.202 and upgraded til 3.207. I configured both Masquerade and Packet filter, but yet my internal network can not get out. I can ping both the Internal and External nic of the firewall, but can not get beyond. The firewall can reach any destination and I can even reach the firewall from the Internet. The client are configured as DHCP client of the firewall and they do obtained IP successfully.

The configuration done so far are:

MASQ:
External Eth0_Network_ All/All MASQ_External None

Packet Filter:
Any Any Any Allow

Is there anything I have done wrong this time.

Thanks,
ao

[size="1"][ 14 August 2002, 11:59: Message edited by: ao ][/size]

This thread was automatically locked due to age.

Parents

0 giodi over 23 years ago

hi, you just misconfigured your masq.
you have (ex. to surf)
masq internal network to extenrnal.

local lan -> All / All MASQ__eth1 None

Pay attention on Maqsq, read the manual.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 giodi over 23 years ago

hi, you just misconfigured your masq.
you have (ex. to surf)
masq internal network to extenrnal.

local lan -> All / All MASQ__eth1 None

Pay attention on Maqsq, read the manual.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 peaceman over 23 years ago in reply to giodi

Giodi,

The configuration I did was as you indicated in your reply. The Eth1 nic is named as External, below are my equivalents to fields in your reply

Local lan = Eth0_Network_
MASQ_Eth1 = MASQ_External

Then I will believe I did the correct thing, except there is still something missing.
ao
Cancel
Vote Up 0 Vote Down

Cancel
0 ClausP over 23 years ago in reply to peaceman

Default GW of the Clients ?
Maybe the "paketfilter live log" shows something interesting ?

[size="1"][ 15 August 2002, 02:35: Message edited by: ClausP ][/size]
Cancel
Vote Up 0 Vote Down

Cancel
0 peaceman over 23 years ago in reply to ClausP

It has be resolved, the problem was on the DNS set to listen on Eth1 instead of Eth0
Cancel
Vote Up 0 Vote Down

Cancel