• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help! Klinux - Network is unreachable

D

divide by zero

Golden Member
OK, trying to set up the first node on my internal LAN.

I have W98SE box with a modem running a pProxy.
It has a NIC with address 192.168.1.1 for talking internally.
Subnet mask 255.255.255.0 Gateway and DNS left empty

Using a Linksys 4-port switch. The W98SE box is plugged into
port 1. All three lights are lit for port 1: Link/Act, 100, Full/Col. For port two just one light is lit: Link/Act.

The node is an Abit BP6, 2x366@550 with an 3C503 NIC running
Klinux 2.2 (no DHCP). Ran netconfig, assigned address 192.168.1.2, subnet mask 255.255.255.0, left gateway and DNS blank.

I get:
SIOCSIFFLAGS: Try again
Usage: inet_route ...

On the Klinux setup page it said that the gateway and DNS are optional. When the client tries to fetch blocks from 192.168.1.1 it says:
Connect to host 192.168.1.1:2064 failed
Error 101 (Network is unreachable)

The node can ping itself using the 192.168.1.2 address.

I tried swapping network cables, CAT 5, straight through.

Any suggestions?
 
divide_by_zero,

Are you sure you 98SE machine's NIC is assigned 192.168.1.1? I could be wrong, but I think that address is reserved as a gateway address.



<< Subnet mask 255.255.255.0 Gateway and DNS left empty...left gateway and DNS blank. >>



Again, I could be wrong, but I think you must assign some sort of gateway when setting up a network and, just like the netmask, this needs to be the same on all the machines.

Russ, NCNE

 
Divide_by_Zero - edit the Hosts file in c:\windows on your 98SE and /etc/hosts on the other box if Klinux has it there, so both machines know each other and can get to each other. Usually windud has a Hosts.sam file that you can use as a template to edit, but make sure it gets saved without the &quot;.sam&quot; extension.

Russ - since it sounds like his whole setup is focussed for internal use (and his net connection to the outside via the modem would pick up a real IP via DHCP from his ISP), then it'll work without a DNS internally - but that is assuming that the hosts files are populated.
 
Poof,

I wasn't concerned about DNS. With Klinux, this will simply default to whatever gateway he assigns. The gateway itself is what I was wondering about. Even internal networks use this? Don't they?

Russ, NCNE
 
Since the node is referring to the pproxy using the IP address I don't think the host files come into play.

Any idea why I'm getting that error right out of netconfig?
 
Russ - the gateway is only needed if you're going from one network to another (basically a gateway is the same as a router).

Divide_by_Zero - heh... ain't linux networking fun? Yeah you're right... if you're just blapping from one IP to another, it should work.

I used to use netconfig (which is actually a good way to do it) but I now just do my net configurations manually.

I know that Kilowatt really stripped that sucker down to get it to fit on a floppy but see if you can do an &quot;ifconfig&quot; at a prompt. If it only gives you a &quot;lo&quot; entry and a bunch of stuff and no &quot;eth0&quot; entry and stuff too, then the netconfig didn't take. Also you may have to put a static route in there to get you to always look to that pproxy machine but we might want to take one step at a time...

Try the other first and let me know...


 
...And since I'm impatient even with myself... 😉

The next step would be to do the following at a prompt:

route add -host 192.168.1.1

Depending on the version of the route that's there, if that doesn't work, you might have to use:

route add -host 192.168.1.1 eth0

The above will setup a static route to the pproxy from the client.
 


<< the gateway is only needed if you're going from one network to another >>



Poof,

HeHe. Of course, you're right. OOPS!



<< I know that Kilowatt really stripped that sucker down to get it to fit on a floppy but see if you can do an &quot;ifconfig&quot; at a prompt. >>



Yes, he was able to include ifconfig in the distro.

divide_by_zero,

I'm still wondering, though, if 192.168.1.1 is actually the IP address assigned to the 98SE machine. Is that the address that comes up when you run winipcfg?

Russ, NCNE
 


<< Poof, HeHe. Of course, you're right. OOPS! >>


That's okay... I get confused too - like with the Hosts file thing... 😉

(BTW, I just bought a mobo off of you this morning so you have assimilated me without even knowing it!! 😉)

And Divide_by_Zero - ditto on what Russ said. Windud can get so screwed up that your IP stack might not be bound to both the modem and NIC, which in your case, has to happen... And please do check winipcfg to make sure the NIC is being assigned that address!!!
 


<< BTW, I just bought a mobo off of you this morning so you have assimilated me without even knowing it!! >>



Poof,

Cool.🙂 You know, I figured I'd get in today and be able to lazy around all day since it's two days before Christmas. For some reason, though, I got a BUNCH of orders in.😀

divide_by_zero,

I just checked, and 192.168.1.1 IS an assignable address. I thought it might be an indentifier or gateway, but it's the first assignable. Do check, though, and make sure it's the one Windows is using.

Russ, NCNE
 
I'm assuming that each machine can ping itself and each other.

Check the listen address and port in the pproxy ini file. Here is a paste of mine that is in a dual NIC server, with one port to the 'net, and the other to my LAN.

[KeyServer]
ipaddress=jator.2y.net
port=2064
connectperiod=600
connectivity=normal
bindip=24.9.x.x
;uuehttpmode=0
; 0=normal,1=uue,2=http,3=http+uue
; 4=socks4,5=socks5,6=genproxy,7=genproxy+uue
;httpproxy=wwwproxy.corporation.com
;httpport=8080
;httpid=

[ports]
listenaddress=
port=2064
;port2=23 ; must be root for ports < 1000
;port3=80
testport=3064
timeout=30

Also, in your Klinux config, did you enter the IP address of 192.168.1.1 in the keyserver<->client connectivity options?

Another common problem with the 192.168.x.x IPs is dislexia sp??
Getting the numbers turned around.

BTW, Win98SE can act as a DHCP server when ICS is installed.

viz
 


<< Cool. You know, I figured I'd get in today and be able to lazy around all day since it's two days before Christmas. For some reason, though, I got a BUNCH of orders in >>



LOL! Consider it a very merry Christmas present! 🙂 I also pointed a few of my co-workers your way too...

And Viz -

<begin crack>

I'm gonna crack on you and be a Linux snob for a sec and ask why, pray tell, would someone want to make a server outta 98SE????? 😉 Especially when the DHCP server stuff is half broken on NT 4.0 Enterprise server as it is, let alone what might happen with something similar on 98SE! 😉 And even then, I can see me, with 10 machines sitting here in my livingroom (with the parts for an 11th on the way), using DHCP (which I don't). But for a 2-machine LAN, isn't DHCP a bit of overkill??? 😉

</end crack>

(*snicker*)
 
Poof-

Overkill on a 2 computer LAN? Yes! But it does automate one part of the Klinux setup process to a neophite that is running ICS, a very popular application on home networks.
I too have a dozen or so machines running around the house, and have on occasion assigned the same IP to two of them. DHCP does help to avoid those problems.

It sure is great to see so many people make use of Klinux for their cracking addiction though.

viz
 
Thanks, Poof, I'll try the ifconfig. When I get the error it suggests using inet_route which I assume is the same as route?

Yes, in winipcfg I select the network card and see 192.168.1.1 just as I set it. When I'm logged in via the modem I can also select PPP and see the address assigned to me by my ISP.

Yes, I've configured the client to look to 192.168.1.1 but this problem pops up prior to even running the client.

Thanks for the help! I'll try it out in a day or two when I have access to my machines again. They're not at home.
 
Divide_by_Zero - yeah, the &quot;inet_route&quot; is referring to the route command. Hopefully adding a static route from client to host will fix it right away. In most cases, you never need to do that, but I know I have a couple machines here where I have to... never figured out what was different except maybe the versions of the network proggies...

And Vizy - I know what you mean about keeping track of IPs so you don't end up with duplicates. We have that prob at work, DESPITE running Winblows NT's DHCP server. Problem is 95 and 95 almost exclusively (which has tendency to grab an address and then refuse to release it to get a new one, despite using winipcfg's release all/renewall, rebooting, etc.).

If anything, setting up DHCP scopes, etc., is a good learning experience for newbies... 😉 It's just that except for my primary linux notebook which occassionally travels and dual boots, and my 2 windud machines, one of which has to be rebooted at least once a week, the rest are never booted, with uptimes > 100+ days. So in a way, running a DHCP server would basically be a waste of cycles... 😉

I do have win2K advanced server here that has a DHCP server running on it but I haven't bothered...

Anyway - have a good holiday! 😀
 
Hey! I like DHCP; I'm lazy.🙂 It makes my crack rack MUCH more convenient. But, I do have my two Linux servers manually configured. Just don't ask me to explain how the hell I got them working.:Q

Russ, NCNE
 
Viztech, Yes the machines can ping themselves but No, they cannot ping one another.

I did the ifconfig and I only get an entry for lo, the loopback.
So the netconfig did not take? The node can ping itself on 192.168.1.2 which I set in netconfig.

When I did a:
route add 192.168.1.100
It says no such device so:
route add 192.168.1.100 eth0
gives: Network down

So I guess the netconfig did fail. How to force it?

I tried a different 3C503 (same kind of NIC) and yielded the same result. This is an ISA NIC 10Mbps. I'm using CAT 5 cable with RJ-45 connectors. They are backward compatible with RJ-11 aren't they?

So how to force the netconfig?
 


<< backward compatible with RJ-11 aren't they? >>

What the hell cables are you tring to use? :Q
Are they home made cables by chance? Maybe the wires aren't conected good enough to the plugs.

Did Klinux find the nic when you booted? Watch the screen as it boots.
I'm not familer with that perticular nic, is it PNP of does it have jumpers?

You are not pluged into the uplink port? /me knows you're not stupid, but just checking

Go ahead and enter the Gateway &amp; DNS as 192.168.1.1 in &quot;netconfig&quot; it won't hurt anything.

I don't know how to &quot;force it&quot;, just fill it out, and hit the enter key, it writes to the needed file.
 
By &quot;forcing it&quot; I mean just manually assigning an IP at a prompt using the ifconfig command rather than the netconfig proggy, ie.,:

ifconfig eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255

Once that's set, you can do &quot;ifconfig&quot; by itself again to make sure you have both &quot;lo&quot; and &quot;eth0&quot; info displayed... then you can do the route command to setup a static route to the pproxy (this is only if doing manual IP assignment still doesn't let you connect to the pproxy):

route add -host 192.168.1.1 eth0
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top