Advertisement
Guest User

Untitled

a guest
Feb 21st, 2015
58
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.76 KB | None | 0 0
  1. * Now talking on #raspberrypi
  2. * Topic for #raspberrypi is: Unofficial RaspberryPi IRC channel but "Blessed" by the Foundation as the ONE channel. Logs @ http://srv.datagutt1.com <> Channel Rules as of 6 May '14: http://tiny.cc/h7za1w <> Getting help on IRC: http://tiny.cc/p9za1w
  3. * Topic for #raspberrypi set by ShorTie!~Idiot@unaffiliated/shortie (Thu Jan 29 11:49:50 2015)
  4. * msample is now known as Myrtti
  5. <OffensiveUser> helo
  6. <ShorTie> Good Morning
  7. * not_underground (~chatzilla@ip70-170-43-227.lv.lv.cox.net) has joined
  8. * Jinx has quit (Quit: reboot)
  9. <OffensiveUser> anyone here knowledgable on small displays
  10. * Moony22 has quit (Quit: leaving)
  11. <ShorTie> like what kind, that is kinda vage
  12. <OffensiveUser> well https://www.fasttech.com/products/1230/10012142/2062707-4-3-tft-foldable-car-vehicle-mounted-rearview this one to be exact
  13. <ShorTie> not that perticular 1, but ya i got a couple tft rearview screens
  14. <ShorTie> ws
  15. * nicdev has quit (Remote host closed the connection)
  16. <ShorTie> whats sup ??
  17. * nicdev (user@2600:3c03::f03c:91ff:fedf:4986) has joined
  18. * interest1ng (~interest1@110-174-176-171.static.tpgi.com.au) has joined
  19. <OffensiveUser> i've read of similar displays regulating to 5v somewhere inside
  20. * chris_99 has quit (Quit: Ex-Chat)
  21. <interest1ng> hey, I am having a peculiar issue
  22. <interest1ng> my network is unreliable on the rpi (2)
  23. <interest1ng> internet completely stops working after a few hours
  24. <interest1ng> but local network works :/
  25. <ShorTie> yup, you can hook them up like this https://www.dropbox.com/s/kpe5ek17e7e4fkf/IMAG0003.JPG?dl=0
  26. <interest1ng> if i shutdown (and wait) i can usually reconnect to the internet
  27. <interest1ng> could anyone tell me where i can start looking to troubleshoot
  28. * cameronfr (~cameronfr@125.32.134.27.ap.yournet.ne.jp) has joined
  29. * utack (~utack@ip9234cb8c.dynamic.kabel-deutschland.de) has joined
  30. <ShorTie> wifi ??
  31. <interest1ng> ShorTie: i am using a wireless bridged adapter, which works fine with other devices
  32. <ShorTie> so wifi
  33. <ShorTie> you need a ping script to keep it alive or try wicd-curses
  34. <interest1ng> yes, but certainly no driver issues
  35. <interest1ng> there are network applications running 24/7 on it
  36. <interest1ng> that's how i know internet stops working ;0
  37. <ShorTie> give wicd-curses a try
  38. * druidd has quit (Ping timeout: 265 seconds)
  39. <interest1ng> its a bridge, the raspberry pi is connected via ethernet to it
  40. <OffensiveUser> so if I understand your connection is AP > receiving ap > pi
  41. <interest1ng> OffensiveUser: yes
  42. <interest1ng> it works fine on the old pi and on other devices
  43. <OffensiveUser> and you can reach the pi from the first ap if internet gives out?
  44. <interest1ng> OffensiveUser: yes, the pi can communicate with the local network. it's just the internet that does not work
  45. <OffensiveUser> does restarting the network adapter on the pi do anything
  46. <interest1ng> its strange: if i reboot the pi/the bridge, the internet doesnt work
  47. <interest1ng> but if i shut down the pi and wait, say an hour, and boot it up again, it works
  48. * Macuser has quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
  49. <interest1ng> what is extremely strange is that when the internet stops working on the pi, if a ping, it says the ping is "from" 192.168.1.9, when my whole network is on a 192.168.2.x subnet, and the pi is 192.168.2.115
  50. <interest1ng> but i can still ssh into it
  51. <OffensiveUser> hmm
  52. <OffensiveUser> dhcp?
  53. <Bilby> It sounds like the bridge may be assigning itself an IP address as well
  54. <interest1ng> no, using static, so i can ssh into it
  55. * eggy has quit (Ping timeout: 250 seconds)
  56. <interest1ng> Bilby: hmm interesting idea
  57. <Bilby> the pi is set up with a static IP - any chance it's within the DHCP range of the router and the router is handing the same IP to something else?
  58. * mumixam has quit (Ping timeout: 272 seconds)
  59. <Bilby> what's the model on the bridge?
  60. <interest1ng> bridge is a tp-link WR703N
  61. <OffensiveUser> have you checked the settings on it
  62. <interest1ng> it has been setup for over a year, and never failed me before
  63. <Bilby> are you running openwrt on it?
  64. * Logicwax has quit (Ping timeout: 245 seconds)
  65. <interest1ng> i havent touched the config of it for so long ;) but i believe it was running ddwrt
  66. * Lartza has quit (Read error: Connection reset by peer)
  67. <Bilby> I wooooonder if something ended up turning on the dhcp server in it...
  68. <OffensiveUser> I'd check everything from wall to pi and back again
  69. <OffensiveUser> even if it's running for over a year
  70. * Lartza (lartza@unaffiliated/lartza) has joined
  71. <interest1ng> Bibly: however the ip address of the pi doesn't change, i can still ssh into it
  72. <Bilby> interest1ng because it's static and just cross-routing on the tp-link
  73. <interest1ng> i havent touched the bridge for so long, i forgot its ip :P
  74. <Bilby> it would account for the out-of-range ip address, at lesat
  75. <interest1ng> i dont even know if i CAN configure it if it is a bridge
  76. <Bilby> Plug it directly into a computer and see if DHCP assigns an IP address?
  77. <interest1ng> you might be right, there could be a conflict with the ips because of bridge
  78. <interest1ng> dhcp will assign an address, because it did before, i just told the pi to use static
  79. * Macuser (~textual@unaffiliated/macuser) has joined
  80. <Bilby> take it outside the wifi network or turn wifi network off temporarily and see if plugging a cat5 between the tp link and a computer gives you a 192.168.2.* address ;)
  81. * eggy (eggy@unaffiliated/eggy) has joined
  82. <interest1ng> that's an interesting test
  83. <interest1ng> so that will check if the bridge is trying to use dhcp
  84. <Bilby> right
  85. * n-st (~n-st@2001:470:7272:0:6877:a44c:5fba:9e9) has joined
  86. <Bilby> if you get a 192.186.2 address you know the tp-link is handing them out like they're going out of style
  87. <Bilby> then, get into it and make sure it's set to just do bridgework
  88. <interest1ng> alright brb ;)
  89. * interest1ng has quit (Quit: leaving)
  90. * cceleri has quit (Remote host closed the connection)
  91. <OffensiveUser> why not just get in the tp-link and check if the deamon is running
  92. <Bilby> because he doesn't know if it's the problem and apparently doesn't have easy access
  93. * x1337807x has quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
  94. <OffensiveUser> true
  95. <Bilby> Also if he already has a dhcp address he's in the right subnet to connect to the config page or ssh in
  96. * gbaman has quit (Remote host closed the connection)
  97. * Moshin (~bangboom@udp000088uds.hawaiiantel.net) has joined
  98. * Saphyel has quit (Read error: Connection reset by peer)
  99. <OffensiveUser> should tell him to jot down the ip of the bridge and tape it to the bottom of it for future reference
  100. <OffensiveUser> probably needs a username and password too
  101. <Bilby> yeah hah
  102. * Adran (~adran@botters/staff/adran) has joined
  103. <OffensiveUser> having used ddwrt i know this for certain actually
  104. <Bilby> For that kind of thing it's a great solution
  105. <Bilby> for more official applications i keep it in a password file ;)
  106. <teclo-> OffensiveUser: I got a weird problem with my dd-wrt. My subnet is 10.20.*, but once in a while dd-wrt gives me an 192.168.1.2 address
  107. * druidd (~lindsey@2602:306:cda2:d3e0:1a3d:a2ff:fe2c:feb0) has joined
  108. * Tachyon` is now known as Tach[Zzz]
  109. * mumixam (~m@unaffiliated/mumixam) has joined
  110. * interest1ng (~interest1@110-174-176-171.static.tpgi.com.au) has joined
  111. <interest1ng> alright im back
  112. teamplayer techwave61 teclo- teepee teknic111 terrasapien
  113. teamplayer techwave61 teclo- teepee teknic111 terrasapien
  114. <interest1ng> my computer failed to connect to the bridge (because main AP was down) and there was no ip address assigned (so no DHCP)
  115. <OffensiveUser> teclo-, you seem to be having a similar problem as interest1ng
  116. <interest1ng> oh, i just connected, what is telco's problem
  117. <OffensiveUser> dd wrt assigns an ip thats not in the subnet
  118. * Guma (~Guma@mobile-166-184-168-170.mycingular.net) has joined
  119. <interest1ng> the IP IS in the subnet
  120. <Bilby> interest1ng hmm
  121. <interest1ng> it stays as 192.168.2.115
  122. <interest1ng> thats why i can ssh into it
  123. <interest1ng> however INTERNET is not working. pretty strange issue.
  124. <Bilby> yes
  125. <interest1ng> and internet works fine, its after a few hours/days it completely stops working
  126. <Bilby> that is pretty strange
  127. <OffensiveUser> can you get into the main access point? maybe that'll list ips of connected devices
  128. <interest1ng> and requires a shutdown, long wait, and boot
  129. * Logicwax (Logicwax@c-50-161-23-192.hsd1.ca.comcast.net) has joined
  130. <Bilby> no way to swap out or bypass the bridge efor a little bit to test it?
  131. <OffensiveUser> then you can trail and error until you hit the bridge
  132. <OffensiveUser> check if it's running the dhcp deamon
  133. <Bilby> it's pretty strange stuff interest1ng i'll give you that. I had a somewhat similar problem at one client, it ended up being the stupid bloody SBC dsl box though
  134. <interest1ng> OffensiveUser: as i noted previously, my computer failed to receive an IP from the bridge alone
  135. <OffensiveUser> oh yeah
  136. <OffensiveUser> sorry
  137. <OffensiveUser> uh
  138. <Bilby> sporadic IP issues are insanely frustrating to troubleshooting
  139. <Bilby> interest1ng no way to run a cat5 all the way?
  140. t0mab Tach[Zzz] tacoexe tapout Taylor taza tchan tchiwam tdy teamplayer techwave61 teclo- teepee teknic111 terrasapien TheKlap thescatman theugster timewa1ker timtaler TmvC toillbail tomaw tonic tonsofpcs tr00p treeherder trevlar trevorman Triffid_Hunter trisi Tronsha Tykling TyrfingMjolnir
  141. teamplayer techwave61 teclo- teepee teknic111 terrasapien
  142. * Logicwax has quit (Ping timeout: 264 seconds)
  143. <teclo-> well in my case ww-drt gives me an adress which is not in the subnet
  144. <OffensiveUser> how do you have yours set up?
  145. * Sonny_Jim has quit (Quit: leaving)
  146. <teclo-> one subnet, 10.20.40.100 to 10.20.40.200
  147. * mumixam has quit (Ping timeout: 272 seconds)
  148. <teclo-> and onece in a while it gives me 192.168.1.2
  149. * Logicwax (Logicwax@c-50-161-23-192.hsd1.ca.comcast.net) has joined
  150. * ShorTie thinkz, but you don't get ip address from a bridge
  151. * DLSteve has quit (Quit: Leaving)
  152. <Bilby> all right lads, i'm off-shift, going to get a drink and have supper
  153. <Bilby> ShorTie with dd-wrt you can
  154. <Bilby> it's the meth of wireless device hardware
  155. <ShorTie> don't think you can/should have 2 dhcp servers on a network
  156. * Macuser has quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
  157. <ShorTie> or you shouldn't
  158. <OffensiveUser> you can
  159. <OffensiveUser> but you shouldn't
  160. * Adran has quit (Ping timeout: 240 seconds)
  161. <Bilby> that
  162. <Bilby> it causess lots of problems
  163. <ShorTie> i hear that
  164. <OffensiveUser> hmm
  165. <interest1ng> i'm honestly giving up trying to troubleshoot the bridge. i'll inconveniently connect the rpi directly to the AP for a while and see if it works
  166. <OffensiveUser> hows the range on that ap set
  167. <OffensiveUser> is your pi's address in range
  168. * voxxit has quit (Remote host closed the connection)
  169. <acidjazz> lol you got a log of tis chat
  170. <acidjazz> this chat
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement