- WLUG - wlug.mailman3.com

Re: [Wlug] Newbie to mailing list- Issue with the generation of graphs in redhat 6.2

by Tom Guilderson

Peram, the top of the stack indicates that the java class loader can not find a particular class needed by java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment() Looking quickly at the javadocs for this - GraphicsEnvirpnment refers to the rendering target of the Graphics2D object. Most likely this method expects to find a target - meaning not only a configured X server - but a running X-server??? Was the X server running on the other machine when you weblogic server was running? If so start X on the other machine, then start weblogic and see what happens. If it is not that - then the problem is that one of the native X windows libraries is missing. If you figure out which java_vm binary is being executed (probably $JAVA_HOME/jre/bin/i386/native_threads/java_vm, then runn ldd against it to see what libraries it relies on - and it will also tell you which it can not find - the two X libraries it is looking for are most likely libX11 and LibXt - make sure both are installed. If you already solved the problem - I would be interested in hearing what it is. One last thought - Have you looked at the servlet code - specifically the makeGraph() method? That is the last method in your code I can see on the stack (the rest are awt stuff) to see if there is any references to a display target? On Tuesday 29 October 2002 17:03, Sudhaker P wrote: > Hi Tim, > Thanks for the reply. > The version of JDK differ the version I'm having issues with is 1.3.1_01 > and the ones the code is running successfully is 1.3.0_02, however the > graphs were being produced before. > The following is the Weblogic log which I'd appreciate if you can look at > and tell what could be the issue in your view: > java.lang.NoClassDefFoundError > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:120) > at > java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironmen >t.java:58) at java.awt.Window.<init>(Window.java:189) > at java.awt.Frame.<init>(Frame.java:315) > at java.awt.Frame.<init>(Frame.java:262) > at com.rivenet.graphingaction.Graphit.runGraph2D(Unknown Source) > at > com.rivenet.reporting.InformalFundingComparisonGraph.makeGraph(Unknown > Source) > at > jsp_servlet._plan._Model_controller._jspService(_Model_controller.java:356) > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav >a:123) at > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextIm >pl.java:761) at > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextIm >pl.java:708) at > weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContex >tManager.java:252) at > weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346) > at > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135) > > I've done some reading and feel that awt uses X-windows and I think that > might be broken. > > I'd appreciate your comments and suggestions. > > Thanks, > > Peram > > > > > > > From: "Keller, Tim" <Tim.Keller(a)stratus.com> > > >Reply-To: wlug(a)mail.wlug.org > >To: "'wlug(a)mail.wlug.org'" <wlug(a)mail.wlug.org> > >Subject: RE: [Wlug] Newbie to mailing list- Issue with the generation of > >graphs in redhat 6.2 > >Date: Tue, 29 Oct 2002 14:45:42 -0500 > > > >Peram, > > > >I'll ask an obvious question... You've verified that both machines running > >the same version of the java run time environment? > > > >Also, does the entire applet fail or does it just fail to display the > >graph. > >If so, you might have to insert some code to catch exceptions... Possibly > >some library has gotten mangled... > > > >Hope that helps, > >Tim. > > > >-----Original Message----- > > From: Sudhaker P [mailto:perams27@hotmail.com] > > >Sent: Tuesday, October 29, 2002 14:35 PM > >To: wlug(a)mail.wlug.org > >Subject: [Wlug] Newbie to mailing list- Issue with the generation of > >graphs in redhat 6.2 > > > > > >Hi , > >I've a program that generates graphs with Java 1.3.1_01. The same program > >is > > > >able to generate graphs on a machine with RH 6.2 kernel 2.4.16 but it > > fails to generate graphs on a machine with RH 6.2 kernel 2.4.7-10 on > > which it used > > > >to generate before. I've installed KDE and gd thinking that something may > >broken in the OS on the jpegs generation part. But that doesn't seem to > >help. > >I'd appreciate if any of you gurus can guide me in this issue with your > >comments and suggestions. > > > >Thanks, > > > >Peram > > > > > > > > > > > > > >_________________________________________________________________ > >Choose an Internet access plan right for you -- try MSN! > >http://resourcecenter.msn.com/access/plans/default.asp > > > > > >_______________________________________________ > >Wlug mailing list > >Wlug(a)mail.wlug.org > >http://mail.wlug.org/mailman/listinfo/wlug > > > >_______________________________________________ > >Wlug mailing list > >Wlug(a)mail.wlug.org > >http://mail.wlug.org/mailman/listinfo/wlug > > _________________________________________________________________ > Internet access plans that fit your lifestyle -- join MSN. > http://resourcecenter.msn.com/access/plans/default.asp > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

