[NetBoot]

Other than proxing the 5504 over to WiRNS. Anyone know if it's possible to filter the connection with my firewall to stop software updates and all so keep CA/IVS?


I rather not run WiRNS if it's possible.


Currently, I'm blocking LAN to WAN access on the Replay. Looks like everythings holding.


Net...

 

[moyekj]

I didn't want to run Wirns 24/7 as well so came up with a solution where you don't have to run Wirns 24/7 to accomplish it. Follow the instructions in my sig to setup WinXP to automatically run a script once daily (or on whatever schedule you want). The only requirement is you keep your computer in sleep/hibernate mode instead of fully powered off - the scheduled job will wake up the computer if needed and kick on at scheduled time, start Wirns, force a net connect on the relevant 5504 and once the job completes the computer will go back into sleep mode. i.e. it's all automatic.


The nice side effect of this method is you can force the net connects to happen on your schedule with no chance of interfering anything instead of the dicated 24+1 hour schedule. I use this (without Wirns part) to force net connect my other 3 50xx machines.

 

[sfhub]

Quote:

Originally posted by NetBoot Currently, I'm blocking LAN to WAN access on the Replay. Looks like everythings holding.

If you don't mind losing IVS that is fine, but eventually you'll need to

connect to replay to account for clock drift and get new guide updates.


moyekj's solution is better than running wirns 24/7.


If you have an advanced firewall which will allow you to selectively respond

to http requests, you could respond to the appropriate http request in

your firewall so that replay will not perform a software update. This will

probably have to be done in your http proxy.