Superpatch/MRV network configuration issues

[lgkahn]

well I've installed superpatch on a 4.01b and the new superpatch 67-all on two 6.2 dtivo rid boxes.. Hmo is working on all but mrv is working on none of the boxes.

And it is not the dns issue that everyone talks about that nutcase is so sure that is the problem.. I have dns server in resolver.conf and dns lookups are
working on all the boxes

ie

tivo:/etc$ cat resolv.conf
search localdomain
nameserver 64.222.190.114
tivo:/etc$
tivo:/etc$ ping dealdatabase.com
PING dealdatabase.com (64.21.8.90): 56 data bytes


the installs all went ok without any problems. I have gone through the logs and there are no relevant errors that I can find..

can anyone confirm maybe that tivo disables this if the ip address is not 192.168 something.. maybe they think you will share over the internet...
maybe I'll try changing to local ip to see if it works.

Can't post in nutcase's support thread because apparently he cannot take any criticism and keeps deleting my posts. Anyway it was nice of him to release it and at least hmo is working.. just wish MRV worked on my boxses...

[lgkahn]

as you can see all tivos are listening (on what I think are the correct mrv ports 2190 and 2191 not sure why each is not showing the other in nowshowing:

tivo2:
tivo:/etc$ netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:3105 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8074 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2190 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2191 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:2190 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 64 /var/dev/log
unix 2 [ ACC ] STREAM LISTENING 137 /tmp/S_EventSwitcherSoc
ket83
tivo:/etc$
tivo:/etc$


tivo3:

(none):/var/tmp$ netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:3105 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8074 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2190 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2191 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:2190 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 64 /var/dev/log
unix 2 [ ACC ] STREAM LISTENING 137 /tmp/S_EventSwitcherSoc
ket84
(none):/var/tmp$
(none):/var/tmp$


tivo1:



(none):/var/tmp$
(none):/var/tmp$ netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:3105 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8074 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2190 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2191 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5013 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:2190 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 45 /var/dev/log
unix 2 [ ACC ] STREAM LISTENING 62 /tmp/S_EventSwitcherSoc
ket82
unix 2 [ ACC ] STREAM LISTENING 344 /var/tmp/SerialPortArbi
trator
(none):/var/tmp$
(none):/var/tmp$

[alldeadhomiez]

If your superpatched boxes can't see each other, there are a number of possible culprits. In my experience, these are the things to check out:

- Is the MRV name set? Did you send an event (4.x) or reboot (6.x+) to load the new keys?

- Is there a log message in tvlog telling you that the network adapter was added as a broadcast interface? Are you seeing udp TvBus "beacons" with a sniffer? If not, this is a problem.

- Are you seeing messages in tvlog from KnownHostListener, showing the other units being added? Do you see any known hosts under /State in MFS, for the other hosts that are known to be sending out beacons? If not, this is a problem.

- Did you try "isolating" the unit? IOW, don't set a DNS server (or set it to 0.0.0.0), same for the default route. You want a quick failure when it tries to talk to something that isn't on your network. You can leave a DTiVo like this permanently; for an SA it would need to be temporary since it needs to phone home.

- Any errors in tverr?

- If you started the network interface without tivoapp's help, 6.x+ might "forget" to add it as a broadcast interface, and therefore MRV will not work. You can get around this by running the hotplug binary. (Anyone want to figure out if this is sending TvBus events?) The command might look something like: "ACTION=register INTERFACE=eth0 /sbin/hotplug". If you see messages in tvlog indicating that the interface changed state or added a broadcast address after executing that command, you're on the right track.

[ZaTHRaS]

I posted this in the superpatch67all thread.
this in reply to this

No Luck. Changed host & net to point to my router "10.0.0.254" instead, but still no luck.
remarked "#" my .author file for IP settings. Renamed dhclient.orig back to dhclient, rebooted...
mrv working great!

Is there anything wrong with my IP setting when using static? who, what, where?

[lgkahn]

thanks alldeadhomies and zathros..

the issue is indeed a network thing. strange it is listening on the correct ports put still not getting the remote now playing info.

the 4.0.1b box I didn't have to change anything it was broadcasting fine becuse I could see it with the test tivoserver program .. the others were not
but they still did not see the 4.01.b box.. so it is more than just not enabling broadcasting on the box due to static ips'

I configured my dhcp server to give out specific ips to the 6.2 boxes using the nic addresses. This still had the wireless/dhcp server as the default g/w which I don't want so I added the following lines to my rc.sysinit.author

route delete default gw 64.222.190.121 netmask 0.0.0.0 metric 1
route add default gw 64.222.190.1 netmask 0.0.0.0 metric 1

now they have the correct gateway..

all is working on all 3 now

my guess is that putting a ifconfig/static ip in the rc.sysinit.author causes eth0 to come up too late in the boot cycle for MRV to work correctly (at least for version 6.2) and as I said above it is more than just broadcasting becuase niether 6.2 box could see the 4.01b box till i changed them to dhcp.

I wish we could figure out what doesn't come up correctlly because I'd rather not use dhcp, but at least it works for now...

thanks again.. if anyone has suggestions I can continue testing..

now the 1000 question I want to block tivo2 and tivo3 from seeing tivo1 (as tivo1 has all my porn on it). I still want to see tivo2 and 3 from tivo1 however.

would you recommend just trying say blocking outgoing packets on port 2190 on tivo1 using an iptables firewall possibly. thanks for suggestions.

[lgkahn]

ok I have an iptables firewall that does what I want.. it is brought up in my rc.sysinit.author
ie
# enable firewall
/var/tivo1firewall > /var/t1f.log



here is the tivo1firewall file with ips changed for security

echo "bringing up firewall at "
date
echo " "

IPTABLES="/sbin/iptables"

echo "clearing tables"
$IPTABLES -F
$IPTABLES -X


# Set default policies for the INPUT, FORWARD and OUTPUT chains.
# These defaults clamp off all communication to or across the
# bridge box (we will add rules to allow some stuff through
# further down, after we bring up the bridge interface)

echo "setting defaults"
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT DROP
$IPTABLES -P FORWARD ACCEPT

#local subnet
echo "doing local subset on forward"
echo " "

echo "block all outgoing on port 2190 so no other tivos see us"
$IPTABLES -A OUTPUT -p TCP -s your-tivo-ip/32 --sport 2190 -j DROP
$IPTABLES -A OUTPUT -p UDP -s your-tivo-ip/32 --sport 2190 -j DROP
$IPTABLES -A OUTPUT -p TCP -s your-tivo-ip/32 --sport 2191 -j DROP
$IPTABLES -A OUTPUT -p UDP -s your-tivo-ip/32 --sport 2191 -j DROP

#block other ips we found on our subnet
echo "blocking other ips on our subnet 3,6,12,35"
$IPTABLES -A OUTPUT -p ALL -d default-gw-ip/32 -j ACCEPT

echo "our trusted subnets"
$IPTABLES -A OUTPUT -p ALL -d local-subnet-base/24 -j ACCEPT
$IPTABLES -A OUTPUT -p ALL -d work-subnet-base/26 -j ACCEPT

#block everyone else
#$IPTABLES -A OUTPUT -p ALL -d your-tivo-ip/32 -j LOG --log-prefix "Battempt Tivo1: "
$IPTABLES -A OUTPUT -p ALL -s your-tivo-ip/32 -j DROP

echo "established connection rule"
$IPTABLES -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT



of course change your-tivo-ip with the ip of the tivo you are putting the fierwall on

change the subnets to your local subnet and any other subnets.
important if you muck up your local subnet you will not be able to access the box and will be putting h/d in a computer to regain access

for you NAT people the rule would be
$IPTABLES -A OUTPUT -p ALL -d 192.168.0.0/24 -j ACCEPT


if your ips were of the range 192.168.0.1 to 192.168.0.255 (class c)


the order is important
basically it sets the default for the output filter to DROP everything if there is
no matching rule

then when it gets a packet it looks for rule in order.

so it is important that the first rules say drop all outgoing packets from your tivo source port 2190 or 2191 (both udp and tcp)

then later on it finds your trusted subnet rule so allows all other packets but those above (because it found the drop rule first) out...

[7.1]

In case anyone is still struggling with this, here's a tcpdump compiled for mips, along with an af_packet.o module for 2.4.20 (7.1a/b, at least, don't seem to ship with it). The af_packet.o module has to be insmod'd before starting tcpdump.

Here's a tcpdump run to dump the broadcast messages on the HMO broadcast port (2190):

bash-2.02# insmod af_packet.o
bash-2.02# tcpdump -nl ether broadcast and dst port 2190
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
04:36:23.386700 IP 192.168.1.108.2190 > 192.168.1.255.2190: UDP, length: 183
04:36:25.497000 IP 192.168.1.100.2190 > 192.168.1.255.2190: UDP, length: 157
04:36:38.593018 IP 192.168.1.106.2190 > 192.168.1.255.2190: UDP, length: 184
04:36:40.404983 IP 192.168.1.109.2190 > 192.168.1.255.2190: UDP, length: 183
04:36:56.639004 IP 192.168.1.101.1416 > 192.168.1.255.2190: UDP, length: 153
04:37:08.376978 IP 192.168.1.107.2190 > 192.168.1.255.2190: UDP, length: 186

You should be getting a broadcast message once a minute from every HMO tivo and every TivoDesktop, JavaHMO or other HMO server.

If you look in the tvlog, if everything is working, you should see something like this:

May 11 03:32:56 (none) TmkInit[249]: Starting program KnownHostComponent
May 11 03:32:56 (none) TmkEnvVar[249]: TV_LAUNCHER_APPLICATION_ID = 0 
May 11 03:32:56 (none) TmkEnvVar[249]: TV_LAUNCHER_PROGRAM_ID = KnownHostService 
May 11 03:32:56 (none) TmkEnvVar[249]: BROWSE_LIST = _tivo_music._tcp;_tivo_photos._tcp;_tivo_videos._tcp;_tivo_hme._tcp;_tivo_servemedia._tcp 
May 11 03:32:56 (none) TmkActivityManager[249]: Activity High Water Mark: 10
May 11 03:32:56 (none) TmkInit[249]:       0.400 seconds: TOTAL for KnownHostComponent
May 11 03:32:56 (none) TmkServer[255]: Enabling port 2190, protocol udp
May 11 03:32:57 (none) TvLauncher[120]: FINISH Start/KnownHostService:   1.336 seconds
May 11 03:32:57 (none) KnownHost[258]: Added TiVoConnect broadcast address 192.168.1.255 
May 11 03:32:57 (none) TmkServer[261]: Enabling port 2190, protocol tcp
May 11 03:32:58 (none) TmkInit[260]: Starting program SiHost

As the heartbeats come in from the other hosts, you'll see:

May 11 03:33:01 (none) KnownHost[254]: New entry: ? "?" tcd/Series2 7.1a-02-2-240 broadcast @ ? : ?

If you aren't seeing these messages, you might try ADH's /sbin/hotplug suggestion, or try configuring the network earlier in your boot process (for example, in /test.conf)

At least under 7.1x, network configuration data seems to be stored in MFS:

bash-2.02# tivosh
% mfs_ls /State/Network
dir: fsid=4456 count=1
      fsid   type     name
      -----------------------------------
      4455   tyDb     004:4455
% dumpobj 4455
NetConfig 4455/10 {
  Default        = 1
  HardwareAddress = 0 16 96 37 215 235
  IndexPath      = /State/Network/004:4455
  IpParams       = 4455/14
  NetworkMedium  = 4
  Version        = 5
}
% dumpobj 4455/14
NetConfigIpParams 4455/14 {
  AutoConfigEnabled = 0
  DnsServers     = 192.168.1.100
  GatewayAddress = 192.168.1.100
  HostAddress    = 192.168.1.107
  SubnetMask     = 255.255.255.0
}

If you want to let the tivo software setup a static network configuration, you might be able to modify these objects in MFS.


Disclaimer: I have only 7.1x machines. 6.2. might be different.

[lgkahn]

thanks 7.1 you are on the right track here.. because there are NO network menus to configure the network in 6.2 there are no ipparms keys in that part of the registry.. the menus do exist on 4.01b and that is why it works there.

I think I will write a little tcl script that sets these thinks in 6.2 and my guess is we can then get rid of the dhcp stuff.. unless someone has a better sugestions...

the menus to configure the network would be great but as previously posted it appears they don't exist in 6.2 currently.

and as I/we summized putting an ifconfig late in the boot process doesn't work for mrv..

[jasch]

There are my results so far:

I managed to get MRV working on some setups. Right now this is what I have:

Network Settings configured through DHCP (using dhclient): WORKS
Network Settings configured from within MFS (legacy configuracion from 4.x): WORKS
Network Settings configured through rc.sysinit.author (ip, gateway and DNS in resolv.conf): DO NOT WORK (the other DVR does not appear at all on the Now Playing List)

I will be running further tests later tonight, perhaps to find what the exact problem is.

It's strande that the 3rd setup would not work, since the TiVo itself was able to resolve domain names with no problems, meaning DNS was working perfectly.

[nova1]

As ADH pointed out, check /var/log/tvlog for msgs from KnownHostListener like these:

KnownHostListener[188]: Adding broadcast interface 0 with address 192.168.1.255
KnownHostListener[411]: Adding broadcast interface 0 with address 169.254.255.255

Also, if it is trying to use dhcp you should see this:

LinuxNetworkInterface[184]: If0: Automatic config

If it is using a fixed ip, you should see this:

LinuxNetworkInterface[184]: If0: Manual config

[7.1]

There are my results so far:

I managed to get MRV working on some setups. Right now this is what I have:

Network Settings configured through DHCP (using dhclient): WORKS
Network Settings configured from within MFS (legacy configuracion from 4.x): WORKS
Network Settings configured through rc.sysinit.author (ip, gateway and DNS in resolv.conf): DO NOT WORK (the other DVR does not appear at all on the Now Playing List)

I will be running further tests later tonight, perhaps to find what the exact problem is.

It's strande that the 3rd setup would not work, since the TiVo itself was able to resolve domain names with no problems, meaning DNS was working perfectly.

I'd like to see this wrapped up into a summary we can take back to the original superpatch support thread. There appear to be two different problems. One is the 'delayed' NowPlaying list. This has been previously attributed to DNS misconfigurations, although I tried to misconfigure mine on 7.1a and could never reproduced the problem. 'Isolating' the unit as ADH described might be the best solution on a dtivo. On a standalone, just make sure you have a valid DNS server set and a valid default route to a gateway.

The other problem is superpatched boxes not seeing each other. We seemed to have nailed this down to the use of static network configurations in the rc.sysinit.author. Two solutions that are now known to work:

• Use DHCP.
• Set your network settings in 4.x before you upgrade to 6.2.

Other approaches that still need to be tested:

• ADH's suggestion to invoke /sbin/hotplug after configuring the network.
• Configure the network earlier, in /test.conf
• Configure the network through a tivosh script that sets up up /State/Network.

[AhoyMatey]

I have two DTiVo's on 4.0.1b. Never had any NowPlaying problems, and have never setup DNS. The DTiVo at 192.168.1.77 has the other TiVo's network info in /State/Network:

/hack>mfs_ls /State/Network
dir: fsid=876268 count=2
      fsid   type     name
      -----------------------------------
   1066957   tyDb     004:1066957
   1197365   tyDb     004:1197365
/hack>tivosh
% dumpobj 1066957
NetConfig 1066957/10 {
  HardwareAddress = 0 16 96 38 184 178
  IndexPath      = /State/Network/004:1066957
  IpParams       = 1066957/12
  NetworkMedium  = 4
  Version        = 3
}
% dumpobj 1197365
NetConfig 1197365/10 {
  Default        = 1
  HardwareAddress = 0 16 96 36 172 59
  IndexPath      = /State/Network/004:1197365
  IpParams       = 1197365/11
  NetworkMedium  = 4
  Version        = 1
}
% dumpobj 1066957/12
NetConfigIpParams 1066957/12 {
  AutoConfigEnabled = 0
  DnsServers     = 0.0.0.0
  GatewayAddress = 0.0.0.0
  HostAddress    = 192.168.1.78
  SubnetMask     = 255.255.255.0
}
% dumpobj 1197365/11
NetConfigIpParams 1197365/11 {
  AutoConfigEnabled = 0
  DnsServers     = 0.0.0.0
  GatewayAddress = 0.0.0.0
  HostAddress    = 192.168.1.77
  SubnetMask     = 255.255.255.0
}

The second TiVo has Version=1 for it's ip address and Version=3 for 192.168.1.77's ip address. 7.1's post has Version=5 for his single TiVo.

It will be interesting to see if these numbers change when I upgrade these machines to 6.2...

[alldeadhomiez]

The second TiVo has Version=1 for it's ip address and Version=3 for 192.168.1.77's ip address. 7.1's post has Version=5 for his single TiVo.

It will be interesting to see if these numbers change when I upgrade these machines to 6.2...

The object's (local) version changes each time you update the object. It's pretty much irrelevant.

BTW: I believe I automated the hotplug event by adding an rc script in boot phase 'G', numbered 42. If you try to do this too early, it will have no effect. I found this to be necessary any time I was bringing up the interface in my scripts (instead of allowing tivoapp to manage it).

[psxboy]

The second TiVo has Version=1 for it's ip address and Version=3 for 192.168.1.77's ip address. 7.1's post has Version=5 for his single TiVo.

It will be interesting to see if these numbers change when I upgrade these machines to 6.2...

Just FYI, I believe the Version item is incremented each time the object data changes. Whether this is a built-in MFS function or just Tivo's way of keeping track of changes, I don't know. But AFAIK, there's no hard set "version" for any of these entries.

EDIT: Bah! Type slower, ADH!
-psxboy

[lgkahn]

I think we are out of luck with the tcl script unless my tcl is wrong possible but don't think, so Please check it over and see if you see a problem.

It appears the objects we need to create don't exist on the 6.2 tcl library..

here is the script and the output on 4.0.1b where the objects exists and
the error on 6.2 bummer..

#!/tvbin/tivosh
##############################################################################
# Network Config 1.0 by l.g. kahn to get around the problem
# that dtivo v. 6.2 has no network menus.
#
# This file will configure the netowrk parameters ie
# ip, default gateway etc. in the correct mfs registry locations
# as if the menus were executed.
#
# In this way you can configure your ip information and use MRV
# on the boxes. Putting an ifconfig in the normal rc.sysinit.author
# is too late in the boot process and thus MRV doesn't work.
#
# (C) 2005. No publication or sale without permission.
##############################################################################

set version "1.0"


puts "Network config v$version by L.G. Kahn"
puts ""

if [llength $argv] {set hostip [lindex $argv 0]} else { set hostip "" }
if [llength $argv] {set subnet [lindex $argv 1]} else { set subnet "" }
if [llength $argv] {set gw [lindex $argv 2]} else { set gw "" }
if [llength $argv] {set dns [lindex $argv 3]} else { set dns ""}
if {$hostip =="" || $subnet == "" || $gw == "" || $dns == ""} {
puts stderr "Error: Syntax is netconfig ipadress subnetmask defaultgw dns-server!"
exit 1
}

set db [dbopen]

ForeachMfsFile fsid name type "/State/Network/" "" {
RetryTransaction {
# puts "in loop fsid = $fsid"
}
}

RetryTransaction {
set nconfig [db $db openid $fsid]
# puts "theid = $nconfig"

#only create if not already existing
try {set ipparms [dbobj $nconfig get IpParams]} catch errCode { set ipparms "" }

if { $ipparms != "" } {

# puts "ipparms = $ipparms"
puts "IpParms object already exists, changing settings."
puts ""

set temp [dbobj $ipparms get AutoConfigEnabled]
puts "Old AutoConfigEnabled is $temp resetting to 0"
dbobj $ipparms set AutoConfigEnabled 0

set temp [dbobj $ipparms get HostAddress]
puts "Old HostAddress is $temp resetting to $hostip"
dbobj $ipparms set HostAddress $hostip

set temp [dbobj $ipparms get SubnetMask]
puts "Old SubnetMask is $temp resetting to $subnet"
dbobj $ipparms set SubnetMask $subnet

set temp [dbobj $ipparms get GatewayAddress]
puts "Old GatewayAddress is $temp resetting to $gw"
dbobj $ipparms set GatewayAddress $gw

set temp [dbobj $ipparms get DnsServers]
puts "Old DnsServers is $temp resetting to $dns"
dbobj $ipparms set DnsServers $dns

} else {
puts "IpParms Key doesn't exist creating it."
puts ""
set newipparms [db $db create IpParams]

puts "Setting AutoConfigEnabled to 0"
dbobj $newipparms set AutoConfigEnabled 0

puts "Setting HostAddress to $hostip"
dbobj $newipparms set HostAddress $hostip

puts "Setting SubnetMask to $subnet"
dbobj $newipparms set SubnetMask $subnet

puts "Setting GatewayAddress to $gw"
dbobj $newipparms set GatewayAddress $gw

puts "Setting DnsServers to $dns"
dbobj $newipparms set DnsServers $dns

dbobj $nconfig set IpParms $newipparms

}
}


dbclose $db

puts ""
puts "Make Sure the above is correct, and then reboot for changes to take effect."
puts ""
puts "WARNING if your info is incorrect you may loose access to the box. Double check the settings end re-run the script if incorrect before rebooting!"



4.0.1b


(none):/var$ netconfig.tcl 85.223.190.115 255.255.255.0 85.223.190.1 85.223.1
90.114
Network config v1.0 by L.G. Kahn

IpParms object already exists, changing settings.

Old AutoConfigEnabled is 0 resetting to 0
Old HostAddress is 85.223.190.115 resetting to 85.223.190.115
Old SubnetMask is 255.255.255.0 resetting to 255.255.255.0
Old GatewayAddress is 85.223.190.1 resetting to 85.223.190.1
Old DnsServers is 85.223.190.114 resetting to 85.223.190.114

Make Sure the above is correct, and then reboot for changes to take effect.

WARNING if your info is incorrect you may loose access to the box. Double check
the settings end re-run the script if incorrect before rebooting!
(none):/var$
(none):/var$



6.2

tivo:/var$ netconfig.tcl 85.223.190.98 255.255.255.0 85.223.190.1 85.223.190.114

Network config v1.0 by L.G. Kahn

IpParms Key doesn't exist creating it.

invalid object type
while executing
"db $db create IpParams"
("uplevel" body line 37)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 5)
invoked from within
"RetryTransaction {
set nconfig [db $db openid $fsid]
# puts "theid = $nconfig"

#only create if not already existing
try..."
(file "./netconfig.tcl" line 40)
tivo:/var$
tivo:/var$