Nov. 4, 2002

RE: [Wlug] Routing problem -can I believe the ISP tech? #2

by George Metz

Reply's interspersed: > I just brought up my fourth RH7.3 server Friday afternoon (one of two > RH7.0 servers that had been hacked-new hard drive and software). I > then went home and spent a couple of hours connected to it with ssh > on a workstation connected to my home RH7.3 server. > > When I went to rerun a slightly modified (open ports for ftp and > internal dhcp twiddling) ipchains firewall I lost the connection, > and, more than 16 hours later, don't have it back. Smells like a typo referencing - specifically - Home's IP address or block, based on this. Double and triple check your firewall configs as a first step. If those are clean: > Home and EFO are on the same ISP and each has a block of 4 static > IPs. The blocks share the first 18 bits of their IP#s. Above tidbit might be important later. And actually, they're listing in your config as blocks of 8, with 6 useable. > Home now cannot connect to EFO via ssh, or access its web site. Pings > are disabled on all my servers - so I can't do that test. I STRONGLY recommend that you re-enable ping on both Home and EFO servers in order to perform this test. Firstly, it's really difficult to pingflood a box these days, second, it's a pretty darned useful indicator. This can be gotten around though, so if you're leery - say, you've been pingflooded recently - then skip it. Run a traceroute to Home from EFO and to EFO from Home. That will tell you, at the very least, where the traffic is dying. > EFO network workstations can browse the web; I can ping out from the > EFO linux box or workstations, and can ping EFO's Cisco 678 router > from its Linux box All good here. > EFO workstations cannot access Home websites (but I had not tried > this before since rebuilding EFO Linux box Most likely a symptom of the overall problem, but don't forget to test again. > Home Cisco 678 cannot be pinged from Home Linux box (!) or EFO (Linux > or workstation), but can be pinged from my office (Linux box on other > ISP). Uh... Houston, we have a problem. If the tech IS being straight with you, then the issue has to be on both sites, but one site is severely impairing the other. > >From my office workstation I can also ssh to EFO and access > EFO website (which in fact I uploaded to the new server from my > office today). Does this discount the possibility of a firewall issue? Not even remotely. All it proves out is that there's no rule in the firewall to block access from your office's IP addresses. There still might be a rule in place to block access to and/or from one site to the other. Note also that this is really easy to do accidentally, because one word change can totally break the intended rule. I'll let someone with more IPChains/IPTables experience help with that one. > I spent countless hours talking to the ISP (Qwest) tech support, and > over an hour with a senior tech who had some Linux knowledge, and he > claims that it must be a configuration issue on one or both of my > Home and EFO Linux boxes, since: > > He can login to both my Cisco routers and ping the other router - > he claims this proves its not a Qwest routing problem. Provisionally, this is correct. The provision has to do with whether or not the tech just ran "ping -c 100 ip.for.efo.site" or if he actually did the CORRECT thing and sourced it off of your Ethernet interface on the router. If Qwest is misrouting your allocation, all sorts of things can go wonky. The only way to test that would be to source off the ethernet IP address from both routers to the same. A straight ping will simply do the WAN IP, which (of course) is routed correctly on Qwest's network. I'm not sure about the Cisco 678s, since I never crawled around in one, but if it's running a standard flavor of Cisco IOS, he should be able to source it off of just about anything he wants to. If he's a senior tech with a clue, it's entirely possible that he did source off the ethernet interface, in which case it's back to config issue. > If he's right I'm still puzzled by two things: > a) Why could I connect from Home to EFO for two hours last night, > no problems? > b) Why can't the Home Linux box ping the Cisco 678 directly > connected to it? The former is simple; most likely the error causing the issue was introduced when you made whatever changes you did. The latter has all sorts of interesting possibilities, but there's no way of knowing without having access to both the 678 and the linux box and about an hour to monkey around. I note that you don't mention whether or not Home can access The World At Large, though you do mention it with the EFO site. Also, as I mentioned above, you're showing as having an assigned block of 8 IPs, of which 6 are normally useable. Knock out one for the router, and that leaves 5 assignable. Since 4 IPs is a little wierd, are you sure that you don't have either more and Qwest is just being stubborn, or perhaps they've routed them differently? Others will probably have an idea or two as well, but this to me just screams config error. Which might be why the tech was convinced of it. =)

Nov. 3, 2002

Routing problem -can I believe the ISP tech? #2

by Richard Goodman

My apologies for the HTML, it was not intentional. I was trying to make part of the email more (not less) readable. I've changed options so hopefully it will never happen again. ======== I just brought up my fourth RH7.3 server Friday afternoon (one of two RH7.0 servers that had been hacked-new hard drive and software). I then went home and spent a couple of hours connected to it with ssh on a workstation connected to my home RH7.3 server. When I went to rerun a slightly modified (open ports for ftp and internal dhcp twiddling) ipchains firewall I lost the connection, and, more than 16 hours later, don't have it back. Other relevant details. (let's call the servers Home and EFO) Home was the other hacked server, and was formatted and rebuilt last weekend. Home and EFO are on the same ISP and each has a block of 4 static IPs. The blocks share the first 18 bits of their IP#s. Home could connect to EFO last night Home now cannot connect to EFO via ssh, or access its web site. Pings are disabled on all my servers - so I can't do that test. EFO network workstations can browse the web; I can ping out from the EFO linux box or workstations, and can ping EFO's Cisco 678 router from its Linux box EFO workstations cannot access Home websites (but I had not tried this before since rebuilding EFO Linux box Home Cisco 678 cannot be pinged from Home Linux box (!) or EFO (Linux or workstation), but can be pinged from my office (Linux box on other ISP). >From my office workstation I can also ssh to EFO and access EFO website (which in fact I uploaded to the new server from my office today). Does this discount the possibility of a firewall issue? I spent countless hours talking to the ISP (Qwest) tech support, and over an hour with a senior tech who had some Linux knowledge, and he claims that it must be a configuration issue on one or both of my Home and EFO Linux boxes, since: He can login to both my Cisco routers and ping the other router - he claims this proves its not a Qwest routing problem. If he's right I'm still puzzled by two things: a) Why could I connect from Home to EFO for two hours last night, no problems? b) Why can't the Home Linux box ping the Cisco 678 directly connected to it? I knew nothing about routing before today - here's the Home routing table: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface xxx.yyy.28.48 0.0.0.0 255.255.255.248 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 xxx.yyy.28.54 0.0.0.0 UG 0 0 0 eth0 I tried the following but still could not access EFO (added just the EFO IP#, not the network block: #route add -host xxx.yyy.26.57 dev eth0 # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface xxx.yyy.26.57 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 xxx.yyy.28.48 0.0.0.0 255.255.255.248 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 xxx.yyy.28.54 0.0.0.0 UG 0 0 0 eth0 Is this enough if to decide if the tech is right or crazy? Any suggestions - I still can't access Home from/to EFO. Dick

Nov. 3, 2002

Re: [Wlug] Looking for networking information

by Brett Russ

> Hi, I recently acquired another pc and I want to incorporate it into my > home network. Does anyone know of a website that has information on how to > install and operate a windows based pc on a network? And I am looking for > more information on networking in general. See the linux doc. project website, particularly the guides section here: http://www.tldp.org/guides.html where you will find the Network Administrators Guide which is pretty informative. -Brett

Nov. 3, 2002

Re: [Wlug] ticked at netgear

by Wes Allen

Good advice, never tell them you're using linux. Actually, it is not a hardware problem (though it sure looked like one). Mandrake issued a new version of initscripts that "fixed" wireless network link problems. And I installed it, however, I never rebooted my machine and the interface was already up, so I didn't notice the problem until this afternoon when I turned on my laptop. I read the comments for the updates and found the issue. Updates that break things, I'm having windows flash-backs. Wes On Saturday 02 November 2002 5:42 pm, Wes Allen wrote: > Hi gang, > I've got a ma401 card from netgear. It worked beautifully under linux > (better than in windows even). Today I switch on my laptop, and I no > longer get a link to my network with the card. I figure I must've had a > power glitch and my firewall isn't giving out dhcp address, so I restart > it. Still no link. I check the settings of my wireless router, all good. > I boot my desktop to see if my usb wireless card works, it does. None of > my settings on my laptop have changed, I checked. I tweak with iwconfig > until my hands are sore, no luck. So I finally call netgear because I > figure that it is a hardware issue and I need to send in the card to have > at least the antenna replaced. Tech support says, "I'm sorry but we can > only trouble-shoot on windows so we can't help you." I tell them, "It's > not a software issue, nothing has changed with my software from last night, > everything is the same, the card is not picking up the link from the > router, it's not functioning, it's a hardware issue..." They say, "But we > need to troubleshoot in windows." I say, "Look, I've turned encryption on > and off, I've tried different modes, I've tried different channels, I've > turned rts and frag on and off [note: now it's not accepting values, > another clue that this is a hardware problem]. Nothing works, your card is > broken and I want to send it in." I'm told to hold. "I'm sorry, we cannot > help you. We need to troubleshoot in windows." I slam the phone on the > reciever so hard I think I nearly break it. Now I am pissed, and I still > have a broken card. > > Does anyone else have any history with wireless antennas not working all > of the sudden? This card hasn't even been out of the house, I leave it > here when I go out for crying out loud! > > My next attempt will to disable encryption and go back to wvlan_cs to see > if that jogs this thing. But I truly think it's hardware; nothing, > NOTHING, on my laptop changed, I didn't even turn it on this morning! > > Wes -- ------ This message may be signed using GPG, for my public key please send me a message with "Key Request" in the subject line.

Nov. 3, 2002

Re: [Wlug] non-windows trouble shooting

by Charles R. Anderson

On Sat, Nov 02, 2002 at 05:47:48PM -0500, Karl Hiramoto wrote: karl> They only want to talk to you if you run that windows crap. I just karl> tell myself that the tech-support guys are too dumb to be able to karl> figure out how to do anything with Linux. If you are lucky enough to have experience on the Windows side to know how things work, you can just "pretend" to do what they ask and feed them "fake" information. Worked for me in the past... -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Nov. 2, 2002

Re: [Wlug] non-windows trouble shooting

by Brian J.Conway

> I've had the problem with everything from DSL connections, cable > modems, printers, hard drives, modems etc. I find that it's works out well that if I'm paying for a product or service, anything that I might come in contact with tech support for is platform independent. For instance, I have systems on both AT&T Broadband and Speakeasy DSL, the troubleshooting for which takes place with the computer unplugged and is in no way dependant on the computer/router connected. Obviously there's not much you can do with a device that's plugged into your computer other than keep a Windows partition around or go without support if that's a company's policy, I suppose. > They only want to talk to you if you run that windows crap. I just > tell myself that the tech-support guys are too dumb to be able to > figure out how to do anything with Linux. I just tell myself that as much as I might like Linux, it doesn't make sense to spend the huge amount of resources it would take to be able to officially support an operating system (in all its incarnations) that a minimal percentage of their users use. Speakeasy won't officially support Linux, but their techs are pretty smart and can troubleshoot most issues from their own knowledge. Brian J. Conway bconway(a)alum.wpi.edu "LINUX is obsolete" - Andrew S. Tanenbaum, creator of Minix - Jan 29, 1992

Nov. 2, 2002

non-windows trouble shooting

by Karl Hiramoto

I've had the problem with everything from DSL connections, cable modems, printers, hard drives, modems etc. They only want to talk to you if you run that windows crap. I just tell myself that the tech-support guys are too dumb to be able to figure out how to do anything with Linux. I can partially understand that Linux is more complex than windows, there are way more platforms, kernel versions, distributions and whatever to support. By only supporting windows i suppose they make it idiot proof by reducing the number of variables/complexities. On Sat, 2 Nov 2002, Wes Allen wrote: > Hi gang, > I've got a ma401 card from netgear. It worked beautifully under linux > (better than in windows even). Today I switch on my laptop, and I no longer > get a link to my network with the card. I figure I must've had a power > glitch and my firewall isn't giving out dhcp address, so I restart it. Still > no link. I check the settings of my wireless router, all good. I boot my > desktop to see if my usb wireless card works, it does. None of my settings > on my laptop have changed, I checked. I tweak with iwconfig until my hands > are sore, no luck. So I finally call netgear because I figure that it is a > hardware issue and I need to send in the card to have at least the antenna > replaced. Tech support says, "I'm sorry but we can only trouble-shoot on > windows so we can't help you." I tell them, "It's not a software issue, > nothing has changed with my software from last night, everything is the same, > the card is not picking up the link from the router, it's not functioning, > it's a hardware issue..." They say, "But we need to troubleshoot in > windows." I say, "Look, I've turned encryption on and off, I've tried > different modes, I've tried different channels, I've turned rts and frag on > and off [note: now it's not accepting values, another clue that this is a > hardware problem]. Nothing works, your card is broken and I want to send it > in." I'm told to hold. "I'm sorry, we cannot help you. We need to > troubleshoot in windows." I slam the phone on the reciever so hard I think I > nearly break it. Now I am pissed, and I still have a broken card. > > Does anyone else have any history with wireless antennas not working all of > the sudden? This card hasn't even been out of the house, I leave it here > when I go out for crying out loud! > > My next attempt will to disable encryption and go back to wvlan_cs to see if > that jogs this thing. But I truly think it's hardware; nothing, NOTHING, on > my laptop changed, I didn't even turn it on this morning! > > Wes > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Freedom: http://www.technojihad.com/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 Yahoo_IM = karl_hiramoto ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø I never said all Democrats were saloonkeepers; what I said was all saloonkeepers were Democrats.

Nov. 2, 2002

ticked at netgear

by Wes Allen

Hi gang, I've got a ma401 card from netgear. It worked beautifully under linux (better than in windows even). Today I switch on my laptop, and I no longer get a link to my network with the card. I figure I must've had a power glitch and my firewall isn't giving out dhcp address, so I restart it. Still no link. I check the settings of my wireless router, all good. I boot my desktop to see if my usb wireless card works, it does. None of my settings on my laptop have changed, I checked. I tweak with iwconfig until my hands are sore, no luck. So I finally call netgear because I figure that it is a hardware issue and I need to send in the card to have at least the antenna replaced. Tech support says, "I'm sorry but we can only trouble-shoot on windows so we can't help you." I tell them, "It's not a software issue, nothing has changed with my software from last night, everything is the same, the card is not picking up the link from the router, it's not functioning, it's a hardware issue..." They say, "But we need to troubleshoot in windows." I say, "Look, I've turned encryption on and off, I've tried different modes, I've tried different channels, I've turned rts and frag on and off [note: now it's not accepting values, another clue that this is a hardware problem]. Nothing works, your card is broken and I want to send it in." I'm told to hold. "I'm sorry, we cannot help you. We need to troubleshoot in windows." I slam the phone on the reciever so hard I think I nearly break it. Now I am pissed, and I still have a broken card. Does anyone else have any history with wireless antennas not working all of the sudden? This card hasn't even been out of the house, I leave it here when I go out for crying out loud! My next attempt will to disable encryption and go back to wvlan_cs to see if that jogs this thing. But I truly think it's hardware; nothing, NOTHING, on my laptop changed, I didn't even turn it on this morning! Wes -- ------ This message may be signed using GPG, for my public key please send me a message with "Key Request" in the subject line.

Nov. 2, 2002

Re: [Wlug] Routing problem -can I believe the ISP tech?

by Charles R. Anderson

HTML problem. Who can't read your email? On Sat, Nov 02, 2002 at 05:11:31PM -0500, Richard Goodman wrote: <html> <pre> I just brought up my fourth RH7.3 server Friday afternoon (one of two RH7.0 servers that had been hacked-new hard drive and software). I then went home and spent a couple of hours connected to it with ssh on a workstation connected to my home RH7.3 server. When I went to rerun a slightly modified (open ports for ftp and internal dhcp twiddling) ipchains firewall I lost the connection, and, more than 16 hours later, don't have it back. Other relevant details. (let's call the servers Home and EFO) Home was the other hacked server, and was formatted and rebuilt last weekend. Home and EFO are on the same ISP and each has a block of 4 static IPs. The blocks share the first 18 bits of their IP#s. Home could connect to EFO last night Home now cannot connect to EFO via ssh, or access its web site. Pings are disabled on all my servers - so I can't do that test. EFO network workstations can browse the web; I can ping out from the EFO linux box or workstations, and can ping EFO's Cisco 678 router from its Linux box EFO workstations cannot access Home websites (but I had not tried this before since rebuilding EFO Linux box Home Cisco 678 cannot be pinged from Home Linux box (!) or EFO (Linux or workstation), but can be pinged from my office (Linux box on other ISP). >From my office workstation I can also ssh to EFO and access EFO website (which in fact I uploaded to the new server from my office today). Does this discount the possibility of a firewall issue? I spent countless hours talking to the ISP (Qwest) tech support, and over an hour with a senior tech who had some Linux knowledge, and he claims that it must be a configuration issue on one or both of my Home and EFO Linux boxes, since:   He can login to both my Cisco routers and ping the other router - he claims this proves its not a Qwest routing problem. If he's right I'm still puzzled by two things: a) Why could I connect from Home to EFO for two hours last night, no problems? b) Why can't the Home Linux box ping the Cisco 678 directly connected to it? I knew nothing about routing before today - here's the Home routing table: <tt>route -n Kernel IP routing table Destination     Gateway         Genmask         Flags Metric Ref    Use Iface xxx.yyy.28.48   0.0.0.0         255.255.255.248 U     0      0        0 eth0 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo 0.0.0.0         xxx.yyy.28.54   0.0.0.0         UG    0      0        0 eth0 </tt>I tried the following but still could not access EFO (added just the EFO IP#, not the network  block: <tt>#route add -host xxx.yyy.26.57 dev  eth0 # route -n Kernel IP routing table Destination     Gateway         Genmask         Flags Metric Ref    Use Iface xxx.yyy.26.57   0.0.0.0         255.255.255.255 UH    0      0        0 eth0 xxx.yyy.28.48   0.0.0.0         255.255.255.248 U     0      0        0 eth0 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo 0.0.0.0         xxx.yyy.28.54   0.0.0.0         UG    0      0        0 eth0 </tt>Is this enough if to decide if the tech is right or crazy? Any suggestions - I still can't access Home from/to EFO. Dick </pre> </html> _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Nov. 2, 2002