Superpatch/MRV network configuration issues [Archive] - DealDatabase Forum - Deals, Freebies, and TiVo & DirecTivo Hacking

lgkahn

05-11-2005, 09:49 PM

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

05-11-2005, 10:02 PM

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

05-11-2005, 11:03 PM

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

05-11-2005, 11:30 PM

I posted this in the superpatch67all thread.
this (http://www.dealdatabase.com/forum/showpost.php?p=222384&postcount=16) in reply to this (http://www.dealdatabase.com/forum/showpost.php?p=222375&postcount=15)

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

05-12-2005, 12:55 AM

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

05-12-2005, 01:50 AM

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

05-12-2005, 02:04 AM

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: 186You 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

05-12-2005, 09:06 AM

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

05-12-2005, 11:36 AM

nova1

05-12-2005, 12:35 PM

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

05-12-2005, 12:40 PM

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

05-12-2005, 01:56 PM

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

05-12-2005, 02:18 PM

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

05-12-2005, 02:22 PM

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

05-12-2005, 02:50 PM

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$

lgkahn

05-12-2005, 02:56 PM

I tried the hotplug suggestions and unless I did something wrong didn't seem to work... but as I said I don't think it is a simple broadcast issue which is what the hotplug did because my 4.0.1b was broadcasting ok and still couldn't see it on my 6.2 dtivos till I enabled dhcp.

7.1

05-12-2005, 03:01 PM

...because my 4.0.1b was broadcasting ok ...How did you verify this? With tcpdump?

As to your script: it's broken. You are trying to create an IpParms tyDB object. That object type doesn't exist in any schema, as far as I know. I think you want NetConfigIpParams. IpParams is the name of the attribute that references the NetConfigIpParams object, not the object type. And it should be created as a subobject of the NetConfig object.

Look around and you should be able to find scripts around that can dump the schema. As far as I know, the schema's in newer software versions always extend the previous schemas. They never drop object types or attributes, they just mark them as obsolete.

jasch

05-12-2005, 03:04 PM

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.

That's exactly what I've been trying to do on my own. I already have a script to 'change' the settings from units that upgraded from 4.x to 6.x and still have the IP information on IpParams.

So far, so good. The script works.

Right now I am having trouble creating IpParams on a unit that does not has the entry...

I know 6.2 supports it, since my other "upgraded" units retained the MFS settings, and they are used by the system.

psxboy

05-12-2005, 03:07 PM

puts "IpParms Key doesn't exist creating it."
puts ""
set newipparms [db $db create IpParams]
How about telling the transaction where to create the IpParams object? Try this & see if it works any better on 6.2:
puts "IpParms Key doesn't exist creating it."
puts ""
set newipparms [db $db createsub IpParams $nconfig]

-psxboy

alldeadhomiez

05-12-2005, 03:14 PM

LanMan

05-12-2005, 05:33 PM

7.1

05-12-2005, 05:44 PM

lgkahn,

I tweaked your script with 7.1 and psxboy's suggestions. I've tested it on
a Dtivo running 6.2 (Never had 4.01b installed) and a Dtivo running 6.2 (Upgraded from 4.01b). Works for me with no mrv problems.

Test it at your own risk..........

Thanks to lgkhan, 7.1 and psxboy.

EricOne note: As AhoyMatey observed, there may be more than one NetConfig object in the /State/Network directory. Your code always modifieds the last one. I suspect the one you really want to modify is the one marked with attribute Default set to 1.

Also, the script does not deal with the case that /State/Network is empty: there are no NetConfig objects at all. Are we sure that can't happen?

lgkahn

05-12-2005, 07:11 PM

1. as I said it is the ipparm object..
2. I will modify it to loop through and only get the with with dfault = 1
3. will may change as above.. when you do that the last line to set the new
object to the child of ipparm is not needed as you already created it as
a subobject

as for the last point this script probably is only for those people that already
have the box working (ie have access via dhcp or ifconfig and want
to get rid of dhcp... so it will be pretty clear when you run it and reboot if
it worked or not.

lgkahn

05-12-2005, 07:55 PM

I had to make a few changes fetching the key it is called ipparams the only place you call it netconfigipparams is creating the object..

this version only processing a network with default =1 and does nothing if it doesn't fine one..

it works on my 4.01.b box and both my 6.2 boxes and I confirmed on one by removing /sbin/dhclient and rebooting after running it that the network still works and MRV works..

so this does seem to be a workaround to get rid of dhcp etc. etc.
wonder if a phone call will wipe it out.. hopefully not..

thanks everyone for your help.

tyke

05-12-2005, 08:15 PM

...wonder if a phone call will wipe it out.. hopefully not..

After a phone call I had to re-run set_mrv_name_67.tcl for MRV to work again (didn't have to reboot to get it working). Networking stuff stayed. Calling home is not a great idea.

lgkahn

05-13-2005, 09:28 AM

well it doesn't hurt to call home once in a while even you have to rerun set name.. because then you can order ppv with the remote...
as long as they don't get pissed we are running mrv hmmm..

other side note even for the 6.2 boxes working there is really nothing in the system info to indicate mrv is working like the stuff in 4.0.1b.. no name of the tivo etc. etc.

alldeadhomiez

05-13-2005, 12:31 PM

well it doesn't hurt to call home once in a while even you have to rerun set name.. because then you can order ppv with the remote...

This has nothing to do with the TiVo call. The two calls can be blocked and unblocked separately.

jasch

05-13-2005, 12:34 PM

This has nothing to do with the TiVo call. The two calls can be blocked and unblocked separately.

HMm. As far as I know, you can only block TiVo calling the motherboard (by blocking TiVO's IP). How do you block DTV calls? (IIRC they are not made through the internet)

lgkahn

05-13-2005, 12:56 PM

yes I would like to know also is there a differnt ip for direct tv calls through the
net or is it still through the phone line.. as I do have a line plugged into one of the boxes to run elseed and caller id..

thanks

alldeadhomiez

05-13-2005, 05:10 PM

How do you block DTV calls? (IIRC they are not made through the internet)

Somewhere between dssapp and the modem...

There are a few different ways of monitoring the traffic on these calls, but it likely involves writing code.

nova1

05-13-2005, 06:51 PM

After a phone call I had to re-run set_mrv_name_67.tcl for MRV to work again (didn't have to reboot to get it working). Networking stuff stayed. Calling home is not a great idea.
Most likely the /State/Keyring was updated. You could try an ADD/DROP patch.

Homer S

05-19-2005, 01:38 AM

well it doesn't hurt to call home once in a while even you have to rerun set name..

Is there a script which either runs the call or runs after the call to which the set_name refresh could be added? I know this could be cron'd but it seems like it would be better to stick it where it would get run in the normal course of the call without adding any overhead.

Just a thought...

Homer Out

alldeadhomiez

05-19-2005, 03:33 AM

Um... why are we allowing hacked, superpatched DTiVo units to phone home to TiVo?

Have we forgotten about why we should not draw undue attention to our modifications?

Homer S

05-19-2005, 08:54 AM

ADH,

Hmmm... good point I suppose. I had a little tickle that they might become cranky if I was subscribed but it never phones in...

Homer Out

P.S. Fixed the fakecall.tcl from your AOW per the collected tips thread, made a fakecall.sh and added to rc.sysinit.author per one of your helpful posts. Now it will be very quiet. Thanks!

Gunnyman

05-20-2005, 05:34 PM

is it possible to add SSID for wireless setups to this script?
I have the following from my functional HDVR2 that I upgraded from 4.01b with slices
NetConfigWirelessParams 91512/12 { DenyUnencrypted = 1 SsId = miniap }
6.2 doesn't seem to include hunting for Wireless access points but the settings migrate over from 4.01b.

7.1

05-20-2005, 06:08 PM

is it possible to add SSID for wireless setups to this script?
I have the following from my functional HDVR2 that I upgraded from 4.01b with slices
NetConfigWirelessParams 91512/12 { DenyUnencrypted = 1 SsId = miniap }To make use of this info, we need the MFS path. Is this referenced from the NetConfig object under /State/Network, or somewhere else? A recursive dump starting from /State/Network would probably provide the necessary info (echo "dumpobj -depth 10 /State/Network/*" | tivosh).

Gunnyman

05-20-2005, 06:17 PM

ask and ye shall receive:

NetConfig 91512/10 { Default = 1 HardwareAddress = 0 48 189 157 232 231
IndexPath = /State/Network/005:91512
IpParams = 91512/11
NetConfigIpParams 91512/11 { }
NetworkMedium = 5
Version = 2
WirelessParams = 91512/12
NetConfigWirelessParams 91512/12
{ DenyUnencrypted = 1
SsId = miniap } }[/

tyke

05-20-2005, 11:55 PM

A newbie try at adding wireless stuff.
Change FSID to match yours
Change SSID to match yours
Not sure about the NetworkMedium, yours is listed as 5, mine is 4 on a wired interface. Not sure if that needs to be changed.
Copy to a .tcl and run
#!/tvbin/tivosh

set db [dbopen]

RetryTransaction {

set netcfg [db $db openid changeme_to_fsidofstate_network]
set wirelessparam [db $db createsub NetConfigWirelessParams $netcfg]
dbobj $wirelessparam set DenyUnencrypted 1
dbobj $wirelessparam set SsId changeme_tossid
dbobj $netcfg set WirelessParams $wirelessparam
}

rbautch

05-21-2005, 12:13 AM

Thought I'd also include a dump from my system, which is secured with WEP. If lgkhan's script is modified to add wireless SSID, I suggest WEP is also included. These additions would be much appreciated. Also note that ThinkDiff kindly created a working script to set SSID, which is posted here (http://www.dealdatabase.com/forum/showpost.php?p=223460&postcount=18).

NetConfig 8004/10 {
Default = 1
HardwareAddress = 0 6 37 166 216 192
IndexPath = /State/Network/005:8004
IpParams = 8004/17
NetConfigIpParams 8004/17 {
AutoConfigEnabled = 0
DnsServers = 192.168.1.1
GatewayAddress = 192.168.1.1
HostAddress = 192.168.1.111
SubnetMask = 255.255.255.0
}
NetworkMedium = 5
Version = 6
WirelessParams = 8004/18
NetConfigWirelessParams 8004/18 {
DenyUnencrypted = 1
SsId = Bautch2
WepKey = 20 -1279806544 -1212960592 -624709453 -1008942118 -591144
230
}
}

Homer S

05-25-2005, 12:45 AM

Fixed the fakecall.tcl from your AOW per the collected tips thread, made a fakecall.sh and added to rc.sysinit.author per one of your helpful posts.

Rats,

I checked today and I messed things up. My fakecall.sh file seems not to be working.

Here is the file and the error:
bash-2.02# more fakecall.sh
while true; do
{
date>> /var/log/hacklogs
/tivo-bin/fakecall.tcl
sleep 82800
}
donebash-2.02# fakecall.sh
/tivo-bin/fakecall.sh: line 7: syntax error near unexpected token `done'
/tivo-bin/fakecall.sh: line 7: `done'

Thanks for any help,
Homer Out

millercentral

05-27-2005, 06:28 PM

To add some confusion to this...

My two HDVR2 boxes (Bedroom, and FamilyRoom) are closely configured, but not identical. MRV success is mixed:

On BEDROOM:
- 4.0 system slice upgraded to 6.2
- DHCP client enabled, no network interface or driver commands in the startup script (DHCP server configured to assign bedroom MAC to ip 192.168.2.11)
- Network had previously been configured manually in 4.0. IPParams object exists, as follows:
NetConfigIpParams 2203724/16 {
AutoConfigEnabled = 0
DnsServers = 192.168.2.1
GatewayAddress = 192.168.2.1
HostAddress = 192.168.2.11
SubnetMask = 255.255.255.0
}
- tvlog has entries for adding broadcast interface as 192.168.2.255 and entries for adding the FamilyRoom client, and Desktop photo/music server
- Incoming MRV work correctly (that is FamilyRoom shows up in Now Showing and transfers from FamilyRoom to bedroom work as expected).
- System is listening on both 2190 and 2191

On FAMILYROOM:
- New 6.2 install from image
- DHCP client enabled, no network interface or driver commands in the startup scripts (DHCP server assignes its MAC address to 192.168.2.10)
- No IPParams object in the MFS
- tvlog has entries for adding broadcast interface (255.255.255.255) and entries for adding the desktop photo/music server, but NOT for adding the Bedroom client
- System is listening on both 2190 and 2191
- Incoming MRV does NOT work (ie, Bedroom tivo does not show up on Now Playing list), but photo/music browsing does work.

Also, the desktop server sees both units named correctly, so I believe the set_name... script worked correctly on each.

So which side of the equation is keeping Bedroom > FamilyRoom MRV from working (when FamilyRoom > Bedroom does work). My hunch is it is a problem with the Bedroom tivo as a result of the manual configuration from 4.0, but that would conflict with what others have said here.

Any suggestions on what I should try? I'm considering one or more of the following:
- rubbishing the IPParams object in the Bedroom tivo
- adding an IPParams object to FamilyRoom
- investigate if the slight different broadcast masks (192.168.2.255 vs. 255.255.255.255 could be causing the issue)

Any insights would be welcome. Thanks.

EDIT: Studying the logs more closely, I did notice one concerning entry in tvlog:
1011:May 28 04:01:50 (none) KnownHostListener[179]: This is a release version of KnownHost. Systems advertising TvBus-based services will be ignored unless they are included in a valid transfer certificate issued by the TiVo Service.
Is this normal?

EDIT2: I modified the network settings script to change the AutoConfigure option to 1 (thus enabling DHCP to work) -- this fixed everything. Setting my router to issue static IPs to the tivos is much easier then figuring out a non-DHCP solution on the box... :)

playtowin

05-28-2005, 06:28 PM

The discussions I have seen indicate two possible ways to get this going.

1) Run netconfig.tcl to set network parameters
2) Set networks parameters early in test.conf using ifconfig

I've seen posts indicating that netconfig.tcl works but nothing specific on test.conf. Has anyone had success getting MRV to work reliably when setting up network parameters in test.conf?

If netconfig.tcl is the only reliable way to get it going, do you run it once, or every time at bootup and do you have to use ifconfig as well?

cheer

05-29-2005, 02:52 AM

I've seen posts indicating that netconfig.tcl works but nothing specific on test.conf. Has anyone had success getting MRV to work reliably when setting up network parameters in test.conf?

If netconfig.tcl is the only reliable way to get it going, do you run it once, or every time at bootup and do you have to use ifconfig as well?
I just did my very first 3.1.1e->6.2 slice upgrade and I can confirm that netconfig.tcl works fine. (I'm not using wireless so YMMV.)

Run it once and it sets everything in MFS. Shouldn't have to run it again. And yes you should remove the ifconfig statements you used to have in rc.sysinit.author (or wherever).

--chris

EvilJack

05-29-2005, 08:50 AM

I think it's agreed that the 6.2 DirectTivo with HMO/MRV
patch should not use the phone to dial in... what about
TCP Ports? Should be block any TCP Ports makeing outgoing
connects to the Tivo Mothership?

jack

cheer

05-29-2005, 12:24 PM

Just do the old "route" fix:

route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0

This redirects the routes for the mothership to the Tivo's own loopback interface, essentially blackholing the mothership calls.

Depending on your software version you may need to configure a loopback interface on your Tivo:

ifconfig lo 127.0.0.1 broadcast 0.0.0.0 netmask 255.0.0.0 up

jonbig

05-30-2005, 12:09 AM

I just did my very first 3.1.1e->6.2 slice upgrade and I can confirm that netconfig.tcl works fine. (I'm not using wireless so YMMV.)

Run it once and it sets everything in MFS. Shouldn't have to run it again. And yes you should remove the ifconfig statements you used to have in rc.sysinit.author (or wherever).
--chris

Let me amplify on this. If you leave the ifconfig in your rc.sysinit, then the information that netconfig.tcl places into the MFS database will be erased and MRV won't work. You'll see an entry in the tverr log saying that sending a beacon packet failed with an error.

So, for 6.2, do run netconfig.tcl, and don't set ifconfig in your rc.sysinit.author (or rc.runfirst if you are using AlphaWolf's setup).

I found this out the hard way.

EvilJack

05-30-2005, 11:48 AM

Just do the old "route" fix:

route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0

This redirects the routes for the mothership to the Tivo's own loopback interface, essentially blackholing the mothership calls.

Does this disable the NTP updates to get your system time
updated? If not... what servers does tivo use... or how does
it update it's time if it doesn't use NTP?

jack

cheer

05-30-2005, 12:16 PM

Does this disable the NTP updates to get your system time
updated? If not... what servers does tivo use... or how does
it update it's time if it doesn't use NTP?

jack
I'm pretty sure the DTivos get the time from the bird. No idea about SA Tivos.

lgkahn

05-30-2005, 08:17 PM

Let me amplify on this. If you leave the ifconfig in your rc.sysinit, then the information that netconfig.tcl places into the MFS database will be erased and MRV won't work. You'll see an entry in the tverr log saying that sending a beacon packet failed with an error.

no it doesn't erase it.. you may get two ipaddress sets on your interface and if they are conflicting/different you may have issues depending on what your default g/w is etc.,

but I have a box with it still in my rc.sysinit.author and no problesm..
network interfaces can have multiple ip addresses.

also ifconfig doesn't touch the mfs database..

7.1

05-30-2005, 09:47 PM

no it doesn't erase it.. you may get two ipaddress sets on your interface and if they are conflicting/different you may have issues depending on what your default g/w is etc.,
...
network interfaces can have multiple ip addresses.Just in case this confused any one: if you set an ip address and netmask on eth0 using ifconfig you will be replacing any previously set ip address, not adding another one. It is possible to assign multiple ip addresses to a physical interface in linux using ip aliases. For example, "ifconfig eth0:1 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx" sets up a virtual sub interface of eth0 with a different IP.

jonbig

05-30-2005, 10:58 PM

no it doesn't erase it.. you may get two ipaddress sets on your interface and if they are conflicting/different you may have issues depending on what your default g/w is etc.,

but I have a box with it still in my rc.sysinit.author and no problesm..
network interfaces can have multiple ip addresses.

also ifconfig doesn't touch the mfs database..

I hate to differ, but it did in my case, with both of my HDVR2s, one upgraded from 3.1.1c and the other installed from the small 6.x image. I verified it twice: I'd run netconfig.tcl, verify with tivowebplus that the MFS settings were there, then reboot the box. On reboot the settings were gone, and MRV wouldn't work.

I don't thing that ifconfig wrote to the MFS database, but I do think some other TiVo process saw that eth0 was already configured and erased the entry in the MFS database during the boot process.

oakwcj

05-31-2005, 11:14 AM

I can confirm that the ip settings in MFS/State/Network will be erased on boot in some situations, but having ifconfig statements in rc.sysinit.author isn't one of them. In my case, at least, the cause was loading the usb drivers in test.conf. Once I took out those insmod lines, the ip settings were persistent and MRV worked.

EvilJack

05-31-2005, 02:37 PM

Just want to check... does this thread have any relevance
to a 6.2 unit that superpatch 67-all patch installed?
I've seen a couple of people say that that is what they
have installed....

I have two 6.2 units with the superpatch installed and
my stuff works fine with nothing but the superpatch
( and the set name tcl script ). What's the purpose of this
netconfig.tcl script as far as a 6.2 unit is concerned?

jack

rbautch

05-31-2005, 02:39 PM

If you upgraded from 4.0 with slices, you won't have any of these issues. It's all explained in part 3b of the first post in the collected info and tips thread.

shawn

06-01-2005, 03:29 PM

Some may want to just look into getting a pair of these.
(NETGEAR XE102US Wall-Plugged Ethernet Bridge)
Keep wired speeds no long cables needed no wireless config needed.

rbautch

06-01-2005, 03:37 PM

Interesting, but at $45 each (http://www.newegg.com/Product/Product.asp?Item=N82E16833122063) these are not a cheap alternative to buying a single $25 wireless usb adapter from Ebay, nor do they address the network configuration issue on which this thread is based.

shawn

06-01-2005, 04:59 PM

I was only posting for those interested in eliminating the config headache and to get wired speeds. These deals eliminate the distance reason for going with Wireless.

Jamie

06-01-2005, 05:54 PM

I was only posting for those interested in eliminating the config headache and to get wired speeds. These deals eliminate the distance reason for going with Wireless.The ethernet side is 10mbps, so the speed isn't really competitive with "wired speeds". I would guess it's pretty similar to 802.11b, although it might be a little better.

Homer S

06-01-2005, 10:20 PM

Nevermind... tried dos2unix and voila!

Homer Out

lgkahn

06-02-2005, 02:03 PM

I have two 6.2 units with the superpatch installed and
my stuff works fine with nothing but the superpatch
( and the set name tcl script ). What's the purpose of this
netconfig.tcl script as far as a 6.2 unit is concerned?

netconfig is for 6.2 boxes that don't have the mfs information becuase they are clean installs or upgrades from 3.1.x

and also are not using dhcp..

for these boxes mrv doesn;t work correctly unless you bring up the eth0 earlier in the boot cycle than in the rc.sysinit.author

on way is to run netconfig.tcl once to config the correct mfs stuff with your networking as if you configured the networking through the tivo networking menus which are non-existant in 6.2

drnull

06-03-2005, 12:47 AM

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.

Thanks for that. I'm having a problem that is slightly different from what I've seen described by others. Been looking at it off and on for the past week with no real success. I cannot access music & photos. I don't know about mrv, as I have only one tivo (and the .idl files changed between 4.0 & 6.2 so I haven't had time to get another "server" up and running...)

First off, background:
HDVR2, originally hacked at 3.1.1c, then sleepered to 4.0 with a fresh mfs restore (about a year ago), unsleepered, killhdinitrd'd, upgraded via slices to 6.2. superpatch-67all-NutKase-1.0.tcl, set_mrv_name_67.tcl ran successfully. The network settings had been set in 4.0.

So I know the tivo and the desktop are both broadcasting: .200 is tivo, .202 is desktop.

> tcpdump/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
20:06:54.107143 IP 192.168.1.200.2190 > 192.168.1.255.2190: UDP, length: 160
20:07:14.392380 IP 192.168.1.202.2712 > 192.168.1.255.2190: UDP, length: 129
20:07:54.167566 IP 192.168.1.200.2190 > 192.168.1.255.2190: UDP, length: 160
20:07:59.421498 IP 192.168.1.202.2714 > 192.168.1.255.2190: UDP, length: 129

My tvlog output, though, is slightly different.
Jun 3 01:34:09 (none) NetworkInterface[161]: If0: Startup 00:10:60:24:53:3e <Linksys USB200M> medium 4
Jun 3 01:34:09 (none) NetworkInterface[161]: If0: Setting IPv4 params
Jun 3 01:34:09 (none) LinuxNetworkInterface[161]: If0: Manual config
Jun 3 01:34:10 (none) NetworkInterface[161]: If0: Done setting IPv4 params

So we know that tivo sees the proper manual network config, that's good, but here we differ:
Jun 3 01:34:18 (none) TmkInit[187]: Starting program KnownHostComponent
Jun 3 01:34:18 (none) TmkEnvVar[187]: TV_LAUNCHER_APPLICATION_ID = 0
Jun 3 01:34:18 (none) TmkEnvVar[187]: TV_LAUNCHER_PROGRAM_ID = KnownHostService
Jun 3 01:34:18 (none) KnownHostListener[187]: This is a release version of KnownHost. Systems advertising TvBus-based services will be ignored unless they are included in a valid transfer certificate issued by the TiVo Service.
Jun 3 01:34:18 (none) TmkInit[187]: 0.382 seconds: TOTAL for KnownHostComponent
Jun 3 01:34:18 (none) KnownHostListener[187]: Adding broadcast interface 0 with address 192.168.1.255
Jun 3 01:34:18 (none) TvLauncher[99]: FINISH Start/KnownHostService: 0.773 seconds
Jun 3 01:34:19 (none) TmkInit[194]: Starting program NetworkVideoService
Jun 3 01:34:19 (none) TmkEnvVar[194]: TV_LAUNCHER_APPLICATION_ID = 0
Jun 3 01:34:19 (none) TmkEnvVar[194]: TV_LAUNCHER_PROGRAM_ID = NetworkVideoService
Jun 3 01:34:19 (none) dbcache[194]: Creating dbcache in program NetworkVideoService, size = 10
Jun 3 01:34:19 (none) DbQueryCacheManager[194]: Creating DbQueryCacheManager in program NetworkVideoService
Jun 3 01:34:24 (none) TvPassKeyCache[182]: Transfer certificate 1 validated and cached
Jun 3 01:34:24 (none) KnownHostListener[187]: In-home viewing enabled
Jun 3 01:34:31 (none) TmkInit[194]: 12.160 seconds: start TvCryptoManager
Jun 3 01:34:31 (none) TmkInit[194]: 12.529 seconds: TOTAL for NetworkVideoService

I get a broadcast interface message for eth0, but no TiVoConnect messages anywhere. Also, there are no messages for KnownHost new entries when the heartbeat broadcasts come in, and /State/KnownHost is empty (of course).

/State/Network gives me the following:
% mls /State/Network
Directory of /State/Network starting at ''

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
004:580909 tyDb 580909 09/16/04 17:22 212

% dumpobj 580909
NetConfig 580909/10 {
Default = 1
HardwareAddress = 0 16 96 36 83 62
IndexPath = /State/Network/004:580909
IpParams = 580909/11
NetworkMedium = 4
Version = 2
}
% dumpobj 580909/11
NetConfigIpParams 580909/11 {
AutoConfigEnabled = 0
DnsServers = 0.0.0.0
GatewayAddress = 192.168.1.1
HostAddress = 192.168.1.200
SubnetMask = 255.255.255.0
}

For completeness, I'm running JavaHMO 2.4. Any pointers as to where to look to find out why m&p aren't working would be much appreciated. I've looked at ethereal captures but they don't seem to tell me much. Just the tivo and JavaHMO going into rapid discovery mode, sending beacons back and forth.

EDIT: Right, and no errors in tverr or kernel or messages, etc.

drnull

06-04-2005, 01:20 AM

I'm having a problem that is slightly different from what I've seen described by others.

Heh, sorry about that... my problem turned out to be a JavaHMO problem. I'm still not sure exactly what the problem was, but I reinstalled JavaHMO and it's all better now. I was just assuming the problem was on the tivo side, since I was getting different output from what 7.1 got, but that would have more to do with the software version, apparently.

Homer S

06-10-2005, 10:37 AM

Ok,

Spoke too soon... Fakecall appears to be working as I have it writing some status lines to a log file. The faked calls seem to be happening daily (86400 seconds). I checked and the dtivo's names have reset to the 4 letter codes and the recordings on the remote dtivo are no longer available. There is a listing, maybe an old one? I checked the keys in system information, both seem to be valid and state expiry sometime in November.

I think this is because *something* has reset the network names. How do I troubleshoot this and more importantly, what is the "approved" way to stop it?

Thanks,
Homer Out

DrTusk

06-10-2005, 01:18 PM

Is there any reason to believe running netconfig.tcl more than once would not work? I recently changed routers and wanted to change my IP address. I ran netconfig.tcl to update to the new IP but now networking doesn't work. I pulled the drive and tweaked the script to re-enable AutoConfiguration and added a line in test.conf to run it, but that doesn't seem to help. I'm working on getting a serial cable, but in the meantime, any thoughts? It's a SD-DVR40 6.2 if that matters. Thanks.

shawn

06-10-2005, 01:20 PM

If you are wired using DHCP boot it with no adaptor then reboot it with the adaptor.
Workes for me. Seems a boot with no adaptor clears settings.

lgkahn

06-10-2005, 01:37 PM

nope I have run it multiple times.. but if you still have differnt info in the ifconfig line somewhere that conflicts with the settings in the mfs database this could be your problem

DrTusk

06-10-2005, 02:04 PM

something strange is going on heh. pulling the network adapter trick worked though and I can telnet again, thanks! it seems like it's still hard-coded to a certain IP address. my router doesn't show the tivo as connected via dhcp. ah well, I'll figure something out, thanks.

RYSmith315

06-10-2005, 07:47 PM

NetConfig 8004/10 {
Default = 1
HardwareAddress = 0 6 37 166 216 192
IndexPath = /State/Network/005:8004
IpParams = 8004/17
NetConfigIpParams 8004/17 {
AutoConfigEnabled = 0
DnsServers = 192.168.1.1
GatewayAddress = 192.168.1.1
HostAddress = 192.168.1.111
SubnetMask = 255.255.255.0
}
NetworkMedium = 5
Version = 6
WirelessParams = 8004/18
NetConfigWirelessParams 8004/18 {
DenyUnencrypted = 1
SsId = Bautch2
WepKey = 20 -1279806544 -1212960592 -624709453 -1008942118 -591144
230
}
}

Could you post the HEX values of your wep key to validate how the keys are stored? I've modified netconfig.tcl to add the wireless params but I need to add wep support.

I've included a modified version of netconfig.tcl that will add your SSID if specified. After running the command ou need to either reboot or kick hotplug to pick up the new parameters.

To kick hotplug type this:
ACTION=register INTERFACE=wlan0 /sbin/hotplug net

...be sure to change INTERFACE to whatever you nic came up as.

After doing that, MRV just started working.....as if by magic!

rbautch

06-11-2005, 01:50 AM

73696D706C

I don't think this is a trivial problem. I updated this post (http://www.dealdatabase.com/forum/showpost.php?p=224965&postcount=18) just now to point you in the right direction. Good luck.

wuf68

06-17-2005, 01:10 PM

I am a newbie but have learned quite a bit thanks to your excellent work....I have instaled Superpatch 67 All to my 6.2 Dtivo and have everything working I could ever want... (For now) However, every morning I lose networking, manually rebooting the Tivo regains it..... Is this because of a phone home issue or does anybody have any thoughts.... I don't want to attempt to fix the problem w/ out some clue of what is causing it..... Thanks again for your great work

PlainBill

06-18-2005, 07:42 AM

cdoug512

06-19-2005, 11:44 PM

Trying to get MRV working, too. I got the error from lgkahn's netconfig-1.tcl that reads,
"Error: Syntax is netconfig ipadress subnetmask defaultgw dns-server!"

What does it tell me is wrong? BTW, this is on a previously unhacked HDVR2 that was upgraded by DTivo to 6.2 and then hacked. HMO (Music/Photos) work fine.

rberning

06-20-2005, 01:42 AM

RYSmith315

06-20-2005, 06:01 PM

I hate to say it but your right...... You need to get wireless working via the wlanctl-ng scripts floating around this fourm first.

After you get wireless working and ftp installed, then transfer the netconfig.tcl I posted a few messages back and setup you SSID with the normal IP parms. Another option is to install TivoWebPlus, after wirless is working, and grab netconfig.itcl from the "Files" forum and put it into TivoWeb's module directory and reload.

You may ask,"Why do I need netconfig.tcl if I can get wireless working without modifying MFS?". Good question.... If you use ifconfig/wlanctl to configure your wireless card TiVo will know nothing about it and MRV will not work, Music & Photo will still work fine. After you have properly configured you network settings in MFS, TiVo will add a "TiVo Beacon" broadcast to that adapter, allowing MRV to work (assuming you have also applied super patch and set_mrv_name_67.tcl)

Good Luck!

EvilJack

06-22-2005, 09:29 AM

Are there any log entries that you can use to figure out how
long a MRV transfer takes?

i.e if I transfer a show from tivoa to tivob and transfer a
show from tivob to tivoc are there log entries on the tivos
that I can use to figure out how long the show took to
transfer from a-to-b and from b-to-c?

Thanks - jack

Jamie

06-22-2005, 11:34 AM

Are there any log entries that you can use to figure out how
long a MRV transfer takes? Look in /var/log/tvlog on the sending tivo.

EvilJack

06-22-2005, 01:10 PM

moved to the bragging thread. Please delete this post.

jack

Jamie

06-22-2005, 01:21 PM

If I sould use a different thread... let me know. I don't think it belongs here. This (http://www.dealdatabase.com/forum/showthread.php?t=39328) thread seems to be the defacto standard place to brag and moan about S2 network performance.

mk1277

06-24-2005, 11:53 AM

Maybe I missed something, but how does the netconfig.tcl get applied to my wireless adapter?

I have a HDVR2 running 6.2 from the 62small.mfs image. Have successfully set up HMO & MRV with my wired network adapter thanks to lgkahn’s netconfig.tcl, but want to get my wireless working since my other HDVR2 does not have a network line near it. I have been playing with this one to try to get it working first before I convert the other.

I have run the latest netconfig.tcl and also Thinkdiff set SSID script. They work great but it only applies the changes to my wired network adapter, See below

bash-2.02# echo "dumpobj -depth 10 /State/Network/*" | tivosh
NetConfig 80531/10 {
Default = 1
HardwareAddress = 0 224 76 0 20 238
IndexPath = /State/Network/004:80531
IpParams = 80531/11
NetConfigIpParams 80531/11 {
AutoConfigEnabled = 0
DnsServers = 68.94.156.1
GatewayAddress = 192.168.1.1
HostAddress = 192.168.1.90
SubnetMask = 255.255.255.0
}
NetworkMedium = 4
Version = 12
WirelessParams = 80531/20
NetConfigWirelessParams 80531/20 {
DenyUnencrypted = 1
SsId = rob
}
}

I plug in my wireless adapter and it does not work. I know I need to run netconfig.tcl on my wireless adapter, but how do I do that when I cannot connect to run it? When I run mfs_ls /State/Network I only get one ID.

bash-2.02# mfs_ls /State/Network
dir: fsid=3982 count=1
fsid type name
-----------------------------------
80531 tyDb 004:80531

Shouldn't my wireless adapter show up as another fsid?

I hate to say it but your right...... You need to get wireless working via the wlanctl-ng scripts floating around this fourm first.

OK. Please forgive me if this is a noob post. I'm familiar with Linux (maybe not to the extent of others here) and can find my way around. I was having an issue similar to the parent poster (rberning).

I have a virgin 6.2 that I hacked for HMO/MRV. Everything went flawless. I used a wired USB200M for all my FTP and Telnet work. I've been trying to get a MA111 v1 up and running. I read the Prism thread and other 6.2 threads and came up with the following:

The wlan-ng tpm file does not work with 6.2. A manual process of extracting and adding the files is required.
Prism modules (and backported USB modules) need to be added to the Tivo
Configure wireless settings (wlan.config, wlancfg-DEFAULT, etc.)
Run netconfig.tcl once wireless is running.

Everything went very well. The modules load every time I insert the MA111. However, I could only get the wlan0 interface running by manually calling wlan.init. Once this was called, ifconfig would show the interface along with eth0 and lo.

However, many times, the USB200M would take the IP that was set in /etc/wlan/network for wlan0 My router showed the MAC of the USB200M with the IP set for wlan0 attached to the network and the USB200M replied to pings at that IP. Also, the MA111 settings didn't seem to take the SSID value even though it was correctly set in the wlan files (I did a wlancfg show wlan0).

I was able to get the MA111 to work by running the wlan.init script a couple of times (it would finally grab the SSID) and then removing the USB200M. It was very late last night, so I was a bit punchy by the end. Since I had a working interface, I ran netconfig.tcl on it and rebooted. Now neither interface will get an IP even though they are active. I'm guessing that this is a MLS problem even though the settings I passed were correct. Can anyone advise? Thanks in advance.

RYSmith315

06-25-2005, 12:32 PM

Did you run the "netconfig.tcl" with wireless support? (posted a few messages back in this thread)

Another alternative is to use the netconfig.itcl TiVoWebPlus module posted in the files section. Once you have setup the ip address and SSID you may still have to run the wlan.init script to run the firmware update contained in shared.prisim2.

The next question is, is the MA111 adapter you are using a MA111v2 (you have to search the box to figure it out). If so, they do not work. The chipset in the v2 is SiS162u and not Prisim.

....last but not least. Are you trying to run multiple interfaces (wired and wireless)? If so, the scripts that have been posted wil likely screw up your settings.

mk1277

06-25-2005, 05:59 PM

RYSMith:
Thanks for the reply. I managed to get one of my adapters working this morning. I do have a MA11 v1. I made very sure I did my homework before buying an adapter :) I removed all the modules, wlan files, and sbin stuff and started from scratch. I followed a short list that was posted on the other forum which was slightly different from my first attempt. There were a couple of original files that needed to be placed back on the Tivo. I kept everything simple and let the adapter connect to any SSID in range. I re-ran the netconfig.tcl script without any SSID and rebooted. It works great now.

I have two other tivos to set this up on and am on my second one now. The prism modules load just fine, but it would seem that I need to run netconfig.tcl and wlan.init again as the adapter doesn't seem to be reading the wlancfg-DEFAULT. I got myself a serial cable, so that makes life a LOT easier. It also solves the problem of trying to telnet into a wired adapter to setup my wireless adapter. :)

Incidentally, I was wondering about the network file in /etc/wlan. It has some ifconfig statements for wlan0. Once the netconfig.tcl script is run, it would seem that the ifconfig statements are ignored/replaced by the settings in mfs, is that correct? Should I comment out or rename the file? Just wondering because I have a different IP set in my /etc/wlan/network file from the netconfig.tcl script just for troubleshooting. I wanted to see what IP was getting assigned to the adapter. (FYI - I also did rename /sbin/dhclient so that I'd only use a statically assigned address).

Thanks again. I'm almost there. :D

RYSmith315

06-26-2005, 09:23 PM

Your very close.....

Are you planning on using MRV? If so, you will need to get your SSID into the /State/Network settings. If you don't care about MRV you don't need to mess with netconfig.tcl. However, Music&Photos will still work.

The "/etc/wlan/network" script can be commented out since the Tivo software will configure the adapter if all the /State/Network settings are right.

The DHCP change is not necessary if you set the AutoConfigEnabled parameter to 0 (found on the NetConfigIpParams page)

Have you installed TiVoWebPlus yet? If so the modules posted in the "Files" discussion group will make this process pretty easy.

imaloserbaby

06-27-2005, 11:27 PM

EDIT: I finally did something with my old script. I took RYSmith315's script with ssid support (which was based on lgkhan's script) and merely added the NetworkMedium flags to that. Since the original script worked, I'm hoping this will too, I'll try and test it tonight. (My changes are deliberately minimal).

EDIT: I also modified it to fix a bug when the ssid was not specified, which is assumed to be wired, the params are now worked out / processed correctly.

As stated in RYSmith315's script, the syntax is:

netconfig ipadress subnetmask defaultgw dns-server [SSID]

E.g. netconfig-1.2.tcl 192.168.0.100 255.255.255.0 0.0.0.0 0.0.0.0 default

I couldn't see anywhere else if anyone had put this in, so apologies if they had. This should help for now at least.

----

I left the old script there purely for interest, but don't recommend it's usage.

(old info removed)

imaloserbaby

06-27-2005, 11:47 PM

Maybe I missed something, but how does the netconfig.tcl get applied to my wireless adapter?

<snip>
NetworkMedium = 4
<snip>

That's why I found I had to alter the script, because NetworkMedium = 4 means wired, whereas NetworkMedium = 5 mean wireless. I've attached my alterations above ^^.

RYSmith315

06-28-2005, 12:46 AM

UPDATE: the itcl configs in the Files section work great, but it's chicken and egg since you need the network running first before getting to TivoWeb.

I added wireless support to netconfig.tcl a few pages back....also, an awful hack and I left out NetworkMedium. I thought the TiVoWeb module would be helpful for those who have had network support working long before the Tivo app actually did anyting with it but now wanted to add MRV and/or let Tivo control setting up the adapter. At any rate I'm glad to see people giving back and supporting the community. Next, somebody needs to crack the WEP key mystery. :)

imaloserbaby

06-28-2005, 05:22 PM

Next, somebody needs to crack the WEP key mystery. :)

Or better yet unhide the hidden network config menus in 6.2 - assuming they did something similar to HMO in 6.2 to "remove it" (ie. just hidden, which you'd certainly hope). Alas my reverse engineering skills are not great esp. w.r.t. tivoapp which is a large beast indeed.

mk1277

06-29-2005, 06:52 PM

I just wanted to say thanks to all on this forum. I figured out over the weekend the missing piece. I didn't have the switch in the script that enabled wireless (i.e. status 5 instead of 4). I ran that with the SSID & FSID and everything fired up. MRV now works! :) It would appear based on the console output I was viewing, that the Tivo doesn't know to read the /etc/wlan directory and wlancfg-DEFAULT file until that switch is made. This may be obvious to others, but I missed it. :o

It took some head scratching and some re-reading of the forum, but it was worth it. By the time I figured all this out on my first two Tivos, I was a pro and had the third Tivo hacked in about 10 mins (including the reboots). Wireless B may not be the fastest thing in the world, but I'm able to MRV a show in approx. real time. Good luck to the others trying to enable wireless.

cyklfreak

07-01-2005, 06:02 PM

never mind i got it working!!!!

Stephanie

07-14-2005, 07:17 PM

Sorry for the long quotation. FWIW, my 4.01b machines could not interact with the 6.2 machines using MRV. Once I set the 4.01b machines to use DHCP instead of static IPs, (the 6.2's were already using DHCP) everything was fine for HMO and MRV. They are all now fully working bi-directionally w/o issues.

-- Steph

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...

captain_video

07-22-2005, 09:56 AM

I finally got around to upgrading a couple of my S2 DTivos with 6.2 and I'd like to add my 2 cents to some of the discussions here. I started with the slice upgrade on a 4.x box but somehow it ended up in a reboot loop so I tried a different approach. I grabbed one of my 40GB stock DTivo drives left over from a previous upgrade and installed Alphawolf's minimal 6.2 image and hacked the whole thing from scratch.

I got everything set up and working and the 6.2 box recognized my other 4.x box with MRV working between them. Once everything was working as it should I made a backup image of the hacked 40GB drive and restored it to the two drives in the 4.x box I previously hosed with the slice upgrade. I got that box working fine but it had the error #51 so I ended up doing a Clear & Delete Everything. Needless to say it hosed up my ethernet settings in mfs from the netconfig.tcl script so I tried another approach. I reinstalled the hacked 40GB drive and ran the 51killer.tcl script then pulled the drive before it rebooted. I made another backup of this drive and restored the backup to the two drives mentioned previously. This retained the network settings in mfs and got rid of the error #51 at the same time.

I then restored the hacked image to my other 4.x box after transferring all its shows to the newly hacked 6.2 box via MRV. I needed to set up a different IP address on the 2nd box so I reran the netconfig.tcl script. When I tried connecting to the box I was unable to use the new IP address so I gave the original address a shot and it still worked. As it turned out, I had uploaded a preconfigured rc.sysinit.author file from an older S2 DTivo and it had the ifconfig statement in it with the original IP address from the other box. The new IP address was being written in mfs but was being overridden by the rc.sysinit.author file. I confirmed this by re-running the netconfig.tcl script and it stated it was changing the address from the new address I had previously set to the same address I was again specifying. Editing the rc.sysinit.author file changed the address over to the new IP.

I also tried setting up crond but when I added the statement to rc.sysinit.aithor and rebooted, I lost MRV capability (i.e., the other Tivos with MRV were not showing up in the Now Playing list). I commented out the line for crond and rebooted and I was back in business.

I wanted to mention the IP address conflict between netconfig.tcl and rc.sysinit.author because it had been discussed in some previous posts. Having the two set up in the same machine will indeed cause a conflict if they're different. However, removing the info from mfs, as I did with the C&DE, will also cause you to lose connectivity as the rc.sysinit.author setting is apparently not taking over. I haven't tried to comment out the ifconfig settings in rc.sysinit.author yet but I suspect it will have no affect on the current settings if I do.

P.S. - I just revised my rc.sysinit.author file to comment out the ifconfig statement and reinstated the line to call crond. MRV is now working. On another note, I can't seem to get a bash prompt via serial connection although I was getting serial output previously but it now appears to have ceased as well. Telnet and FTP are working fine as is video extraction. No doubt more mucking about will be required. :eek:

P.P.S. - While, it's official. I'm definitely over the hill and having major senior moments. I discovered why I wasn't getting a bash prompt - I hadn't set it up in my rc.sysinit.author file! Doh! The good news is that I finally have bash back via serial on all my DTivos except one. I seriously hosed the backported driver install on that one by adding an incorrect symbolic link that didn't even need to be there in the first place.

wlblljb

08-14-2005, 11:30 PM

hello everyone,
I have tried to run the netconfig.tcl several times but I cannot get it to work
I get this message

.//netconfig.tcl No such file or directory

I saw some info on the internet that this was a error because it was a windows text file

I have ran other tcl files that I uploaded from Windows with no problems
I don't understand why it is not working

Thanks

Jamie

08-14-2005, 11:49 PM

I have tried to run the netconfig.tcl several times but I cannot get it to work
I get this message

.//netconfig.tcl No such file or directory

I saw some info on the internet that this was a error because it was a windows text file
...So you did enough research to discover that it might be dos style line endings. Did you take the next step and try running dos2unix on it? There are many posts on this topic. Here's (http://www.dealdatabase.com/forum/showthread.php?p=224088#post224088) one.

Also, did you really mean to have two slashes in the path to the tcl file?

wlblljb

08-15-2005, 01:08 AM

Thanks
That was it.
I knew that I had seen the command somewhere but none of the searches was bringing it back up.

BTW there were two slashes in the response line.
I tried to run it from a couple or dir's and got 2 slashes everywhere.
I didn't type them in they were just there in the response.

Thanks again

rbautch

09-13-2005, 08:43 PM

Freddy_k

09-15-2005, 01:21 PM

Hi All I have a hacked DSR 704 and 708 200 gig each 6.2 superpatched 1 hour buffer. I love em and owe all I have acomplished to you. My problem is I am trying to get MVR working and had no luck I have been following the posts and tried the netconfig.tcl on 1 unit it worked fine I can access it with static ip the works tivoweb works fine. THe second unit I get this error

bash-2.02# netconfig.tcl 10.1.1.100 255.255.255.0 0.0.0.0 0.0.0.0
Tmk Assertion Failure:
FsAllocateFunction, line 159 ()
Tmk Fatal Error: Thread tivosh <7165> strayed!
Paste the following into a shell to get a backtrace...

bt -t /tvbin/tivoapp <<END_OF_BT
read 0x2aaa8000 /lib/ld.so.1
read 0x2ab04000 /lib/libutil.so.1
read 0x2ab48000 /lib/libdl.so.2
read 0x2ab8c000 /lib/libpthread.so.0
read 0x2abe8000 /lib/libm.so.6
read 0x2acb0000 /lib/libc.so.6
0x012cdf04 0x01384aa4 0x0138518c 0x013851e0 0x00f58a3c 0x00f58124 0x00612c48
0x00403090 0x2acc13fc
END_OF_BT

Tmk Fatal Error: Thread tivosh <7165>: assertion failure
flushing ide devices: hda
Restarting system.

I dont understand the error and hope 1 of you here might have a idea.

Thanks

Freddy_k

Jamie

09-15-2005, 01:39 PM

Do a titles only search for "FsAllocateFunction".

Freddy_k

09-15-2005, 01:51 PM

Do a titles only search for "FsAllocateFunction".

Thanks I found a few and will test tonight.

Jamie Thank you that helped me and it worked I now have MRV to ad to my hacks :) I fat fingered the subnet missed last 0 :(

Thanks for not Bashing me :)

Freddy_k

Harry5150

09-16-2005, 01:18 AM

I have 2 4.x Dtivo's, slice upgraded to 6.2 with the networking info entered prior to the upgrade for static ip's. Superpatch has been done and music/photos is working. Both tivo's can see my computer (tivo desktop server) and I can telnet & ftp to both, but apparently they can't see each other.

Basicly I'd like to enable DHCP to attemp to fix my MRV problem.

So... am I right in just renaming the files back to original: /etc/netfilter-enable and /sbin/dhclient and reboot? Is there anything else I'm missing?

Oh yeah, lost my serial cable. :(

Jamie

09-16-2005, 01:22 AM

So... am I right in just renaming the files back to original: /etc/netfilter-enable and /sbin/dhclient and reboot? Is there anything else I'm missing?

Oh yeah, lost my serial cable. :(If you mv netfilter-enable back, you'll be re-enabling the firewall and you'll lose telnet/ftp access.

Harry5150

09-16-2005, 01:23 AM

Thanks, got it working.

scottym

09-27-2005, 10:47 AM

Does this (http://www.dealdatabase.com/forum/showpost.php?p=222557&postcount=24) post contain the latest/recommended netconfig.tcl for people not interested in wireless configuration?

scottym

10-02-2005, 01:33 AM

I'm not entirely sure why it is necessary to run netconfig.tcl before superpathc-67all. Superpatch did fail when I ran it without running netconfig.tcl first. I believe the argument that execution of the rc.sysinit.author command may be too late in the boot process to set a static address, but why write directly to the MFS object instances? Wouldn't it be easier to rename dhclient and add a dhclient symlink to /sbin that executes a simple script containing the ifconfig command.

I installed the Instant Cake 6.2 image and used PTVnet to gain network access. The superpatch-67all script would fail unless I first ran netconfig.tcl. I tried running netconfig.tcl and subsequently ran superpatch-67all and superpatch proclaimed success.

The end result is that I could see my two other TiVos running 4.01b from the "Now Showing" menu but my 6.2 TiVo reported that it was not enabled for MRV when I selected a different TiVo from the "Now Showing" menu. :confused:

Any help, as always, is appreciated!

yoviyer

10-20-2005, 09:30 PM

Attached is an interactive script to set SSID, DHCP, and WEP in MFS. The only catch is that you have to select from one of five predetermined WEP keys rather than one of your choosing. This will have to do until we figure out the hash that's applied to the hex value of WEP before it's stored in MFS. This issue is being discussed in the development forum here (http://www.dealdatabase.com/forum/showthread.php?p=232990&postcount=7). The script assumes you've already run netconfig.tcl.

Great script. Works like a charm. Enabled me to upgrade, network and MRV all my non-HR10-250 units. (3 DSR7000's and a Standalone Tivo with DVD). Did anyone get a chance to work on a used input WEP key? If not I can work on the hash. The only question I have is how did you get the actual hash or where in MFS does it reside?

rbautch

10-26-2005, 09:30 PM

Glad the script worked for you. I got the WEP keys by installing 4.01b, entering various WEP values through the on-screen menus, and then noting what the corresponding values are in MFS. Looks like the WEP effort has lurched forward recently in this thread. (http://www.dealdatabase.com/forum/showthread.php?t=44829) Please throw your hat into the ring!

jovillan

11-04-2005, 02:13 PM

Well, I have had 6.2 running for several months on three DTivo boxes. I haven't had any issues other than the following:

It seems that every-so-often the boxes will lose their network settings and drop off the network. The only way to get the boxes back on the network is by restarting them.

I thought this was being caused by the daily call, so I loaded the script to fake the daily call. I still have the network drop issue. I have searched through the posts and cannot find an answer to my problem. Can anyone please point me in the right direction?

Thanks for any help.

-----------------
120Gb HDRV2/6.2/WUSB11
120Gb DSR708/6.2/WUSB11

Jamie

11-04-2005, 02:44 PM

It seems that every-so-often the boxes will lose their network settings and drop off the network. The only way to get the boxes back on the network is by restarting them.Most likely this is a dhcp lease renewal issue. Are you using a fixed IP or dhcp? If you are using a fixed IP, how did you set the fixed IP? Is it possible the tivo is still trying to use dhclient?

Suggested references:
6.2 collected info (http://dealdatabase.com/forum/showthread.php?t=42325) (see section 3b),
6.2 MRV network configuration issues summary (http://dealdatabase.com/forum/showthread.php?p=222641#post222641).

jovillan

11-04-2005, 03:39 PM

Most likely this is a dhcp lease renewal issue. Are you using a fixed IP or dhcp? If you are using a fixed IP, how did you set the fixed IP? Is it possible the tivo is still trying to use dhclient?

Suggested references:
6.2 collected info (http://dealdatabase.com/forum/showthread.php?t=42325) (see section 3b),
6.2 MRV network configuration issues summary (http://dealdatabase.com/forum/showthread.php?p=222641#post222641).

The IP addresses are static. The network settings were done when I had 4.01 running on the boxes previously. I upgraded to 6.2 via slices. I did the following steps, during the 6.2 upgrade, which I thought would remove the dhcp issue:

1. Rename /sbin/dhclient to /sbin/dhclient.orig
2. Rename /etc/netfilter-enable to /etc/netilter-enable.not

I also have the following in my rc.sysinit.author,to prevent calls home:

# add static routes
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0

Thanks for our help.

Jamie

11-04-2005, 03:48 PM

The IP addresses are static. The network settings were done when I had 4.01 running on the boxes previously. I upgraded to 6.2 via slices. I did the following steps, during the 6.2 upgrade, which I thought would remove the dhcp issue:

1. Rename /sbin/dhclient to /sbin/dhclient.orig
2. Rename /etc/netfilter-enable to /etc/netilter-enable.notProbably not a dhclient problem then. You might want to examine it carefully through a serial console connection next time you lose the network.

jovillan

11-04-2005, 03:56 PM

Probably not a dhclient problem then. You might want to examine it carefully through a serial console connection next time you lose the network.

What should I look for? I do know that when I reboot the boxes I do not see the
"May 13 16:49:39 (none) KnownHost[17020]: Added TiVoConnect broadcast address 192.168.1.xxx"

anywhere in the /var/log/tvlog

Still the boxes all see each other. I just restarted them, so we will see how long it takes for them to lose each other, somtimes one day somtimes two.

Thanks again.

[edit] I wonder if running one of the network.itcl scripts you linked would help? The only problem is, I use SSID and WEP for my wireless setup.

Jamie

11-04-2005, 04:32 PM

What should I look for?Run ifconfig on the interface. Does it still have an IP address? Does it think it is still connected to the outside world?

If it doesn't have an ip address, that points back to a dhcp problem. Double check that there isn't a dhclient running.

If it has an IP address, but can't ping the outside world, take the interface down and bring it back up (ifconfig eth0 down; ifconfig eth0 up). Does that fix it? If not, try hot unplugging and plugging the usb dongle. Does that bring the interface up? I'd suspect a buggy driver if you find yourself here.

jovillan

11-04-2005, 04:36 PM

...try hot unplugging and plugging the usb dongle. Does that bring the interface up? I'd suspect a buggy driver if you find yourself here.

That actually leads me to what I was researching at the time of your reply. I have not loaded any of the backported drivers that are loaded on these forums. I am using the USB drivers that came with 6.2. Should I switch to backported drivers?

Jamie

11-04-2005, 09:45 PM

That actually leads me to what I was researching at the time of your reply. I have not loaded any of the backported drivers that are loaded on these forums. I am using the USB drivers that came with 6.2. Should I switch to backported drivers?I don't have any personal experience with them with wireless devices, so I can't say if they are more or less stable than the stock 6.2 drivers with that device. Perhaps someone else that uses a WUSB11 with 6.2 can chime in.

singe606

11-07-2005, 01:46 PM

I have 6.2 and WUSB11 (I think v2.8?), and I just kept the stock drivers. Seems pretty stable to me. Every once in a while I need to unplug it and plug it back in, but that's usually a result of my router locking up. Stability aside, is there any performance advantage to the backported drivers? Once I played around with netperf and I got ~3.7Mbps out and ~0.9Mbps in. I can't remember what the limiting factor is...

jovillan

11-09-2005, 03:08 PM

...try hot unplugging and plugging the usb dongle. Does that bring the interface up? I'd suspect a buggy driver if you find yourself here.

Lost connectivity to my HDVR2 last night. I removed the usb and plugged it back in, box came back up on the network. So I am assuming that this means it is most likely a driver issue. I have not had any issues with the DSR708's. I am hesitant to mess with the drivers, just cause I don't really want to lose network connectivity if I frack it up. I may just live with rebooting the wireless-nic when I lose connectivity.

I will keep my eye on the boards to see if anyone comes out with a definite issue/fix for this problem. Thanks for all your help.

DIDS

11-19-2005, 11:41 AM

I am trying to run the netconfig.tcl and am getting a message saying "No such file or directory". I FTP the netconfig.tcl file into /var and ran and got the following response when trying to run it:

DIDS_Tivo:/var$ ./netconfig.tcl 192.168.0.4 255.255.255.0 192.168.0.0 192.168.0.0
bash: ./netconfig.tcl: No such file or directory

I also tried to FTP it to Tivo-bin and ran it again and got the same response:

DIDS_Tivo:/tivo-bin$ ./netconfig.tcl 192.168.0.4 255.255.255.0 192.168.0.0 192.168.0.0
bash: ./netconfig.tcl: No such file or directory

I have already done the Superpatch-67all install and set the Tivo Name by running "set_mrv_name_67.tcl". I made sure I made my drive read/write (mount -o remount,rw /" before running netconfige.tcl and did "chmod 755 /tivo-bin/netconfig.tcl" also "chmod 755 /var/netconfig.tcl". Would someone be able to give me a hint as to what I am doing wrong. I searched the forum and also google and didn't find anything on the search phrase "./netconfig.tcl: No such file or directory". Thanks for any help you may be able to provide me.

Regards,

DIDS

Jamie

11-19-2005, 11:50 AM

I am trying to run the netconfig.tcl and am getting a message saying "No such file or directory". I FTP the netconfig.tcl file into /var and ran and got the following response when trying to run it:
FAQ: What causes "No such file or directory" errors when running bash/tcl scripts? (http://www.dealdatabase.com/forum/showthread.php?p=224088#post224088)

Hint: try searching for the error message string when you get an error. Read item (S1) in this (http://www.dealdatabase.com/forum/showthread.php?p=202772#post202772) newbie sticky.

DIDS

11-19-2005, 12:02 PM

Thanks Jamie. I dont remember opening this up in a windows editor,but I guess I did because it executed fine after doing dos2unix. I usually use metapad when opening unix files in windows that way I dont run into these problems. Most have been very tired when I opened it in another editor.

Regards,

DIDS

jovillan

12-13-2005, 05:05 PM

** Update:
I still have issues with my HDVR2 dropping off the network from time-to-time. At first, I would unplug/plug the device and it would come back on the network.

For some reason I decided to try something new the next time it dropped off the network. I went down to my PC and started to ping the IP address of the HDVR2. The first few pings timed out, then it started to repsond.

Not sure what this means, I just thought it was kind of odd. Does the WUSB11 or HDVR2 have some sort of sleep mode? One explanation is that the range of my WRT54G sucks, and the network adapter is losing connectivity. Then pinging renews the connection...? I don't know. Just thought I would share.

gnezer

01-16-2006, 02:28 AM

Have two S2 Tivos (DSR-708 & SD-DVR40, both on sw 6.2-01-2-301)... both Instacake, PTV Net, Alpha Wolfe's S2s, superpatch-67all-NutKase-1.0). I have the Tivos successfully networked wirelessly (with USB200Ms).

Now I'm trying to get MRV working.

Started, mistakenly in the mfs_ftp thread where Jamie offered the following in response to my statement "I checked the network settings in my author file... as I set them for static weeks ago, and all seemed to work fine.":

This is almost certainly your problem. You should not be setting your ip settings in your author file with 6.2, or if you do you need to disable dhclient and run /sbin/hotplug manually. The suggestion method is to either run the netconfig.tcl script to set your network settings in MFS, or use dhcp. See this post for summary information, and follow the link there to the thread I pointed you to earlier for further discussion. Please move any further discussion to that thread where this conversation is on topic: " Superpatch/MRV network configuration issues". This has nothing to do with mfs_ftp.

So now I'm here, having attempted to run netconfig.tcl. Unfortunately, I received the response:

bash-2.02# ./netconfig.tcl
Network config v1.1 by L.G. Kahn

Error: Syntax is netconfig ipadress subnetmask defaultgw dns-server!

On this Tivo:

IP Address=192.168.1.201
Network=255.255.255.0
Broadcast=192.168.1.255
Gateway=192.168.1.1

So, I'm lost on what to add to the netconfig.tcl statement. This Tivo's IP address? Is "defaultgw" calling for the Gateway value? Where would I determine the "subnetmask" and "dns server" values?

Finally, if going back to DHCP is an easier road, I'm willing to live with the changing IP addresses for the Tivos... just need a nudge to finally get this done.

cheer

01-16-2006, 02:44 AM

Error: Syntax is netconfig ipadress subnetmask defaultgw dns-server!

On this Tivo:

IP Address=192.168.1.201
Network=255.255.255.0
Broadcast=192.168.1.255
Gateway=192.168.1.1

So, I'm lost on what to add to the netconfig.tcl statement. This Tivo's IP address? Is "defaultgw" calling for the Gateway value? Where would I determine the "subnetmask" and "dns server" values?
./NetConfig.tcl 192.168.1.201 255.255.255.0 192.168.1.1 x.x.x.x
Replace "x.x.x.x" with the IP address of your DNS server. "255.255.255.0" is your subnet mask, and "defaultfw" is indeed your Gateway.

gnezer

01-16-2006, 12:54 PM

Cheer-

Thanks for this info... I feel like I'm finally making some headway.

But I need to make sure I gave you good data...

Since my last post, I ipconfig'd on my PC and received:
Connection-specific DNS Suffix= domain_not_set.invalid
IP Address= 192.168.1.100
Subnet mask=255.255.255.0
Default Gateway= 192.168.1.1

So, I'm clear on the subnet mask & gateway values. But which IP address should I use with the netconfig.tcl statement? Is it this one (from my PC, 192.168.1.100) or the IP address (in my earlier message) I set on the Tivo (192.168.1.201)?

And the DNS server value really has me puzzled. What does the statement "domain_not_set.invalid" mean, and how do I fix it? For that matter, am I even referring to the the correct DNS value (per your earlier message)?

One other question.... I have been laboring under the impression that using netconfig.tcl, required FTPing over to the Tivo, with no requirement to place the file in a specific folder before invoking it. Is that a correct assumption?

Thanks for your help here...

Edit: Just found my way to my broadband router's URL. So now I see that the domain name box is empty, and the router's DNS value is 192.168.0.1. Should I use this DNS value in the netconfig.tcl statement?

Narf54321

01-16-2006, 01:11 PM

Edit: Just found my way to my broadband router's URL. So now I see that the domain name box is empty, and the router's DNS value is 192.168.0.1. Should I use this DNS value in the netconfig.tcl statement?

If your router gets its own IP from your upstream provider (most home routers use DHCP themselves when "talking" to your ISP), you should use either the DNS of your ISP, or the DNS address of the router itself. Most routers will act as a DNS proxy so you don't have to worry about it.

192.168.0.1 would be on a different subnet than your tivo ( 192.168.1.201 or whatever you are setting ), but it might work. Usually, if the router does DNS proxy, you want to set DNS the same as your gateway address (which in your case seems to be 192.168.1.1 )

cheer

01-16-2006, 01:23 PM

So, I'm clear on the subnet mask & gateway values. But which IP address should I use with the netconfig.tcl statement? Is it this one (from my PC, 192.168.1.100) or the IP address (in my earlier message) I set on the Tivo (192.168.1.201)?
The one on your Tivo. Also, once this is all done, be sure to remove the ifconfig statements from rc.sysinit.author and reboot.
And the DNS server value really has me puzzled. What does the statement "domain_not_set.invalid" mean, and how do I fix it? For that matter, am I even referring to the the correct DNS value (per your earlier message)?
No, what we want is the IP address of the DNS server. Go back to your PC and from a command prompt run "ipconfig /all" and you should see one (or more) IP addresses listed for DNS server. Just take the first one listed and use that.
One other question.... I have been laboring under the impression that using netconfig.tcl, required FTPing over to the Tivo, with no requirement to place the file in a specific folder before invoking it. Is that a correct assumption?
Yep!
Edit: Just found my way to my broadband router's URL. So now I see that the domain name box is empty, and the router's DNS value is 192.168.0.1. Should I use this DNS value in the netconfig.tcl statement?
Confirm by running "ipconfig /all" on your PC. It may be that your router is feeding that as a DNS IP to your PC and then acting as a proxy, as Narf mentions. On the other hand, that may just be a default bogus value. By doing the check on your PC you'll know for sure.

gnezer

01-16-2006, 02:45 PM

Great news...

After following your advice (re: netconfig.tcl) to the letter, I rebooted both Tivos, and now MRV is working. I see (and can access) the other Tivo's Now Playing list.

So, now my question is in response to your last bit of advice:

"Also, once this is all done, be sure to remove the ifconfig statements from rc.sysinit.author and reboot."

So I vi the rc.sysinit.author file, and get the following text which seems related to your advice:

# Check flags for IP address (we recommend you just stick with DHCP)
if [ -f /init/ptv_flags/DHCP_ON ]; then
/ptvupgrade/bin/dhcp_enable.ptv
fi

if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
fi

Understandably, I'm a little skittish in making changes to the author file without being certain I've got it right. Am I in the right place, and referring to the right text? Am I to place a # in front of both of the above "if" statements, or just the "static on" one? And do I place the # in front of the first "if", or each line of that "paragraph"?

Will this in any way affect my ability to remain wireless, with static IPs on both Tivos?

Thanks again...