I
think I just followed the instructions here:
http://homepage.ntlworld.com/robin.d....html#fwconfig
But it was so long ago, and I've slept since then
IIRC it turned out that once I'd made some changes, and set up ZA so that it new that the modem was trusted, it all started working properly again. Turned out that ZA was misinterpreting the requests from the modem.
Hope that helps anyway, shout back if it doesn't and I'll install ZA here and see if I can remember what I did
__________________
Here's the bit from that page that seems particularly relevent to what you're experiencing:
Quote:
|
Of the above list, the UBR's private IP address (see Finding the UBR Address above) seems to be the most important (and the one which causes difficulties unique to cable connections): the UBR acts as a DHCP Relay Agent (see RFC 2131). Several users have reported that they had difficulties acquiring or renewing their DHCP lease (symptom: disconnection every few hours) until they included their UBR as a trusted host (or permitted DHCP protocol from any host). Some firewalls are smart enough to recognise a normal DHCP transaction, but few are smart enough to recognise the validity of the DHCP broadcasts emanating from an apparently off-subnet address such as the UBR's private IP address.
|
__________________
Oh, and
by the way