Sponsored Content
Operating Systems Linux Debian Dhcp not getting configured on Ubuntu Post 302971420 by lazerz on Wednesday 20th of April 2016 03:08:19 AM
Old 04-20-2016
Dhcp not getting configured on Ubuntu

I have kali running on vbox as :-

Quote:
DISTRIB_ID=Kali
DISTRIB_RELEASE=kali-rolling
DISTRIB_CODENAME=kali-rolling
DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
/etc/network/interfaces
Quote:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback
#iface eth0 inet dhcp

auto eth0
iface eth0 inet dhcp

ifup eth0 gives me
Quote:
Listening on LPF/eth0/08:00:27:fa:25:8e
Sending on LPF/eth0/08:00:27:fa:25:8e
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
tpcdump

Quote:
00:53:31.212388 08:00:27:fa:25:8e > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:fa:25:8e, length 300
00:53:43.828472 08:00:27:fa:25:8e > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:fa:25:8e, length 300
00:53:43.904128 bc:85:56:86:57:6e > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 10.25.0.81.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:85:56:86:57:6e, length 300
 

10 More Discussions You Might Find Interesting

1. Slackware

LDAP not getting configured!!!

hi, i m tryin to learn ldap. but its not getting configured. the error msg it shows is: LDAP configure error: BDB/HDB : Berkeley DB version incompatibe. The BDB version i have installed is bdb4.2.52 and the ldap version is openldap-2.3.12. my machine is running on red hat linux 9. Why... (1 Reply)
Discussion started by: mridula
1 Replies

2. UNIX for Advanced & Expert Users

Configured sftp still requires password

Hi Gurus:) I have to connect from a SunOS 5.10 to a 5.8 using sftp in BatchMode. For this, I have generated a Public-Key (ssh-keygen -b 1024 -P "" -t dsa) on the 5.10 and saved it in ~remote-user/.ssh/authorized-keys on the 5.8. Then, running either one of ssh or sftp, it asks for the... (24 Replies)
Discussion started by: unilover
24 Replies

3. Solaris

solaris 10 u5 what happens if no default route configured

Hi, I am new to solaris 10. What is the procedure the os takes if a default route is not configured? I am using a multihomed server with 4 interfaces. It looked strange to me this morning, because i had not defined a default route it defaulted to making one up, with the ip address of another... (9 Replies)
Discussion started by: borderblaster
9 Replies

4. UNIX for Advanced & Expert Users

Working in new IP segment, But Product configured with another IP??

Dear all, We have installed one of our product in a HP PC server(DL380G5)/SUSE 10 SP1 (2 network cards) with an IP address 10.18.7.25. The Product is working fine. Now for giving a internet based demo, we have moved to a different network(192.168.50.*) For the demo, we want to use... (0 Replies)
Discussion started by: jagannathks
0 Replies

5. Red Hat

How to Find what HBA is configured on Linux?

Hi I am working in an environment where there are many redhat physical and virtual machines, mostly Redhat 4. These servers have LUNs attached. The external storage can be EMC, NetApp or Par3. My question is that when Storage Administrator informs that a new LUN has been presented to a... (4 Replies)
Discussion started by: Tirmazi
4 Replies

6. Solaris

Default route is configured, but seem to not work

Hiya, I got the default gateway set in /etc/defaultrouter file, however "netstat -nr" doesn't show anything like "default" in the routing table. As far as I know "netstat" on Solaris 10 u7 should show something like : Routing Table: IPv4 Destination Gateway Flags Ref ... (8 Replies)
Discussion started by: TomSu
8 Replies

7. IP Networking

Get DHCP relay interfaces IP address using DHCP

Hi All , please view the set up below: ------------------------------------------------------------------- | DHCP Server |-----------| ROUTER & |-----------| Clients | | 192.168.99.1 | - -<eth1>| DHCP-RELAY|<eth2>-- | 192.168.88.X | ... (2 Replies)
Discussion started by: gdangoor
2 Replies

8. AIX

Get details of the existing configured printer

I need to get the domain under which a printer is configured in an AIX machine. I have the IP address of the printer. Could you please help me with that? (3 Replies)
Discussion started by: Pandee
3 Replies

9. IP Networking

IP not configured is being used to login

Hi have a solaris server with the following IP 192.168.0.85, but anybody can login in using 172.19.0.85, and the ifconfigcommand does not show the 172.19.05 . # ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask... (6 Replies)
Discussion started by: fretagi
6 Replies

10. Ubuntu

Ubuntu Server in VM - DHCP Server not working

Hello. Doing my first steps in Linux and while trying to configure a DHCP server in Linux i encountered some problems: TOPOLOGY: - Laptop with Windows 8.1 - VM Player 12 with Linux installed (Ubuntu Server 14.04) - ICS-DHCP-SERVER installed and running - Another LAPTOP conected to a... (1 Reply)
Discussion started by: Portuguevos
1 Replies
appender_type_rollingfile.h(3)					       log4c					    appender_type_rollingfile.h(3)

NAME
appender_type_rollingfile.h - Log4c rolling file appender interface. SYNOPSIS
#include <log4c/defs.h> #include <log4c/appender.h> #include <log4c/rollingpolicy.h> Functions LOG4C_API rollingfile_udata_t * rollingfile_make_udata (void) LOG4C_API int rollingfile_udata_set_logdir (rollingfile_udata_t *rfudatap, char *logdir) LOG4C_API int rollingfile_udata_set_files_prefix (rollingfile_udata_t *rfudatap, char *prefix) LOG4C_API int rollingfile_udata_set_policy (rollingfile_udata_t *rfudatap, log4c_rollingpolicy_t *policyp) LOG4C_API const char * rollingfile_udata_get_logdir (rollingfile_udata_t *rfudatap) LOG4C_API const char * rollingfile_udata_get_files_prefix (rollingfile_udata_t *rfudatap) LOG4C_API long rollingfile_get_current_file_size (rollingfile_udata_t *rfudatap) Variables __LOG4C_BEGIN_DECLS LOG4C_API const log4c_appender_type_t log4c_appender_type_rollingfile Detailed Description Log4c rolling file appender interface. The rolling file appender implements a logging mechanism of a list of files up to a maximum number. The files are written by default to the current directory with logging names folowing the pattern log.1, log.2 etc. These parameters may be changed using the appropriate setter functions. If the appender fails to open logfiles for writing then the messages are logged to stderr--it will continue to try to open the zero-th file for writing at rollover events so if it succeeds at some point to open that file the messages will start to appear therein and will no longer be sent to stderr. Switching from logging from one file to the next is referred to as a 'rollover event'. The policy that determines when a rollover event should happen is called a 'rolling policy'. A mechanism is provided to allow different rolling policies to be defined. Log4c ships with (and defaults to) the classic size-window rollover policy: this triggers rollover when files reach a maximum size. The first file in the list is always the current file; when a rollover event occurs files are shifted up by one position in the list--if the number of files in the list has already reached the max then the oldest file is rotated out of the window. See the documentation in the rollingpolicy_type_sizewin.h file for more details on the size-win rollover policy. Function Documentation LOG4C_API long rollingfile_get_current_file_size (rollingfile_udata_t *rfudatap) Get the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the current size of the file being logged to. LOG4C_API rollingfile_udata_t* rollingfile_make_udata (void) Get a new rolling file appender configuration object. Returns: a new rolling file appender configuration object, otherwise NULL. LOG4C_API const char* rollingfile_udata_get_files_prefix (rollingfile_udata_t *rfudatap) Get the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the prefix. LOG4C_API const char* rollingfile_udata_get_logdir (rollingfile_udata_t *rfudatap) Get the logging directory in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the logging directory. LOG4C_API int rollingfile_udata_set_files_prefix (rollingfile_udata_t *rfudatap, char *prefix) Set the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. prefix the logging files prfix to use. Returns: zero if successful, non-zero otherwise. LOG4C_API int rollingfile_udata_set_logdir (rollingfile_udata_t *rfudatap, char *logdir) Set the logging directory in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. logdir the logging directory to set. Returns: zero if successful, non-zero otherwise. LOG4C_API int rollingfile_udata_set_policy (rollingfile_udata_t *rfudatap, log4c_rollingpolicy_t *policyp) Set the rolling policy in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. policyp the logging files prfix to use. Returns: zero if successful, non-zero otherwise. Variable Documentation __LOG4C_BEGIN_DECLS LOG4C_API const log4c_appender_type_t log4c_appender_type_rollingfile rollingfile appender type definition. This should be used as a parameter to the log4c_appender_set_type() routine to set the type of the appender. Author Generated automatically by Doxygen for log4c from the source code. Version 1.2.1 Mon May 2 2011 appender_type_rollingfile.h(3)
All times are GMT -4. The time now is 07:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy