Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Help, Freenas can't see my network

2,242 views
Skip to first unread message

Bob H

unread,
Apr 17, 2013, 6:02:07 PM4/17/13
to
I have just installed x3 2tb hard Disks and got freeNas to boot from a
flash drive, but when it gets to Starting Network, it says
Link State changed to UP.
The Starting dhclient
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 (etc 6 times),
then
NO DHCOFFERS Received

At the end, after the freenas menu, it says, You may try the following
URL's to access the web user interface:
http://0.0.0.0

My network goes through a gigabit 8 port switch, if that has anything to
do with it.

Advice please

Bob H

unread,
Apr 17, 2013, 6:28:26 PM4/17/13
to
I have tried pinging the virgin media SH with a direct connection from
server, but freenas can't see it with Error No Route to Host

Advice please

Bob H

unread,
Apr 17, 2013, 6:29:40 PM4/17/13
to
I have just installed x3 2tb hard Disks and got freeNas to boot from a
flash drive, but when it gets to Starting Network, it says
Link State changed to UP.
The Starting dhclient
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 (etc 6 times),
then
NO DHCOFFERS Received

At the end, after the freenas menu, it says, You may try the following
URL's to access the web user interface:
http://0.0.0.0

My network goes through a gigabit 8 port switch, if that has anything to
do with it.

I have tried pinging the virgin media super hub , but freenas gives
error No Route to Host

Advice please

Gordon

unread,
Apr 18, 2013, 1:49:49 AM4/18/13
to
On 2013-04-17, Bob H <b...@despammer.com> wrote:
> I have just installed x3 2tb hard Disks and got freeNas to boot from a
> flash drive, but when it gets to Starting Network, it says
> Link State changed to UP.
> The Starting dhclient
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 (etc 6 times),
> then
> NO DHCOFFERS Received

Okay, here is the important part. The FreeNAS machine is wanting an offer
from a DCHP server on your home network (LAN), soi that it can have a IP
number. Do you have one?

My money is that you do not?

Could you explain more about your setup. Do you have a LAN? FreeNAS thinks
networking right from bootup.

Bob H

unread,
Apr 18, 2013, 4:05:44 AM4/18/13
to
On 18/04/2013 06:49, Gordon wrote:
> On 2013-04-17, Bob H <b...@despammer.com> wrote:
>> I have just installed x3 2tb hard Disks and got freeNas to boot from a
>> flash drive, but when it gets to Starting Network, it says
>> Link State changed to UP.
>> The Starting dhclient
>> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 (etc 6 times),
>> then
>> NO DHCOFFERS Received
>
> Okay, here is the important part. The FreeNAS machine is wanting an offer
> from a DCHP server on your home network (LAN), soi that it can have a IP
> number. Do you have one?
>
> My money is that you do not?
>
> Could you explain more about your setup. Do you have a LAN? FreeNAS thinks
> networking right from bootup.
>
>
>
I have been using WHS2008 for my home server for over 12 months, and
after much discussion on the NG I have decided to ditch WHS2008 and use
FreeNas instead

I have FeeNas on a thumb/flashdrive plugged into the back of the server case

The home server is connected to a TP Link 8 port switch as are 3 other
PC's, so that the files on the server can be accessed by the other machines.

I have googled this problem but can't see how or where to make any
changes if indeed they are required.

Bob H

unread,
Apr 18, 2013, 4:08:18 AM4/18/13
to
On 18/04/2013 06:49, Gordon wrote:
> On 2013-04-17, Bob H <b...@despammer.com> wrote:
>> I have just installed x3 2tb hard Disks and got freeNas to boot from a
>> flash drive, but when it gets to Starting Network, it says
>> Link State changed to UP.
>> The Starting dhclient
>> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 (etc 6 times),
>> then
>> NO DHCOFFERS Received
>
> Okay, here is the important part. The FreeNAS machine is wanting an offer
> from a DCHP server on your home network (LAN), soi that it can have a IP
> number. Do you have one?
>
> My money is that you do not?
>
> Could you explain more about your setup. Do you have a LAN? FreeNAS thinks
> networking right from bootup.
>
>
>
I have been using WHS2008 for my home server for over 12 months, and
after much discussion on the NG I have decided to ditch WHS2008 and use
FreeNas instead

