I am posting this here beacuse a lot of the smart photobridge guys hang out here.
If I Telnet into the Photobridge (Rev B 2.0.36) The connection sequence takes about 25 seconds before a connection is made. I have tried various telnet programs, but they all take about the same amount of time so I am deducing it is the Photobridge. Once the connection is made all proceeds as one would expect.
I do not recall this being the case in the early Photobridge days.
Can any one please shed some light on this. I want to do some work using the Telnet interface but the lomg delay on connection seems unreasonable from a user interface perspective.
Your Digital Media Has Never Looked So Good
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
Almost Instantanous
When I telnet to my Roku the connection is very quick.
No delay at all.
No idea what would be causing the delay for you but it doesn't seem to be a ROku issue.
Box is a Rev B running .036
No delay at all.
No idea what would be causing the delay for you but it doesn't seem to be a ROku issue.
Box is a Rev B running .036
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
-
- leenuxg33k
- Posts: 170
- Joined:
- Location: Boston, MA
- Contact:
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
I get an immediate notification of connected (that is the event 'connected' fires in my telnet program). I can do nothing until the Prompt event fires indicating reeipt of a prompt and that the system is ready for input, normally the logon sequence the time between the connected event firing and the prompt event firing looks like about 25 seconds.
-
- leenuxg33k
- Posts: 170
- Joined:
- Location: Boston, MA
- Contact:
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
What is the format of an entry in the etc hosts file?
I put in:
192.168.1.202 victor
where 192.168.1.202 is the IP address and the host name is victor. One space between them, IP starts in col 1.
Is that correct? unfortunately it did not help
From what I can see, I am getting a connection. I am just not getting back the prompt indication (prompt received event firing) until about 25 seconds have elapsed.
I put in:
192.168.1.202 victor
where 192.168.1.202 is the IP address and the host name is victor. One space between them, IP starts in col 1.
Is that correct? unfortunately it did not help
From what I can see, I am getting a connection. I am just not getting back the prompt indication (prompt received event firing) until about 25 seconds have elapsed.
-
- jm_maclaren
- Posts: 329
- Joined:
Did you put anything in .bash_profile that is eating time?
mine is
mine is
Code: Select all
# .bash_profile
# User specific environment and startup programs
export PATH=.:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin
export PS1="# "
alias l='ls -F'
alias la='ls -Fa'
alias ll='ls -Fal'
export TERM=ansi
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
-
- jm_maclaren
- Posts: 329
- Joined:
what does ping say
mine gives
$ ping 192.168.1.111
Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
does your 1st ping take a while? If not it is something in the log on thats taking time.
mine gives
$ ping 192.168.1.111
Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
does your 1st ping take a while? If not it is something in the log on thats taking time.
-
- barrygordon
- Posts: 275
- Joined:
- Location: Merritt Island FL
- Contact:
-
- jm_maclaren
- Posts: 329
- Joined:
This just happened to me when my cable internet went out so the roku couldn't reach the outisde world. The telnet login had this huge delay in loggin in and I also couldnt do an nfs mount. Now the internet is back up all is well. Maybe that is your issue too. Can't say I fully understand this, but hey I live in New Orleams the land of voodoo and other weird stuff!
-
- leenuxg33k
- Posts: 170
- Joined:
- Location: Boston, MA
- Contact:
jm_maclaren wrote:This just happened to me when my cable internet went out so the roku couldn't reach the outisde world. The telnet login had this huge delay in loggin in and I also couldnt do an nfs mount. Now the internet is back up all is well. Maybe that is your issue too. Can't say I fully understand this, but hey I live in New Orleams the land of voodoo and other weird stuff!
After hearing this I would bet on it being dns! If this is still happening even when your internet is back up I would look at your dhcp server and see if it is handing out the correct address. once you connect to the roku cat the /etc/resolv.conf file and see what it points to and see if you can ping that address.
Who is online
Users browsing this forum: No registered users and 5 guests