Re: Ipcop won't connect after power failure
s baker <[email protected]>
| Newsgroups | gmane.comp.security.ipcop.user |
|---|---|
| Message-ID | <[email protected]> |
I actually have a hub between ipcop and the verizon router, so that probably isn't it. The strange thing is that clicking disconnect, then connect works. I played with removing files /var/run/dhcp* and /var/ipcop/red/* before bringing up networking, but that didn't help at all. I found that rc.red was throwing an error after trying to start the dhcpcd daemon, but only when I clicked connect, not on boot. After playing with it for a while and not figuring it out, I have changed to a static address on red, which works fine. Thanks for the ideas. If someone who knows how this is supposed to work wants to try to fix this I'm willing to try more things in the spirit of fixing ipcop, otherwise I'll stick with a static red address. > > Sounds like the DHCP is not being fully torn down during restart. Had > this error YEARS AGO on smoothwall with DHCP on ethernet. I had delete > the information in /etc/dhcp (* please do not trust the path name doing > it from almost 20yrs of memory!) during boot to correct it. DHCP > clients normal ask to reused the last IP it had, but that was problem > with ISDN modems in the day. By removing the contents of /etc/dhcp (*), > it forced the card to be FULL rebooted and DHCP to start from scratch > and get clean IP assigned. I placed in the "rm -R /etc/dhcp/*" (*) in > the boot script. > > How is RED connected to Verizon WiFi? Is it via an ethernet cable? OR > do you have another method? > > If via ethernet, I would suggest you try to install a ether-switch > between them. What you may be seeing is that Verizon WiFi is holding > the ethernet port UP/ON, so to itself, it is not seeing IPCOP is > signaling to reconnect, since DHCP client tries to reuse the old IP. At > the same time the IPCOP looks like it is working, but nothing is being > responded right, so it waits for something to happen. The switch will > break the connection with the null-cable between two pieces of equipment > and allow for each to act "right". > > If another like "modem", then that DHCP clear trick may solve it. > > Both are just thoughts. > > jackb > ------------------------------------------------------------------------------ _______________________________________________ IPCop-user mailing list [email protected] Manage your subscription or unsubscribe https://lists.sourceforge.net/lists/listinfo/ipcop-user