I have FeeNas on a thumb/flashdrive plugged into the back of the server case

The home server is connected to a TP Link 8 port switch as are 3 other
PC's, so that the files on the server can be accessed by the other machines.

I have googled this problem but can't see how or where to make any
changes if indeed they are required.

The router is a VIRGINMEDIA SUPER HUB , which all 3 machines can access
on 192.168.0.1, but freenas reports Host is down

Bob H

unread,
Apr 18, 2013, 4:42:59 AM4/18/13
to
I have ran ipconfig/all on the 3 machines I have and I see that DHCP is
no enabled on any of them, although it is on the VM Super Hub

Rob

unread,
Apr 18, 2013, 7:34:04 AM4/18/13
to
Try enabling DHCP on one of your PCs (which must currently use
static IPs.) Reboot that PC and see if it obtains an IP address
from the VM superhub. If it doesn't, the DHCP server on the
superhub isn't working or is not set up correctly.
Alternatively, write down the static IPs of all of your PCs
then give FreeNas a fixed, non-clashing IP in the same range.
eg, if your 3 PCs have 192.168.0.30, 192.168.0.31, 192.168.0.32
then set FreeNas to be 192.168.0.33.
--
Rob



Rob

unread,
Apr 18, 2013, 7:41:45 AM4/18/13
to
Bear in mind that your old server may have been supplying the
IP addresses from its own DHCP server. DHCP IP addresses have
a lease expiry time, so the PCs will keep that old address until
the expiry time is up.
To get new IPs from a new DHCP server (ie your VM hub), at a
command prompt on each PC, type:
ipconfig /renew
They should then get their new IP addresses.
--
Rob

Bob H

unread,
Apr 18, 2013, 8:18:26 AM4/18/13
to
On 18/04/2013 12:34, Rob wrote:
I have checked the VM super hub and DHCP is enabled.
I have checked in services of the 2 win7 machines and DHCP is shown as
Started, and I have clicked on Restart.
Again from ipconfig/all DHCP is not Enabled....How can that be, from the
above?
I have done ipconfig/renew to get new IP addresses.
I have checked the VM superhub to see that there are new IP addresses
and wrote them down

I used these instruction to assign a static IP address:

Enter an option from 1-11: 1
1) em0
Select an interface (q to quit): 1
Delete existing config? (y/n) n
Configure interface for DHCP? (y/n) n
Configure IPv4? (y/n) y
Interface name: (press enter as can be blank)
Several input formats are supported
Example 1 CIDR Notation:
192.168.1.1/24
Example 2 IP and Netmask seperate:
IP: 192.168.1.1
Netmask: 255.255.255.0, or /24 or 24
IPv4 Address: 192.168.1.108/24
Saving interface configuration: Ok
Configure IPv6? (y/n) n
Restarting network: ok
You may try the following URLs to access the web user interface:
http://192.168.1.108

I assigned 198.168.0.15, which is outside the current range of IP
addresses shown on the Super Hub.

Freenas then told me I could access the web browser at the said IP
address, but I could not

Rob

unread,
Apr 18, 2013, 8:34:27 AM4/18/13
to
192.168.0.15 is on a different subnet to 192.168.1.x, so won't
be accessible.
The first 3 parts of the IP addresses all need to be the same to
be on the same subnet, so try using 192.168.1.15.
I'm only able to give generic advice on IP addressing as I have
never used FreeNas.
--
Rob


Rob Morley

unread,
Apr 18, 2013, 8:44:31 AM4/18/13
to
On Thu, 18 Apr 2013 13:34:27 +0100
Rob <no...@nowhere.noway.con> wrote:

> 192.168.0.15 is on a different subnet to 192.168.1.x, so won't
> be accessible.
> The first 3 parts of the IP addresses all need to be the same to
> be on the same subnet,

It depends on the class of network - you can use the 10.0.0.0 addresses
for a home network and as long as they start with 10 everything will be
visible.
I'm fairly sure you meant "using the 192.168 private subnets the first
three parts need to be the same", and 192.168 are probably the most
commonly used for small/home networks, but all the same ...

Bob H

unread,
Apr 18, 2013, 8:51:59 AM4/18/13
to
192.168.0.15 is actually on the same subnet, as all my ip addresses
start with 192.168.0.

