|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
I wanted to add that I am using an Ethernet crossover cable .
ifconfig -A print. Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33200 priority: 0 groups: lo inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:0d:b9:1c:96:80 priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::20d:b9ff:fe1c:9680%vr0 prefixlen 64 scopeid 0x1 inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255 vr1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:0d:b9:1c:96:81 priority: 0 media: Ethernet autoselect (100baseTX full-duplex) status: active enc0: flags=0<> priority: 0 groups: enc status: active pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33200 priority: 0 groups: pflog |
|
|||
First i think i should get an ip address to the network card inside my laptop Through the network cable in port vr1 .
Secondly - cat /var/log/daemon print . Code:
Oct 20 11:37:45 ecbox savecore: no core dump Oct 20 18:45:00 ecbox savecore: no core dump Oct 20 18:57:21 ecbox dhclient[27753]: ioctl(SIOCGIFFLAGS) on fxp0: Device not configured Oct 20 18:57:29 ecbox dhclient[702]: DHCPREQUEST on vr0 to 255.255.255.255 port 67 Oct 20 18:57:29 ecbox dhclient[702]: DHCPACK from 192.168.1.1 (00:22:6b:7b:7e:68) Oct 20 18:57:29 ecbox dhclient[32743]: routehandler: interface address deleted Oct 20 18:57:29 ecbox dhclient[702]: bound to 192.168.1.102 -- renewal in 43200 seconds. Oct 20 19:07:30 ecbox savecore: no core dump Oct 20 19:07:31 ecbox dhcpd[27321]: Can't listen on vr1 - it has no IP address. Oct 20 19:07:31 ecbox dhcpd[27321]: No interfaces to listen on. Oct 20 19:07:31 ecbox dhcpd[27321]: exiting. Oct 20 19:32:10 ecbox dhcpd[29767]: Can't listen on fxp0 - it has no IP address. Oct 20 19:32:10 ecbox dhcpd[29767]: No interfaces to listen on. Oct 20 19:32:10 ecbox dhcpd[29767]: exiting. Oct 20 19:32:17 ecbox dhcpd[25136]: Can't listen on vr1 - it has no IP address. Oct 20 19:32:17 ecbox dhcpd[25136]: No interfaces to listen on. Oct 20 19:32:17 ecbox dhcpd[25136]: exiting. Oct 20 19:32:25 ecbox dhcpd[23654]: Can't listen on vr1 - it has no IP address. Oct 20 19:32:25 ecbox dhcpd[23654]: No interfaces to listen on. Oct 20 19:32:25 ecbox dhcpd[23654]: exiting. Oct 20 19:55:41 ecbox savecore: no core dump Oct 20 19:55:42 ecbox dhcpd[13655]: Can't listen on vr1 - it has no IP address. Oct 20 19:55:42 ecbox dhcpd[13655]: No interfaces to listen on. Oct 20 19:55:42 ecbox dhcpd[13655]: exiting. Oct 20 20:02:33 ecbox dhcpd[29108]: Can't listen on fxp0 - it has no IP address. Oct 20 20:02:33 ecbox dhcpd[29108]: No interfaces to listen on. Oct 20 20:02:33 ecbox dhcpd[29108]: exiting. Oct 20 20:02:39 ecbox dhcpd[4807]: Can't listen on vr1 - it has no IP address. Oct 20 20:02:39 ecbox dhcpd[4807]: No interfaces to listen on. Oct 20 20:02:39 ecbox dhcpd[4807]: exiting. Oct 20 20:02:44 ecbox dhcpd[21725]: Can't listen on vr1 - it has no IP address. Oct 20 20:02:44 ecbox dhcpd[21725]: No interfaces to listen on. Oct 20 20:02:44 ecbox dhcpd[21725]: exiting. Oct 20 20:04:43 ecbox savecore: no core dump Oct 20 20:04:44 ecbox dhcpd[24328]: Can't listen on vr1 - it has no IP address. Oct 20 20:04:44 ecbox dhcpd[24328]: No interfaces to listen on. Oct 20 20:04:44 ecbox dhcpd[24328]: exiting. Oct 20 20:11:51 ecbox dhcpd[21028]: Can't listen on start - it has no IP address. Oct 20 20:11:51 ecbox dhcpd[21028]: No interfaces to listen on. Oct 20 20:11:51 ecbox dhcpd[21028]: exiting. |
|
|||
Quote:
$ cat /etc/hostname.vr1
|
|
|||
$ cat /etc/hostname.vr1
cat: /etc/hostname.vr1: No such file or directory |
|
||||
You must assign a static IP address for this network segment. It must be in a different IP subnet from the segment attached to vr0. You do this by creating the missing file. See FAQ 6.2.1. Your pool of address in your dhcpd.conf must be in this same subnet.
|
|
|||
What's the output that you was expected from this commandes
$ cat /etc/hostname.vr1 I do not understand why I need to set a static address on port vr1. I think when I set dhcp server is supposed to give a ip address to the laptop network card . |
|
|||
The DHCP server should have it's own IP statically assigned.
dhcpd(8) uses this information to determine which interface it should listen for DHCP requests on. |
|
||||
The output expected is an IPv4 configuration file that you or Igor create. As described in FAQ 6.2.1 and the man page referred to you there. Please spend time with the FAQ, it will save you from yourselves if you do.
If you need help with basic networking concepts, please look for a book on TCP/IP written in your language. |
|
|||
Quote:
Then, you need to study the DHCP protocol. There are multiple sources you can use to study. Some obvious choices include:
|
|
|||
question:
How does openBSD determin if a an internet connection is down (by down i mean the ISP has a problem), does it wait until a request is sent to the internet and is not replied for some time? or does it sends constant pings to some server to test the connection? |
|
|||
Quote:
Please see http://www.daemonforums.org/showpost...0&postcount=38 for a suggestion to take a step-by-step approach.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump Last edited by ocicat; 21st October 2011 at 11:19 AM. Reason: fixed link |
|
||||
Please refer to ifstated.conf(5), where you will see both internal state changes (NIC status) and external (user defined) tests.
Last edited by jggimi; 21st October 2011 at 01:36 PM. Reason: clarification |
|
|||
Quote:
While I agree that these issues will eventually need to be addressed, if the goal of your project is to construct a device capable of failing over from one ISP to another, none of the 5 months you have spent on this project will amount to anything unless you know & can demonstrate that you can connect wirelessly. J65nko attempted to help you prioritize what needs to be done in the following: http://www.daemonforums.org/showpost...0&postcount=38 It does not appear that you have made any progress on confirming whether you can connect through this USB device. While it is your choice to work through the issues involved in the project in whatever manner you wish, it would seem to me that you should take care of the most critical items first. Otherwise, if you are unable to connect through a secondary conduit, the goal of your project has not been met & you have simply wasted your time. I recommend that you spend time studying PPP connections as described in Section 6.5 of the FAQ very soon. Studying the relevant manpages will help too. It will also be beneficial to search for PPP discussions on the official misc@ mailing list. Archive sites can be found at the following: http://www.openbsd.org/mail.html Studying these sources will far be more useful than trying to find shortcuts by searching for howto documents. Most information found on the Internet is either old, incomplete, or simply wrong. Staying with information & discussions on the OpenBSD project or its mailing lists is much more likely of being correct & current. |
|
|||
Does anyone know if there's a software using which I can simulate my stay alive algorithm for two ISP connections? - to see if it works correctly, not on my board but virtually.
|
|
||||
Sigi, you can build a network of interconnected virtual machines for this sort of testing. If your host is OpenBSD, emulators/qemu is the recommended solution.
You will need, at minimum, five systems on four subnetworks. If you have questions about running qemu with OpenBSD as a host, or using qemu with virtual (or real) network interconnections, please start a new thread. |
Thread Tools | |
Display Modes | |
|
|