[homenet] Best way to test Homenet?

[Rich Brown]

Several months ago, I asked about the best way of getting started with Homenet. 
At the time, the recommendation was that OpenWrt 15.05.1 with its own hnet-full 
package was as good a way as any to test/use Homenet in a live environment. 
Lately, I received new information that HEAD fixes many problems in the (now 
18-month old) OpenWrt 15.05.1 package. 

My request:

I'd like to update the wiki at www.homewrt.org to give good instructions for 
people who are newcomers to Homenet. I specifically want to provide guidance 
about versions that are (mostly) stable, so that they're good candidates that 
likely work fine but need additional testing. What advice should the wiki 
provide re: 

- OpenWrt 15.05.1 vs OpenWrt DD/trunk vs LEDE
- which hnet packages to install
- whether it's useful to put Homenet into a home "production" environment (that 
is, used by spouses, kids, etc. who expect the network "just to work")

Many thanks.

Rich
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] upstream dhcp with hnetd

[Rich Brown]

Hi Massimiliano,

I'll happily update the "Installing Homenet..." guide if you could give me a 
few hints about installing a head version of Homenet on OpenWrt 15.05.1. - 
http://www.homewrt.org/installation/hnet-openwrt I will also test the procedure 
before posting, so I know that it worked at least once. :-)

Thanks,

Rich


> On Sep 18, 2016, at 1:20 PM, Massimiliano Stucchi  wrote:
> 
> 
> Hi,
> 
> On 15/09/16 12:45, Tim Coote wrote:
>> 
>> I’m using hnet-full on CC 15.05.1 on Linksys wrt1200ac.
> 
> I would suggest moving to head.  I spent an inordinate amount of time
> trying to debug issues I was having with 15.05.1, and then found out
> that upgrading to head made the network more robust.
> 
>> Additionally, this is an ADSL connection so I need a pppoe connection to
>> my external modem, including a username/password. What’s the canonical
>> way to add this extra step with hnetd?  I can add it to a uci interface
>> (even an interface not called WAN) and the connection is made, but I
>> don’t know whether this will interfere with hnet. 
> 
> I have a similar situation, although on a fiber connection that requires
> PPPoE for IPv4.  I solved it like this:
> 
> config interface 'homenet4'
>   option ifname 'eth0.6'
>   option proto 'pppoe'
>   option username 'username'
>   option password 'password'
> 
> config interface 'homenet4ext'
>   option ifname 'pppoe-homenet4'
>   option proto 'hnet'
>   option mode 'external'
>   option _orig_ifname 'pppoe-homenet4'
> 
> Basically, you "piggyback" on the interface created by PPPoE to use it
> for hnet.
> 
>> I’d rather not go through the pain of building from source and adding
>> debug statements, but, if necessary, I will.
> 
> Again, I suggest moving to head.  You'll find more mature code.
> 
> Ciao!
> 
> -- 
> 
> Massimiliano Stucchi
> MS16801-RIPE
> 
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] upstream dhcp with hnetd

[Massimiliano Stucchi]

Hi,

On 15/09/16 12:45, Tim Coote wrote:
> 
> I’m using hnet-full on CC 15.05.1 on Linksys wrt1200ac.

I would suggest moving to head.  I spent an inordinate amount of time
trying to debug issues I was having with 15.05.1, and then found out
that upgrading to head made the network more robust.

> Additionally, this is an ADSL connection so I need a pppoe connection to
> my external modem, including a username/password. What’s the canonical
> way to add this extra step with hnetd?  I can add it to a uci interface
> (even an interface not called WAN) and the connection is made, but I
> don’t know whether this will interfere with hnet. 

I have a similar situation, although on a fiber connection that requires
PPPoE for IPv4.  I solved it like this:

config interface 'homenet4'
option ifname 'eth0.6'
option proto 'pppoe'
option username 'username'
option password 'password'

config interface 'homenet4ext'
option ifname 'pppoe-homenet4'
option proto 'hnet'
option mode 'external'
option _orig_ifname 'pppoe-homenet4'

Basically, you "piggyback" on the interface created by PPPoE to use it
for hnet.

> I’d rather not go through the pain of building from source and adding
> debug statements, but, if necessary, I will.

Again, I suggest moving to head.  You'll find more mature code.

Ciao!

-- 

Massimiliano Stucchi
MS16801-RIPE



signature.asc
Description: OpenPGP digital signature
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet