Green Connection problems

par **PeteB** » 04 Mars 2004 01:34

I have been struggeling with IPCOP for the past few night, and need some help. I want to run a set up with a single NIC and a USB modem. My IPCOP server can not be reached with a browser or pinged. Its console reports that "Network is unreachable" when I try to ping any PC other than itself. I get the same results on two different PC's, with both IPCOP 1.3 and 1.4 (One of the PC's runs both W2K and Suse Linux 9.0 without any network probs, the other is an old P166 in which I have tried several different model NICs) I am a beginner with Linux and not used to trouble shooting with it. ifconfig show the presence of the NIC as eth0 ping to itself (192.168.1.1) works as expected. After I run ifconfig eth0 192.168.0.255 to change the address the ping results change: For a valid IP address on my network the console will show (for example) PING 192.168.0.1 (192.168.0.1) from 192.168.0.255 : 56(84) bytes of data but there will be no response. (no error message either) If I enter a non existing IP address I get (After a similar message to the above): From 192.168.0.255: Destination Host Unreachable My Conclusion: There is communication. (And from the variety of hardware and IPCOP versions used: That I am probably doing something wrong rather then faced with a hardware problem.) I did at one time get e response on the browser, when I started, however at that time I was quite confused as to how the USB ports came into play, so started all over and do not recall what I might have done different. (I suspect inclusion of orange and red NICs) Any help will be most welcome. Pete

par **betamax** » 04 Mars 2004 04:14

Hi, 192.168.0.255 is the adress to broadcast...dont works have you enable dhcp ??? on your ipcop. otherwise you must to put a static ip in the others PC : ex 192.168.1.2 regards

par **Franck78** » 04 Mars 2004 05:04

In most case it's red interface/dsl authentication with provider wich causes trouble !!! ifconfig show the presence of the NIC as eth0 ping to itself (192.168.1.1) works as expected. Is a good address. Why change it (to an invalid one by the way) ? You have another machine with this ip is only reason. You are very beginner with ip (not only linux). GREEN ipcop cannot use DHCP. Maybe you have DHCP server active (the Suse?) On Suse machine read it's IP add 10 to the last number. example : 192.168.1.3 => 192.168.1.13 Read the mask (255.255.255.0 classic) On ipcop1.4 console #:setup modify Green interface with your new address/mask validate Now you can ping the Suse machine. Go to it Start your browser, enter <a href="https://192.168.1.13:445" target="_blank">https://192.168.1.13:445</a> Enjoy Ah oui : c'est fatiguant le ricain. Essaie le Français ! Bye _________________ Franck <IMG SRC="images/smiles/icon_wink.gif">

par **JaDiuM** » 04 Mars 2004 07:21

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD>En réponse à:<HR></TD></TR><TR><TD><BLOCKQUOTE> Le 2004-03-04 00:34, PeteB a écrit: I have been struggeling with IPCOP for the past few night, and need some help. I want to run a set up with a single NIC and a USB modem. My IPCOP server can not be reached with a browser or pinged. Its console reports that "Network is unreachable" when I try to ping any PC other than itself. I get the same results on two different PC's, with both IPCOP 1.3 and 1.4 (One of the PC's runs both W2K and Suse Linux 9.0 without any network probs, the other is an old P166 in which I have tried several different model NICs) I am a beginner with Linux and not used to trouble shooting with it. ifconfig show the presence of the NIC as eth0 ping to itself (192.168.1.1) works as expected. After I run ifconfig eth0 192.168.0.255 to change the address the ping results change: For a valid IP address on my network the console will show (for example) PING 192.168.0.1 (192.168.0.1) from 192.168.0.255 : 56(84) bytes of data but there will be no response. (no error message either) If I enter a non existing IP address I get (After a similar message to the above): From 192.168.0.255: Destination Host Unreachable My Conclusion: There is communication. (And from the variety of hardware and IPCOP versions used: That I am probably doing something wrong rather then faced with a hardware problem.) I did at one time get e response on the browser, when I started, however at that time I was quite confused as to how the USB ports came into play, so started all over and do not recall what I might have done different. (I suspect inclusion of orange and red NICs) Any help will be most welcome. Pete </BLOCKQUOTE></TD></TR><TR><TD><HR></TD></TR></TABLE> Hello pete, You have many errors in your configuration. I try to explain myself: The best way of integrating this system is to make an inventory of the configurations of all your PCs: Ex: If your network (customers) use an adressing like 192.168.0.0/24, you must have a green IP of the same type (IPcop side: 192.168.0.1). Note that 192.168.0.255 is the broadcast of this network and thus consequently not usable directly on NIC PC. Try Something like that: IPCOP PPP0: RED Modem USB DHCP IPCOP eth0 : GREEN 192.168.0.1 mask: 255.255.255.0 W2K: 192.168.0.2 mask 255.255.255.0 Gateway 192.168.0.1 Suse: 192.168.0.3 mask 255.255.255.0 Gateway 192.168.0.1 (To use Orange network you must have a second NIC installed on IPCOP !!!) Hope it's help you. Regards _________________ ---------------------------------- "Computers are like air conditionners. They stop working properly when you open Windows" ----------------------------------

par **PeteB** » 05 Mars 2004 10:18

Thanks & Merci for the responses I started from skratch: Ipcop box plus one other PC on the hub and got the Green site working as expected except that if I enter 192.168.1.1 as address during the IPCOP install it will not work. 192.168.0.1 or 192.168.0.10 does work. This is not really a prob, but I would like to understand. (The adress of the second PC on the hub is 192.168.0.9) Now the RED side: Is 1.4.0.1a compatible with a Sagem 800 (Free.fr) (I write french like a cow would write spanish, but have no problem reading it.) Pete

par **Gesp** » 05 Mars 2004 10:56

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD>En réponse à:<HR></TD></TR><TR><TD><BLOCKQUOTE>I started from skratch: Ipcop box plus one other PC on the hub and got the Green site working as expected except that if I enter 192.168.1.1 as address during the IPCOP install it will not work. 192.168.0.1 or 192.168.0.10 does work. This is not really a prob, but I would like to understand. (The adress of the second PC on the hub is 192.168.0.9) </BLOCKQUOTE></TD></TR><TR><TD><HR></TD></TR></TABLE> It's may work but depend of the netmask you set. -with usual netmask 255.255.255.0, only 192.168.0.x adresses are on the same subnet, so you can address 253 other ip addresses from your ipcop (256 minus 0,255 and ipcop green address) - with larger netmask 255.255.0.0, all 192.168.x.y adresses are on the same subnet and you can address 254*254-1 other IP addresses. Yes V1.4.0a1 work with Free ISP in both flavors (dégroupé with routedIP Vcmux and standard settings with PPPoA VCmux or PPPoE LLC)

Green Connection problems

Qui est en ligne ?