On Wed, 2010-07-21 at 10:46 -0500, Dan McGhee wrote:
My biggest conceptual error was that I thought all the static stuff got
used only with an ISP and their stuff is all on the router.
Nope - the router will be configured to talk to the ISP, but your
computer still needs to know how to talk to
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip address unless you
assign a static ip address *and* the dhcp server assigns the same
address. Usually the dhcp server will have a range
Dan McGhee wrote:
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip address unless you
assign a static ip address *and* the dhcp server assigns the same
address. Usually the dhcp server
On 07/21/2010 09:49 AM, Bruce Dubbs wrote:
Dan McGhee wrote:
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip address unless you
assign a static ip address *and* the dhcp
On 07/21/2010 10:46 AM, Dan McGhee wrote:
On 07/21/2010 09:49 AM, Bruce Dubbs wrote:
Dan McGhee wrote:
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip address
On 21/07/10 16:46, Dan McGhee wrote:
I dug out my router book and learned that without changing anything the
first address it assigns to computers on my network is 192.168.1.100 in
the range 100-253. I can get the other 98, it reserves 1, by using the
on-line utility. So here is what is in my
On 21/07/10 17:09, Dan McGhee wrote:
Had to change GATEWAY to 192.168.1.100 to stop NETLINK errors. I cannot,
however, ping my router.
Could you tell us what the errors are? Maybe something needs tweaking in
your kernel config?
Have you tried setting up the network by hand? Eg, as root
ip
On Wednesday 21 July 2010 11:46:07 Dan McGhee wrote:
On 07/21/2010 09:49 AM, Bruce Dubbs wrote:
Dan McGhee wrote:
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip address unless
Neal Murphy wrote:
On Wednesday 21 July 2010 11:46:07 Dan McGhee wrote:
On 07/21/2010 09:49 AM, Bruce Dubbs wrote:
Dan McGhee wrote:
On 07/19/2010 03:44 PM, Bruce Dubbs wrote:
This is all discussed at 7.13. Configuring the network Script.
A dhcp server does not interfere with a static ip
On 07/21/2010 11:59 AM, Andrew Benton wrote:
On 21/07/10 16:46, Dan McGhee wrote:
I dug out my router book and learned that without changing anything the
first address it assigns to computers on my network is 192.168.1.100 in
the range 100-253. I can get the other 98, it reserves 1, by
Dan McGhee wrote:
Or are the numbers 2-99 available for static use
by my machines?
Yes.
I've run into something, however, that may be preventing success here.
I'm not getting any kernel messages like Link is ready or Link is
up.
The kernel should say:
[2.361360] :00:19.0:
On Wednesday 21 July 2010 06:58:59 Dan McGhee wrote:
Bruce, if I understand what you are saying in relation to the
book--without knowing the why yet--if I copy and paste the entries
in Chapter 7.13 to my 'ifconfig.wlan0/ipv4' I should be able to connect.
Is this true?
If wlan is a typo
On Wednesday 21 July 2010 12:17:50 Bruce Dubbs wrote:
$ /sbin/ifconfig
ip addr ;)
--
Regards,
Trent.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On Wednesday 21 July 2010 13:09:54 Trent Shea wrote:
Possibly irrelevant stuff. Digging around the thread it looks like you may have
already installed the wireless prereqs. It wouldn't hurt to confirm that you're
connected to your access point though, with iwconfig wlan0.
--
Regards,
Trent.
From someone for whom the description Networking is My Weakest Area is
also apt, I'd just like to say thanks to Neal and Bruce for explaining all
that stuff about GATEWAY, BROADCAST and NETMASK. Very lucid and helpful.
Although the information is presented briefly in section 7.13: Configuring
the
Timothy Rice wrote:
From someone for whom the description Networking is My Weakest Area is
also apt, I'd just like to say thanks to Neal and Bruce for explaining all
that stuff about GATEWAY, BROADCAST and NETMASK. Very lucid and helpful.
Although the information is presented briefly in
On Wednesday 21 July 2010 18:30:06 Timothy Rice wrote:
From someone for whom the description Networking is My Weakest Area is
also apt, I'd just like to say thanks to Neal and Bruce for explaining all
that stuff about GATEWAY, BROADCAST and NETMASK. Very lucid and helpful.
Although the
On Monday 19 July 2010 12:01:55 Dan McGhee wrote:
I've never really taken the time to sit down and learn the nits and
grits' of networking. I don't have enough knowledge to even make me
dangerous. Over the years I've not ever really had anything to worry
about because I had a hard-wired
On 07/19/2010 12:03 PM, Neal Murphy wrote:
1. Your router's WAN port has the address assigned by ISP. This address is
your public address.
2. Your router's LAN port has an address from one of the private ranges,
typically 192.168.0.0/16 (google 'CIDR'). This address is the default gateway
On Monday 19 July 2010 13:33:43 Dan McGhee wrote:
But, if I'm reading all this correctly, I'm not
going to be able to connect to the interned until I install dhcp on my
new system. Is that correct?
Not exactly. You can work on a static IP address. Look on the router and
determine the range
On 07/19/2010 01:50 PM, Neal Murphy wrote:
There will be a file in /etc that defines the
interfaces and how they are configured. (On Debian,
it's /etc/network/interfaces; dunno about other systems, or even LFS.)
In my 6.5 LFS it's /etc/sysconfig/network-devices/*, with an
ifconfig-ethX for
On 19/07/10 18:33, Dan McGhee wrote:
Thanks, Neal. This is much more than I bargained for when I asked. I
knew about the router's dhcp server. At the current state of my {,B}LFS
build I really don't need any connectivity since I can generate what I
need to do in chroot. But, if I'm reading all
Andrew Benton wrote:
On 19/07/10 18:33, Dan McGhee wrote:
Thanks, Neal. This is much more than I bargained for when I asked. I
knew about the router's dhcp server. At the current state of my {,B}LFS
build I really don't need any connectivity since I can generate what I
need to do in chroot.
On Mon, 19 Jul 2010, Bruce Dubbs wrote:
A dhcp server does not interfere with a static ip address unless
you assign a static ip address *and* the dhcp server assigns the
same address. Usually the dhcp server will have a range of
addresses it manages, say 192.168.1.10 - say
24 matches
Mail list logo
