Okay just to clarify - I've yet to get to the web interface. No matter what I do it says it can't find that host.
>Of course you need to manually configure an ip address on your >workstation. Under linux the following should work: >ifconfig eth0 up >ip addr add 192.168.1.200/24 dev eth0 >ip route add default via 192.168.1.1 Well here's the result of that (on my client)! [EMAIL PROTECTED] mbrown]# ifconfig eth0 up [EMAIL PROTECTED] mbrown]# ip addr add 192.168.1.200/24 dev eth0 [EMAIL PROTECTED] mbrown]# ip route add default via 192.168.1.1 RTNETLINK answers: File exists [EMAIL PROTECTED] mbrown]# I don't quite understand any of that. Well, I understand that ifconfig eth0 up brings up eth0, but the rest of it is kinda chinese to me. So, once again 1) I've installed IPCOP 2) I've setup the network cards 3) I set it up as a DHCP server in the install (how do I get back to those settings anyways?) 4) It's been rebooted 5) I can't get to it :-/ My computer fails to get the IP information from ifup it just times out 6) well.. We already saw the result of that stuff you gave me! On 5/15/06, Gustin Johnson <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > Mitchell Brown wrote: > > You guys, after your lovely presentation insipred me to set one up of my > > own. Okay, the install went smooth. > > I've got two network cards in it, and I've correctly identified them as > > green and red. Now, when I plug a machine into my green interface, and > > try and ifup it, it cant get an IP from the DHCP server! I set it up to > > act as it (although I can no longer find the menu to change it :-/) but > > it still doesn't see the machine. > > > In the web GUI, click: Services -> DHCP server > > > Even though I couldn't get an IP, I tried going to http://192.168.1.1:81 > > (The IP I gave it) and, not surprisingly, it failed. > > > https://192.168.1.1:445 > > Of course you need to manually configure an ip address on your > workstation. Under linux the following should work: > ifconfig eth0 up > ip addr add 192.168.1.200/24 dev eth0 > ip route add default via 192.168.1.1 > > Windows should be straight forward (look in tcp/ip properties on the > appropriate Ethernet device). > > If all of this fails, log in to your ipcop box (try ssh, or directly via > the console aka keyboard :) and issue a reboot command. > > Also, make sure that there is no other device on the LAN with the same > IP address. > > Oh, and finally, check all the cabling. Physical issues can cause > sleepless nights if you don't look for them. > > > Suggestions anyone? > > > > -- > > pub 1024D/9091C422 02/05/2006 Mitchell Brown <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> > > Primary key fingerprint: 812B 94BC EA0D 345A CC1C 2ED9 F7F6 5CCF > > 9091 C422 > > > > > > ------------------------------------------------------------------------ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFEaS6AwRXgH3rKGfMRAjaeAJwNv8mMZaENDD4OXDkl1iTfoPvRQACdGslc > qpR4QaRbS9lO69ndr8MUaL0= > =APJK > -----END PGP SIGNATURE----- > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > -- pub 1024D/9091C422 02/05/2006 Mitchell Brown <[EMAIL PROTECTED]> Primary key fingerprint: 812B 94BC EA0D 345A CC1C 2ED9 F7F6 5CCF 9091 C422 _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
