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

Outbound access failing with new network

I have added an additional network attached to eth3 on the Sophos firewall with the following details:

HP2920 Switch
IP: 192.168.75.253
MASK: 255.255.255.0
DG: 192.168.75.254 (Sophos Eth3)

SOPHOS FIREWALL ETH3
IP: 192.168.75.254
MASK: 255.255.255.0
DG:

Now what I expected is that a client with a default gateway of 192.168.75.253 should be able to get internet access, but it doesn't work

CLIENT (doesn't work - I see nothing in the firewall log)
IP: 192.168.75.1
MASK: 255.255.255.0
DG: 192.168.75.253 (HP2920 Switch)
Dns: 8.8.8.8

CLIENT (works)
IP: 192.168.75.1
MASK: 255.255.255.0
DG: 192.168.75.254 (Sophos Eth3)
Dns: 8.8.8.8

The resellers engineer is at a loss. I have tried a different switch with the same results. I am running version 9.309-3.

This thread was automatically locked due to age.

Parents

0 DarkKnight93 over 10 years ago
Hmm Longman can you do an Tracert/traceroute on the Client not being able to connect?

for using the router function you Need to specify in config mode

ip Routing

afterwards a write mem, reload will start the router mode.

Then you can add the routes via ip route ...

Feel free to post if you have any questions on this - I can share a config file due I have 2 2920 on my hands
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 DarkKnight93 over 10 years ago
Hmm Longman can you do an Tracert/traceroute on the Client not being able to connect?

for using the router function you Need to specify in config mode

ip Routing

afterwards a write mem, reload will start the router mode.

Then you can add the routes via ip route ...

Feel free to post if you have any questions on this - I can share a config file due I have 2 2920 on my hands
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

Outbound access failing with new network

Submitted a Tech Support Case lately from the Support Portal?