Thanks anyway

Bob H

unread,
Apr 18, 2013, 8:55:12 AM4/18/13
to
I forgot to add that I can ping to and from all the win7 machines but
not to and from the nas server.

Bernard Peek

unread,
Apr 18, 2013, 8:56:09 AM4/18/13
to
When using 192.168 addresses at least the first two numbers must be the
same. It is possible to create a subnet that spans different numbers in
the third group but it is uncommon.

The OP used a netmask of 255.255.255.0 so all of the first three numbers
must match exactly for every machine on the network. Having some
machines on the 192.168.0 subnet and some on 192.168.1 will not work.

If he had used a netmask of 255.255.0.0 then only the first two numbers
would need to match. This is possible but not very common and best
avoided on the principle of least surprise.




--
Bernard Peek
b...@shrdlu.com

Rob Morley

unread,
Apr 18, 2013, 10:03:33 AM4/18/13
to
On Thu, 18 Apr 2013 13:56:09 +0100
Bernard Peek <b...@shrdlu.com> wrote:

> When using 192.168 addresses at least the first two numbers must be
> the same. It is possible to create a subnet that spans different
> numbers in the third group but it is uncommon.
>
> The OP used a netmask of 255.255.255.0 so all of the first three
> numbers must match exactly for every machine on the network. Having
> some machines on the 192.168.0 subnet and some on 192.168.1 will not
> work.
>
I should probably have read back up the thread for mention of netmasks,
but by definition 192.168.* is 256 separate (albeit contiguous)
networks, while 10.* is a single one. I'm not sure if anything actually
forces you to use the address space that way, but I imagine some
software might well assume that's how it's allocated.

Richard Kettlewell

unread,
Apr 18, 2013, 10:13:25 AM4/18/13
to
Classful addressing has been obsolete for a couple of decades now. You
can divide up the RFC1918 address space whichever way you like.

--
http://www.greenend.org.uk/rjk/

Bob H

unread,
Apr 18, 2013, 12:35:46 PM4/18/13
to
I found this about setting up the LAN IP address, and I am not too sure
about the part that says 'The LAN Subnet mask is 24'
Does that mean subnet 255.255.255.24?

'Console setup' - select 2 - Set LAN IP address

'Do you want to use DHCP for this interface?' - select No (you could
select yes if you wish but it's best to set a static IP address for your
FreeNAS computer)

'Enter new LAN IPv4 address' - enter the IP address you want for your
FreeNAS computer. For example, it should be on the same sub-net and with
a unique IP address. If you are on a home network, this is what you can
do to decide which IP address to use:

a) Go to your Windows PC
b) Click Start | Run
c) Type CMD [Enter]
d) Type IPCONFIG /all [Enter]
e) Where it says 'IP address' it'll read something like 192.168.0.18,
that's the address of your Windows PC. The address you should enter for
the FreeNAS should be the same but the last number should be different,
like .250. For example, on your FreeNAS computer enter 192.168.0.250

'Enter new LAN subnet mask' - the default is 24, this should be correct
in most cases, select OK

'Enter IPv4 default gateway' - enter your default gateway, typically
your Router, the same IP address as before but ending in .1. Take a look
on your Windows PC, the default gateway is listed on the IPCONFIG
information. In our example I will enter 192.168.0.1

'Enter DNS IPv4 address' - again you can find this in the IPCONFIG
information from your Windows PC. Often this is the same as your default
gateway. In my example my DNS address is 192.168.0.1

'Do you want to configure IPv6 for this interface?' - select No

Press Enter

The FreeNAS computer is ready!

Rob Morley

unread,
Apr 18, 2013, 1:09:08 PM4/18/13
to
On Thu, 18 Apr 2013 17:35:46 +0100
Bob H <b...@despammer.com> wrote:

> I found this about setting up the LAN IP address, and I am not too
> sure about the part that says 'The LAN Subnet mask is 24'
> Does that mean subnet 255.255.255.24?

No. One way of writing it is 192.168.0.0/24 which denotes that the
first 24 bits are the network address, and the last 8 bits are
nodes within that network, which is the same as 192.168.0.0 with
netmask 255.255.255.0
Note 255 is 11111111 in binary i.e. eight individual bits, and
255.255.255.0 can be written as 11111111111111111111111100000000
i.e 24 bits set and eight bits unset, the /24 notation is a
representation of that.

Bob H

unread,
Apr 18, 2013, 1:39:58 PM4/18/13
to
Thanks for the clarification, as it is what I thought.

Bob H

unread,
Apr 18, 2013, 2:56:33 PM4/18/13
to
After reading a bit about this, it would seem that my VM super Hub is
not seeing the requests for an IP address or no request is getting
through to the Super Hub.

After saying that there is a list of IP addresses under the DHCP section
of the SH, and I have added an IP address for the FreeNas, but it didn't
make any difference.

Bob H

unread,
Apr 18, 2013, 3:57:22 PM4/18/13
to
I've just tried the Freenas usb stick in my laptop, and it said that no
network interfaces were found, and the said laptop is connected to my
home network.

Oh well I tried with Freenas, and it looks like I'll be going back to
WHS 2008 again

Johny B Good

unread,
Apr 18, 2013, 6:55:19 PM4/18/13
to
It's certainly a possibility if my experience with a Netgear unit is
anything to go by. Most of the time, it works perfectly fine but,
maybe 4 or 5 times a year, I find myself having to powercycle it to,
variously, get Gbit ports recognised as Gbit, rather than 100Mbps
connections, access to the internet fully functional and, IIRC, other
PCs on the network to be seen.

Since it takes only a dozen or so seconds for it to restart, it's
been more of a minor foible rather than a major upset which I can live
with. In your case, it's certainly worth resetting the switch and then
reboot your FreeNAS box.

I've read the following posts (BTW, you were generating duplicate
postings) and notice the SH's use of the uncommon 192.168.0,nnn
private subnet address range has some contributers a little confused.

