Re: Logging from remote sources
by Gene Heskett
On Monday 02 March 2009, Roberto Ragusa wrote:
>Gene Heskett wrote:
>> I want to set up rsyslog on this machine to be a receiver, and log to a
>> separate file, the data it should be capturing on port 514. Right now, it
>> looks like a pretty good imitation of /dev/null. :)
>>
>> I have the manpages and docs installed for rsyslog, and they seem to
>> contain nice examples of sending the logs someplace else, but nothing on
>> the reverse, where it is to log from another source.
>
>Well, I just had a look at the man pages and conf files and found this:
>
># Provides UDP syslog reception
>#$ModLoad imudp.so
>#$UDPServerRun 514
>
># Provides TCP syslog reception
>#$ModLoad imtcp.so
>#$InputTCPServerRun 514
This, after removing the appropriate # comments, and restarting rsyslog seems
to have worked, however the messages are being intermixed with this machines
messages. They are marked as coming from the 'router', I presume by a
gethostbynumber call someplace.
This gives a nice trigger if I can figure out how to use it:
Mar 2 19:41:12 router syslog: syslogd : syslog daemon successfully stopped
Mar 2 19:41:12 router kernel: klogd started: BusyBox v1.11.1 (2008-07-26 11:32:32 CEST)
Mar 2 19:41:12 router syslog: klogd : klog daemon successfully started
I would like to put those in their own log. Is that possible?
>which appears to be what you have to uncomment to receive messages.
>Do you want to receive TCP or UDP?
Not sure, so I enabled both. :)
>Try to understand if data is coming to your machine with
>
>tcpdump -i eth0 -n -n
That was very informative, the major portion of the net traffic here is
being generated by arp, scanning the local subnet asking whohas, getting
to .254 and resuming at 1. That was so noisy if I saw anything from the
router it scrolled offscreen so fast I couldn't read it. That could be
turned off because I use host files here for the majority of my stuff.
AFAIKT from the services config there is no arp daemon running. htop also
doesn't show it. FWIW, dnsmasq is running, but not bind nor nscd.
How can I turn that off?
>and do not forget to make a hole in the firewall to avoid
>discarding these packets.
No firewalls in use on the local net, dd-wrt seems to handle that very
well. In 2 years, the only people who got through it, were given the
passwd to do so by me.
Thank You, Roberto.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
In Greene, New York, it is illegal to eat peanuts and walk backwards on
the sidewalks when a concert is on.
15 years, 2 months
Re: How to set up a DNS server(at Home)
by Mikkel
Bruno Wolff III wrote:
> On Wed, Jan 28, 2009 at 11:14:58 -0600,
> "Mikkel L. Ellertson" <mikkel(a)infinity-ltd.com> wrote:
>> He may also find that dnsmasq, witch is in the repository
>> (dnsmasq-2.45-1.fc10.i386) may do the job, and is much simpler to
>> set up then bind.
>
> That's a forwarder isn't it?
>
> (When I was listing DNS server types I forgot to mention forwarders which
> can be used to selectively pass requests on to recursive resolvers either
> to provide local caching or to query different servers based on attributes
> of the request.)
>
It is a forwarder, caching name server, and a name server for the
local network all in one. It can also act as a DHCP server. It works
well for a home or small office. But it is not a full featured name
server. (Does a home network need one?)
From the man page:
Dnsmasq accepts DNS queries and either answers them from a small,
local, cache or forwards them to a real, recursive, DNS server. It
loads the contents of /etc/hosts so that local hostnames which do
not appear in the global DNS can be resolved and also answers DNS
queries for DHCP configured hosts.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
15 years, 3 months
Re: How to set up a DNS server(at Home)
by Bruno Wolff III
On Wed, Jan 28, 2009 at 11:14:58 -0600,
"Mikkel L. Ellertson" <mikkel(a)infinity-ltd.com> wrote:
> He may also find that dnsmasq, witch is in the repository
> (dnsmasq-2.45-1.fc10.i386) may do the job, and is much simpler to
> set up then bind.
That's a forwarder isn't it?
(When I was listing DNS server types I forgot to mention forwarders which
can be used to selectively pass requests on to recursive resolvers either
to provide local caching or to query different servers based on attributes
of the request.)
15 years, 3 months
Re: How to set up a DNS server(at Home)
by Mikkel
Bruno Wolff III wrote:
>
> For a general overview of DNS, DJB's pages (http://cr.yp.to/djbdns.html)
> are probably a better start. Though he should note that neither tinydns
> nor dnscache are in Fedora, so he probably isn't going to want to use
> because of the extra work involved.
>
> You response conflated parts of running a caching resolver and a publisher.
> Those are two distinct things and there will be less confusion if he
> understands what each does indpendently. He may only need one of these
> types for his home system depending on what he is trying to accomplish.
>
He may also find that dnsmasq, witch is in the repository
(dnsmasq-2.45-1.fc10.i386) may do the job, and is much simpler to
set up then bind.
One other thing to keep in mind - if you are using DHCP from a
firewall/router, then /etc/resolv.conf is going to get overwritten
if you use the default configuration, so the local name server will
not be used.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
15 years, 3 months
Re: "Static" wireless interface and runlevel 3
by Geoffrey Leach
On 01/25/2009 09:02:16 PM, Todd Zullinger wrote:
> Geoffrey Leach wrote:
> > I have a system whose network interface is via a USB wireless to a
> > router.
> >
> > From what I've read, NetworkManager is deemed unsuitable for this
> > task. Correct?
>
> IMO, not entirely correct. If your wireless network uses WPA, then I
> think the old network service requires some fiddling, perhaps more
> than it takes to make NetworkManager bring up your connection
> automatically without a user logging in. (This was the case the last
> time I looked at the network service scripts, which was a few
> releases
> ago now. If that's changed, then please ignore me. :)
>
> Now, if you're not using WPA, then system-config-network and the
> network service is probably sufficient and simpler than
> NetworkManager.
>
> Perhaps if you provide more details about what sort of wireless
> you're
> trying to setup and which tools you're using / have used so far
> someone can be of more help.
>
> Personally, I try to avoid mixing system-config-network and NM. I do
> have NetworkManager starting my WPA wireless connection prior to
> login
> on my laptop. I generally boot into runlevel 5, so I haven't tested
> it in runlevel 3, but I do think it would work there.
Hmmm ... well, at least its possible!
No desire to mix NM and network. Whichever I can get to work wins!
I'm using WPA.
The network interface is via USB wireless to a Netgear router.
iwconfig gives the same info as on the other end of the link.
The system config is the Netgear router that talks to a satellite modem
on one side and has both a wired and wireless connection to a laptop.
The system I'm attempting to connect to has just a wireless (USB)
connection. The wired (eth0) will be talking to another device.
Everything works as expected once I log in at runlevel 5.
Various experiments with the network service all fail at some point
because no IP address could be acquired. I tried a hard-wired IP in
ifcfg-wlan0 to no avail. I'm running dnsmasq, which has no trouble
discovering the router. Presumably the problem is one of getting things
done in the right order, but I've tried all the combinations I can
think of - restarting network, restarting dnsmasq, ... to no avail.
15 years, 3 months
Fedora 9 Network Manager vpn connection regression
by Patrick Mansfield
The current network manager vpn is not working for me, it was working fine in
early december, directly using vpnc or using the cisco vpn client I am
able to connect.
Any ideas?
I've searched quite a bit and still have not found an answer.
Thanks for any help ...
Details:
I'm running Fedora 9, all up to date.
It probably worked with these versions, back in mid december or so:
NetworkManager-glib-0.7.0-0.11.svn4022.4.fc9.i386
NetworkManager-vpnc-0.7.0-0.10.svn4024.fc9.i386
NetworkManager-gnome-0.7.0-0.11.svn4022.4.fc9.i386
NetworkManager-0.7.0-0.11.svn4022.4.fc9.i386
It started failing with these, sometime in late December:
NetworkManager-gnome-0.7.0-0.12.svn4326.fc9.i386
NetworkManager-glib-0.7.0-0.12.svn4326.fc9.i386
NetworkManager-0.7.0-0.12.svn4326.fc9.i386
NetworkManager-vpnc-0.7.0-0.11.svn4326.fc9.i386
And current testing rpms also fail, these:
NetworkManager-gnome-0.7.0-1.git20090102.fc9.i386
NetworkManager-vpnc-0.7.0-1.svn13.fc9.i386
NetworkManager-glib-0.7.0-1.git20090102.fc9.i386
NetworkManager-0.7.0-1.git20090102.fc9.i386
It connects to the vpn, but then it hits some failure - I'm not sure what -
and decides the vpn connection failed.
I see in log files:
Jan 17 09:38:23 palm NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 26505
Jan 17 09:38:23 palm NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections
Jan 17 09:38:23 palm NetworkManager: <info> VPN plugin state changed: 1
Jan 17 09:38:28 palm NetworkManager: <info> VPN plugin state changed: 3
Jan 17 09:38:28 palm NetworkManager: <info> VPN connection 'work' (Connect) reply received.
Jan 17 09:38:28 palm kernel: tun0: Disabled Privacy Extensions
Jan 17 09:38:29 palm NetworkManager: <info> VPN connection 'work' (IP Config Get) reply received.
Jan 17 09:38:29 palm NetworkManager: <info> VPN Gateway: nnn.nnn.nn.nnn
Jan 17 09:38:29 palm NetworkManager: <info> Tunnel Device: tun0
Jan 17 09:38:29 palm NetworkManager: <info> Internal IP4 Address: 192.168.45.140
Jan 17 09:38:29 palm NetworkManager: <info> Internal IP4 Prefix: 24
Jan 17 09:38:29 palm NetworkManager: <info> Internal IP4 Point-to-Point Address: 192.168.45.140
Jan 17 09:38:29 palm NetworkManager: <info> Maximum Segment Size (MSS): 0
Jan 17 09:38:29 palm NetworkManager: <info> Internal IP4 DNS: nnn.nnn.nn.nnn
Jan 17 09:38:29 palm NetworkManager: <info> Internal IP4 DNS: nnn.nnn.nn.nnn
Jan 17 09:38:29 palm NetworkManager: <info> DNS Domain: 'foo.bar.com'
Jan 17 09:38:29 palm NetworkManager: <info> Login Banner:
Jan 17 09:38:29 palm NetworkManager: <info> -----------------------------------------
Jan 17 09:38:29 palm NetworkManager: <info> You are connected to foo bar as a user
Jan 17 09:38:29 palm NetworkManager: <info> -----------------------------------------
Jan 17 09:38:29 palm dnsmasq[3759]: reading /etc/resolv.conf
Jan 17 09:38:29 palm dnsmasq[3759]: using nameserver 216.99.193.19#53
Jan 17 09:38:29 palm dnsmasq[3759]: using nameserver 216.99.193.1#53
Jan 17 09:38:29 palm dnsmasq[3759]: using nameserver 216.99.193.2#53
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_set_ip4_route: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: <info> VPN connection 'work' (IP Config Get) complete.
Jan 17 09:38:30 palm NetworkManager: <info> Policy set 'eth0' (eth0) as default for routing and DNS.
Jan 17 09:38:30 palm NetworkManager: <info> VPN plugin state changed: 4
Jan 17 09:38:30 palm NetworkManager: <info> VPN plugin failed: 1
Jan 17 09:38:30 palm NetworkManager: <info> VPN plugin state changed: 6
Jan 17 09:38:30 palm NetworkManager: <info> VPN plugin state change reason: 0
Jan 17 09:38:30 palm NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.
Jan 17 09:38:30 palm NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Jan 17 09:38:30 palm NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Jan 17 09:38:31 palm dnsmasq[3759]: reading /etc/resolv.conf
Jan 17 09:38:31 palm dnsmasq[3759]: using nameserver 216.99.193.19#53
Jan 17 09:38:31 palm dnsmasq[3759]: using nameserver 216.99.193.1#53
Jan 17 09:38:31 palm dnsmasq[3759]: using nameserver 216.99.193.2#53
Jan 17 09:38:31 palm NetworkManager: <info> Policy set 'eth0' (eth0) as default for routing and DNS.
15 years, 3 months
mdadm: cannot open device /dev/sda1: Device or resource busy \ mdadm: /dev/sda1 has no superblock - assembly aborted
by James Groleau
Hey Folks,
I've got a problem that I cannot seem to make go away.
I've got a machine running FC8
]# uname -a
Linux <hostname> 2.6.26.6-49.fc8 #1 SMP Fri Oct 17 15:33:32 EDT 2008 x86_64
x86_64 x86_64 GNU/Linux
with an external eSATA Hard Drive RAID 5 array.
I installed a replacement drive for the main system and performed a fresh
install of FC10 with the RAID 5 array disconnected. Then after ensuring all
updates were completed (as of Jan 03/09) I reattached the array.
As root I issued the mdadm command and received the following error:
]# mdadm --assemble /dev/md1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sda1
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has no superblock - assembly aborted
I cannot seem to determine why I cannot access the sda1 drive. I have replaced
the FC8 system drive and all is well. I can start and mount the RAID array
normally.
There is no mdadm.conf file. I have always mounted the array manually.
I've beat Google into a frenzy over the last couple days trying find a
solution to no avail.
Any clues/hints/suggestion?
Thanks much.
Additional information:
======================================================
]# mdadm --assemble --run /dev/md1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
This will work to bring up the array under FC10 in a degraded state.
I did remove sda1 from the array, then delete and recreate the partition on
sda, and attempt to add it back into the array, but continue to receive the
same error messages from mdadm.
I had to rebuild the array under FC8.
====================================================
]# lsof | grep -i sda
<nothing listed>
======================================================
]# mdadm --examine /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : c03bad6f:28dae689:a100065d:2118bad4
Creation Time : Sat Nov 8 17:08:48 2008
Raid Level : raid5
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Update Time : Sat Jan 3 16:11:42 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 3fb6543 - correct
Events : 445816
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 4 8 1 4 active sync /dev/sda1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 81 3 active sync /dev/sdf1
4 4 8 1 4 active sync /dev/sda1
======================================================
]# mdadm --examine /dev/sdb1
mdadm: No md superblock detected on /dev/sdb1.
]# mdadm --examine /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 0.90.00
UUID : c03bad6f:28dae689:a100065d:2118bad4
Creation Time : Sat Nov 8 17:08:48 2008
Raid Level : raid5
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Update Time : Sat Jan 3 16:11:42 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 3fb655b - correct
Events : 445816
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 33 0 active sync /dev/sdc1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 81 3 active sync /dev/sdf1
4 4 8 1 4 active sync /dev/sda1
=================================================================
]# mdadm --examine /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 0.90.00
UUID : c03bad6f:28dae689:a100065d:2118bad4
Creation Time : Sat Nov 8 17:08:48 2008
Raid Level : raid5
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Update Time : Sat Jan 3 16:11:42 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 3fb655b - correct
Events : 445816
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 33 0 active sync /dev/sdc1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 81 3 active sync /dev/sdf1
4 4 8 1 4 active sync /dev/sda1
================================================================
]# mdadm --examine /dev/sde1
/dev/sde1:
Magic : a92b4efc
Version : 0.90.00
UUID : c03bad6f:28dae689:a100065d:2118bad4
Creation Time : Sat Nov 8 17:08:48 2008
Raid Level : raid5
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Update Time : Sat Jan 3 16:11:42 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 3fb657f - correct
Events : 445816
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 65 2 active sync /dev/sde1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 81 3 active sync /dev/sdf1
4 4 8 1 4 active sync /dev/sda1
===============================================================
]# mdadm --examine /dev/sdf1
/dev/sdf1:
Magic : a92b4efc
Version : 0.90.00
UUID : c03bad6f:28dae689:a100065d:2118bad4
Creation Time : Sat Nov 8 17:08:48 2008
Raid Level : raid5
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Update Time : Sat Jan 3 16:11:42 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 3fb6591 - correct
Events : 445816
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 81 3 active sync /dev/sdf1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 81 3 active sync /dev/sdf1
4 4 8 1 4 active sync /dev/sda1
============================================================
]# service --status-all | grep -i md
mdadm is stopped
======================================================
]# service --status-all
acpid (pid 2176) is running...
anacron (pid 2649) is running...
atd (pid 2569) is running...
auditd (pid 2057) is running...
Avahi daemon is running
BackupPC is stopped
bluetoothd is stopped
btseed is stopped
bttrack is stopped
Frequency scaling enabled using ondemand governor
crond (pid 2518) is running...
cupsd (pid 2616) is running...
cups-config-daemon is obsolete
dc_client is stopped
dc_server is stopped
dnsmasq (pid 2657) is running...
Usage: /etc/init.d/firstboot {start|stop}
Checking fuse filesystem ok.
gpm (pid 2507) is running...
hald (pid 2184) is running...
httpd is stopped
innd is stopped
irattach is stopped
irqbalance (pid 2085) is running...
iscsid is stopped
kerneloops (pid 2527) is running...
libvirtd (pid 2590) is running...
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +15.0°C
Core0 Temp: +5.0°C
Core1 Temp: +0.0°C
Core1 Temp: -3.0°C
mdadm is stopped
dbus-daemon (pid 3149 2152) is running...
multipathd is stopped
netconsole module not loaded
netplugd is stopped
Configured devices:
lo eth0 eth1
Currently active devices:
lo eth0 eth1 virbr0
NetworkManager (pid 2402) is running...
rpc.mountd is stopped
nfsd is stopped
rpc.rquotad is stopped
rpc.statd (pid 2105) is running...
nmbd (pid 2540) is running...
nscd is stopped
ntpd (pid 2453) is running...
nvidia.ko for kernel 2.6.27.9-159.fc10.x86_64 was found.
The driver is enabled.
openvpn: service not started
pcscd (pid 2389) is running...
portreserve is stopped
Process accounting is disabled.
racoon is stopped
rdisc is stopped
restorecond is stopped
rpcbind (pid 2092) is running...
rpc.idmapd (pid 2139) is running...
rsyslogd (pid 2073) is running...
saslauthd is stopped
sendmail (pid 2488) is running...
sm-client (pid 2497) is running...
setroubleshootd (pid 2435) is running...
smartd is stopped
smbd (pid 2548) is running...
Monthly smolt check-in is enabled.
snmpd is stopped
snmptrapd is stopped
squid is stopped
openssh-daemon (pid 2445) is running...
Xvnc is stopped
vsftpd (pid 2471) is running...
winbindd (pid 2415) is running...
wpa_supplicant (pid 2412) is running...
ypbind is stopped
15 years, 4 months
Re: Getting DHCP to work/f10 declines to start network
by tom
On Sun, 21 Dec 2008, Anoop wrote:
> On Sun, Dec 21, 2008 at 11:48 PM, tom <tfreeman(a)intel.digichem.net> wrote:
>>
>> I'm giving f10 a try on a new disk, and therefor a fresh install.
>> I'm supposed to be picking up (and was with f8) the ip4 address
>> from a dnsmasq server via dhcp, but f10 is barfing. Well, not
>> entirely, as the IP6 style networking shows on ifconfig, but since
>> I don't want IP6 networking at this moment, that isn't exactly
>> usefull.
>>
>> Now since I dislike Network Manage on a desktop machine, and would
>> prefe to have the network come up during boot, what is the prefered
>> way to get rid of Netwreck Mangler (sp?), and bring the network
>> up the old fashioned way.
> Disable 'NetworkManager' and enable 'network' service. You can do that
> by running 'setup' on your shell. Then you can edit interface related
> files in '/etc/sysconfig/networking/' to setup addresses. I am
> suggesting this because, 'system-config-network' has some issues of
> late.
>
Ok. Yet another fresh install. Disabled "NetworkManager" and enabled
"network". Going with dhcp, I get hung at boot "Determining IP information
for eth0." Hard hung as big red switch time.
Things do seem to be willing to work if I set the IP address by hand, and
not have dhclient try to do the job.
Is the dhcp system busted here? Or am I nuts?
>>
>> I'd love to see pointers or suggestions on trouble shooting this
>> type issue also.
>>
>> And now to go pester fiend Google and find out how little I
>> understand 8-/.
>>
>> Thanks for the assistance.
>>
>> --
>> fedora-list mailing list
>> fedora-list(a)redhat.com
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>
>
>
15 years, 4 months
Re: Getting DHCP to work/f10 declines to start network
by Anoop
On Sun, Dec 21, 2008 at 11:48 PM, tom <tfreeman(a)intel.digichem.net> wrote:
>
> I'm giving f10 a try on a new disk, and therefor a fresh install.
> I'm supposed to be picking up (and was with f8) the ip4 address
> from a dnsmasq server via dhcp, but f10 is barfing. Well, not
> entirely, as the IP6 style networking shows on ifconfig, but since
> I don't want IP6 networking at this moment, that isn't exactly
> usefull.
>
> Now since I dislike Network Manage on a desktop machine, and would
> prefe to have the network come up during boot, what is the prefered
> way to get rid of Netwreck Mangler (sp?), and bring the network
> up the old fashioned way.
Disable 'NetworkManager' and enable 'network' service. You can do that
by running 'setup' on your shell. Then you can edit interface related
files in '/etc/sysconfig/networking/' to setup addresses. I am
suggesting this because, 'system-config-network' has some issues of
late.
Thanks,
Anoop
>
> I'd love to see pointers or suggestions on trouble shooting this
> type issue also.
>
> And now to go pester fiend Google and find out how little I
> understand 8-/.
>
> Thanks for the assistance.
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
15 years, 4 months
Getting DHCP to work/f10 declines to start network
by tom
I'm giving f10 a try on a new disk, and therefor a fresh install.
I'm supposed to be picking up (and was with f8) the ip4 address
from a dnsmasq server via dhcp, but f10 is barfing. Well, not
entirely, as the IP6 style networking shows on ifconfig, but since
I don't want IP6 networking at this moment, that isn't exactly
usefull.
Now since I dislike Network Manage on a desktop machine, and would
prefe to have the network come up during boot, what is the prefered
way to get rid of Netwreck Mangler (sp?), and bring the network
up the old fashioned way.
I'd love to see pointers or suggestions on trouble shooting this
type issue also.
And now to go pester fiend Google and find out how little I
understand 8-/.
Thanks for the assistance.
15 years, 4 months
