DHCP Annoyances (Apr 19 2007)
Message boards :
Technical News :
DHCP Annoyances (Apr 19 2007)
Message board moderation
| Author | Message |
|---|---|
 Matt Lebofsky  Send message Joined: 1 Mar 99 Posts: 1444 Credit: 957,058 RAC: 0 
|
Spent the morning ramping myself up on using subversion instead of cvs. That's the way BOINC is going, and therefore SETI is getting pulled along into it as well. Fair enough. The BOINC backend is a bit backed up in general. I think it's a combination of a few things - recovering from the recent "partial" outage where bruno was dropping a subset of connections for many hours, the general increase in splitter/validator demand due to the quorum changes, and catching up from the assimilators being off for a day to build an index on the Guassian table. We'll see how it goes. In the meantime I fired up an extra splitter on kryten to hopefully prevent running out of work to send out. There are still a fair number of hits on kryten's secondary upload/download server despite the DNS switch over a month ago. We're talking about 1-2 hits per second (as opposed to 20-30 per second on bruno). I think next week we'll shut it down no matter what, as the new gigabit switch came in the mail today. This will allow us to move bruno into the closet and therefore have fast access to the workunit filesystem and therefore we can move the remaining BOINC server processes off of kryten and perhaps push that aged system into retirement. No timeframe on that yet. I just tried getting this switch on the network (has web-based remote management). It can only get its IP address via DHCP upon installation. Of course, it's not finding our lab-wide DHCP server which I have no control over (nor am I allowed to start my own, for security reasons). Sigh. We'll get that sorted out at some point. It probably is some rogue DHCP server on the network messing things up (people bring their Linksys switches in from home and think they're being so clever). - Matt -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude ID: 549225 ·  |
Toby  Send message Joined: 26 Oct 00 Posts: 1005 Credit: 6,366,949 RAC: 0
|
RE: the DNS changes... I know the boinc client had (I think it has been fixed now) a problem with never flushing its DNS cache unless you restarted it completely. Probably just some missing curl setting but very annoying when projects change their IPs around. I remember a couple occasions when I couldn't get any work from a project because they had changed DNS and a week later boinc was still using the old IP. A member of The Knights Who Say NI! For rankings, history graphs and more, check out: My BOINC stats site ID: 549240 · |
|
Matt Lebofsky Send message Joined: 1 Mar 99 Posts: 1444 Credit: 957,058 RAC: 0
|
I know the boinc client had (I think it has been fixed now) a problem with never flushing its DNS cache unless you restarted it completely. Yeah.. I'm certain that's what it is. But we gotta shut down kryten sometime. So when we do those clients will eventually notice they are frozen and hopefully the users will restart before giving up. We'll probably post a news item when we do. - Matt -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude ID: 549245 · |
KWSN THE Holy Hand Grenade!  Send message Joined: 20 Dec 05 Posts: 3187 Credit: 57,163,290 RAC: 0
|
I know the boinc client had (I think it has been fixed now) a problem with never flushing its DNS cache unless you restarted it completely. When you do finally shut down Kryten, you might want to post a notice on the main page, like you did back in Febuary, when you changed Net providers. Something on the order of: "If your client can no longer contact Berkeley, stop the BOINC client and re-start it... and if that doesn't work, re-boot!" should handle anyone who looks at the main page... .  Hello, from Albany, CA!... ID: 550148 · |
|
seti@elrcastor.com Send message Joined: 30 Jan 00 Posts: 35 Credit: 4,879,559 RAC: 0
|
I just tried getting this switch on the network (has web-based remote management). It can only get its IP address via DHCP upon installation. Of course, it's not finding our lab-wide DHCP server which I have no control over (nor am I allowed to start my own, for security reasons). Sigh. We'll get that sorted out at some point. It probably is some rogue DHCP server on the network messing things up (people bring their Linksys switches in from home and think they're being so clever). no console port on it? 
ID: 550229 · |
John McLeod VII  Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0
|
I just tried getting this switch on the network (has web-based remote management). It can only get its IP address via DHCP upon installation. Of course, it's not finding our lab-wide DHCP server which I have no control over (nor am I allowed to start my own, for security reasons). Sigh. We'll get that sorted out at some point. It probably is some rogue DHCP server on the network messing things up (people bring their Linksys switches in from home and think they're being so clever). Most new routers don't have console ports on them...   BOINC WIKI ID: 550317 · |
|
seti@elrcastor.com Send message Joined: 30 Jan 00 Posts: 35 Credit: 4,879,559 RAC: 0
|
well, all cisco ones do. just wondering because i thought there might be a higher network equipment standard they had to adhear to, aka cisco.
ID: 550500 · |
|
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0
|
well, all cisco ones do. just wondering because i thought there might be a higher network equipment standard they had to adhear to, aka cisco. Actually, if I recall correctly, linksys is owned by cisco, so not even that statement is strictly true. BOINC WIKI ID: 550633 · |
|
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0
|
well, all cisco ones do. just wondering because i thought there might be a higher network equipment standard they had to adhear to, aka cisco. ... and remember, this is an ethernet switch (hub), not a router. ID: 550675 · |
KWSN - Chicken of Angnor  Send message Joined: 9 Jul 99 Posts: 1199 Credit: 6,615,780 RAC: 0 
|
Hi Matt, not sure which Linksys switch exactly you're trying to set up, but I'm guessing it'll be a business-class managed one. So it's probably one of this series - probably something like SRW2024 or -48, a 24- or 48-port switch with 2/4 SFP slots for fiber connection. I looked at the docs for the WebView switches, and they do say they have a serial console. The PDF has a rear view of the device, which includes a 9-pin serial plug. PDF I'm referencing:
HTH, Simon. Donate to SETI@Home via PayPal! Optimized SETI@Home apps + Information ID: 550889 · |
|
seti@elrcastor.com Send message Joined: 30 Jan 00 Posts: 35 Credit: 4,879,559 RAC: 0
|
well, all cisco ones do. just wondering because i thought there might be a higher network equipment standard they had to adhear to, aka cisco. i was refering to switches like this http://www.cisco.com/en/US/products/hw/switches/ps5528/index.html or a router like this http://www.cisco.com/en/US/products/ps5855/index.html
ID: 551135 · |
Pappa  Send message Joined: 9 Jan 00 Posts: 2562 Credit: 12,301,681 RAC: 0
|
Sorry Most are missing the point... There is a "rouge router" that is giving out 192.168.x.xxx addresses that caused the issue in SSL Address Space... So there is a larger problem, that the SSL IT Staff has to find... Then Help them configure it properly to coexist... In the mean time it blocked moving the Gigabyte Switch into the Server Closet to to solve other Seti Issues... Please consider a Donation to the Seti Project. ID: 551246 · |
Richard Haselgrove  Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 
 |
An observation, and a suggestion. Observation: I have no idea what make of gigabit switch is being configured, though Pappa possibly does - I believe it was a user donation. Until/unless we have that information, any number of well-meaning links to configuration guides will be so much obfuscation. Re-read the OP: the reference to Linksys was just a disparaging remark about the possible provenance of the 'rogue router' which Pappa has described. Suggestion: why not set up your own 'rogue network' in the lab? One PC, one cheap'n'cheerful router, and the gigabit switch - isolated from everything else for the duration. If it wants DHCP, it can have DHCP for just enough time to teach it better manners! With a second PC nearby to look up the reference values, you should be able to do enough configuration to get it to co-exist with the rest of the IP address space: then you can connect it to the lab pipes, and finish the job off properly. ID: 551263 · |
|
Pappa Send message Joined: 9 Jan 00 Posts: 2562 Credit: 12,301,681 RAC: 0
|
Richard, Hehehehhe It only takes a Laptop, a cheap router and the Switch and two network cables... The larger issues is, the "rogue router" that caused things to not happen... It could also cause other issues within the SSL network with getting to setiboinc.ssl.berkerley.edu... Or getting "kryten" offline properly... The one that I recommended and sent money for was a DLink.. So yes, part of this is my fault! Yes I could bore many with instructions to Matt on how to get around what the SSL IT Staff needs to do... It still goes back to Matt, to resolve it inspite of what I may incorrectly suggest... I am not there and I/We can not see many things that would make the configuration easier... It really means that other departments needs more IP's that did not ask, or know how to properly configure... So it caused another problem that Seti has to deal with... It takes time... So I guess this is my fault as I sent a Check for $400 to get the Gigabyte Switch... Please do not tell my wife, as she does not know yet! Pappa An observation, and a suggestion. Please consider a Donation to the Seti Project. ID: 551269 · |
Fuzzy Hollynoodles  Send message Joined: 3 Apr 99 Posts: 9659 Credit: 251,998 RAC: 0 |
Richard, Hehehehhe Oops, sorry, I think I mentioned that to Kate the other day. :-O (;-D) "I'm trying to maintain a shred of dignity in this world." - Me 
ID: 552271 · |
Demiurg  Send message Joined: 2 Jul 02 Posts: 883 Credit: 28,286 RAC: 0 
|
192.168.x.xxx And I who thought 192.168ers where in sweden... Carl Edit/ Excepting 192.168.x.xxx ie, the 168 group up intil 175. Well, every day one learn something is a good day:-) ID: 552295 · |
|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874
|
192.168.x.xxx 192.168.xxx.yyy is, and always has been, assigned for usage on private networks and is non-routable to the internet at large. Here's a summary. ID: 552300 · |
|
Demiurg Send message Joined: 2 Jul 02 Posts: 883 Credit: 28,286 RAC: 0
|
[quote]192.168.x.xxx 192.168.xxx.yyy is, and always has been, assigned for usage on private networks and is non-routable to the internet at large. I just noticed via http://www.ipaddresslocation.org/ip_ranges/get_ranges.php I am just so used to 192 being swedens primary IP... Carl ID: 552302 · |
|
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0
|
192.168.x.xxx Actually, the private IP ranges were not reserved until March 1994. The original document is RFC-1597, and the current RFC is 1918. Before 1994, NAT and other translating schemes were not widely used, and private IP based networks just picked some random block. They often had to renumber when they connected to the internet and found a conflict with some other site. ID: 552496 · |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.