Personally, I'd eschew the use of DHCP for server IP address
assignment and choose a fixed one outside of the DHCP scope (but
within the subnet range, such as 192.168.0.150 for example). You need
to enter the gateway router's address ( 192.168.0.1) as well as DNS
server addresses (either your ISP's actual DNS server addresses or
else the gateway router's address - 192.168.0.1 in this case- if you
don't happen to know them).

I've assumed (as has everyone else) that you don't have a selection
of ethernet adapter interfaces to choose from since not many MoBos
have more than a single LAN port built in (and you'd know if you had
fitted a PCIe Gbit LAN adapter, wouldn't you?). You can check whether
this is the case by selecting the "Configure Interface" option and see
if more than a single instance is available. Also, leave the IPv6
option disabled - it has no function on a private LAN.

HTH & HAND
--
Regards, J B Good

Jaimie Vandenbergh

unread,
Apr 20, 2013, 2:45:47 PM4/20/13
to
Friggin' Cisco still teach it as the Main Deal for CCNA and such
courses... pfft. Nonsense.

Cheers - Jaimie
--
Okay, it works now. Or at least it malfunctions in all the expected ways.
-- Mark Edwards, asr

Mike Tomlinson

unread,
Apr 20, 2013, 5:36:36 PM4/20/13
to
En el art�culo <1io5n85dnlohssrb8...@4ax.com>, Jaimie
Vandenbergh <jai...@sometimes.sessile.org> escribi�:

>Friggin' Cisco still teach it as the Main Deal for CCNA and such
>courses... pfft. Nonsense.

And they still use the inverse netmask in the config files, which drives
me mad. It might just be me, but when I look at Cisco configs, my mind
goes blank. I'm sure for some it's intuitive, but not me.

--
(\_/)
(='.'=)
(")_(")

Jaimie Vandenbergh

unread,
Apr 20, 2013, 7:21:02 PM4/20/13
to
I don't think it is for anyone, it's just learned. The different
configuration regions are all incoherently different in syntax and
intent, showing clearly that new services weren't so much designed to
fit into the overall schema (because there isn't one) as bolted on -
often with a rivet gun, stripping the metaphorical threads. "Sod the
way we've done it for 20 years, *this* way'll be better". No, it's
equally bad and now just confusing. Cisco's IOS is a horrible thing.

I'm doing a CCNA at the moment, to pass the time. Did you guess?

Cheers - Jaimie
--
"The time you enjoy wasting is not wasted" -- Bertrand Russell

Mike Tomlinson

unread,
Apr 21, 2013, 3:39:02 AM4/21/13
to
En el art�culo <7g86n8tfmom5hehrs...@4ax.com>, Jaimie
Vandenbergh <jai...@sometimes.sessile.org> escribi�:

>I'm doing a CCNA at the moment, to pass the time.

I could think of better ways to pass the time, preferably involving
$BEER, but to me, naked wrestling with grizzly bears in mud is more
enjoyable than doing CCNA.

> Did you guess?

I did mine a few years ago but failed the exam. Wasn't particularly
motivated to bother trying again.

Jaimie Vandenbergh

unread,
Apr 21, 2013, 4:40:27 AM4/21/13
to
Yeah, me too - failed it a couple of months ago. I turn out to be very
solid on the theory (didn't surprise me) and not so solid on
remembering the totally disjointed commands and syntax in the
practical bits (surprised me a little bit) and I missed the 82.5%
passmark by ~5%. I'm currently doing a lot of practice in labs -
trouble is I don't have real kit to play with, so it's all a bit
artificial. We'll see.

Cheers - Jaimie
--
Never sleep with anyone crazier than you are.

Richard Kettlewell

unread,
Apr 21, 2013, 5:27:57 AM4/21/13
to
Jaimie Vandenbergh <jai...@sometimes.sessile.org> writes:
> Richard Kettlewell <r...@greenend.org.uk> wrote:
>> Classful addressing has been obsolete for a couple of decades now.
>> You can divide up the RFC1918 address space whichever way you like.
>
> Friggin' Cisco still teach it as the Main Deal for CCNA and such
> courses... pfft. Nonsense.

Really? That’s outrageous.

--
http://www.greenend.org.uk/rjk/

Mike Tomlinson

unread,
Apr 21, 2013, 11:36:26 AM4/21/13
to
En el art�culo <4a97n8d839tglv1je...@4ax.com>, Jaimie
Vandenbergh <jai...@sometimes.sessile.org> escribi�:

>Yeah, me too - failed it a couple of months ago. I turn out to be very
>solid on the theory (didn't surprise me) and not so solid on
>remembering the totally disjointed commands and syntax in the
>practical bits

I got almost all the questions I answered right, just was too slow
answering them and ran out of time, getting 78%.

>I'm currently doing a lot of practice in labs -
>trouble is I don't have real kit to play with, so it's all a bit
>artificial.

I presume you're using the Boson CCNA simulation software? There's no
substitute for working on real kit. Plenty on fleabay cheap enough.

Mike Tomlinson

unread,
Apr 21, 2013, 11:37:35 AM4/21/13
to
En el artículo <8738uk5...@araminta.anjou.terraraq.org.uk>, Richard
Kettlewell <r...@greenend.org.uk> escribió:

>Really? That’s outrageous.

+1. Old-time network engineers still refer to the classes but it has no
place in modern-day teaching of IP.

Jaimie Vandenbergh

unread,
Apr 21, 2013, 12:04:52 PM4/21/13
to
On Sun, 21 Apr 2013 16:36:26 +0100, Mike Tomlinson
<mi...@jasper.org.uk> wrote:

>En el art�culo <4a97n8d839tglv1je...@4ax.com>, Jaimie
>Vandenbergh <jai...@sometimes.sessile.org> escribi�:
>
>>Yeah, me too - failed it a couple of months ago. I turn out to be very
>>solid on the theory (didn't surprise me) and not so solid on
>>remembering the totally disjointed commands and syntax in the
>>practical bits
>
>I got almost all the questions I answered right, just was too slow
>answering them and ran out of time, getting 78%.

Gah! So close. Aggravating, isn't it?

Yeah, I ditched a whole lab and half of one, still ran out of time.

>>I'm currently doing a lot of practice in labs -
>>trouble is I don't have real kit to play with, so it's all a bit
>>artificial.
>
>I presume you're using the Boson CCNA simulation software? There's no
>substitute for working on real kit. Plenty on fleabay cheap enough.

Borrowing time on someone else's real kit, even cheaper. But it's
still a lab, not real working kit with interesting traffic and actual
activity to peruse.

Cheers - Jaimie
--
panic("Foooooooood fight!");
-- /usr/src/linux/drivers/scsi/aha1542.c
0 new messages