-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Init location "FBLipke" and device "nsm2_xw" #934
base: main
Are you sure you want to change the base?
Conversation
fblipke-ap01: 130 | ||
- vid: 42 | ||
role: mgmt | ||
prefix: 10.248.3.160/28 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this IP range is already used by kiezladen154 and therefore a conflict
low_flash: true | ||
|
||
ipv6_prefix: "2001:bf7:850:1500::/56" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please state all the ips of your location here so everybody can very. usually we register one large ipv4 range and one ipv6 prefix and split the ipv4 range for the different networks. You can have a look at location w38b for a good example
- vid: 50 | ||
role: uplink | ||
|
||
- role: tunnel | ||
ifname: ts_wg0 | ||
mtu: 1280 | ||
prefix: 10.248.3.177/32 | ||
wireguard_port: 51820 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while one uplink is fine, you might want to have a second uplink for more redundancy and faster routing failovers e.g. during a firmware update of the uplink gateway.
location__wireless_profiles__to_merge: | ||
- name: foobar | ||
devices: | ||
- radio: 11g_standard | ||
legacy_rates: false | ||
country: DE | ||
ifaces: | ||
- mode: ap | ||
ssid: berlin.freifunk.net | ||
encryption: none | ||
network: dhcp | ||
radio: [11a_standard, 11g_standard] | ||
ifname_hint: ff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please remove this. Your configuration stated in the hosts section that it uses the default profile and therefore you don't need it. You only need to override the wireless_profiles if you want the APs to announce networks that are not the default. Have a look at w38b for a complex example.
no_corerouter_dns_record: true | ||
assignments: | ||
fblipke-core: 129 | ||
fblipke-ap01: 130 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need this line. The ap will be reachable via the ip of the management network (vid 42).
- hostname: fblipke-ap01 | ||
role: ap | ||
model: "ubnt_nanostation_m2_xw" | ||
wireless_profile: freifunk_default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the default for APs and therefore can be removed from the configuration.
name: 11s_n_2g | ||
prefix: 10.248.2.200/32 | ||
ipv6_subprefix: -20 | ||
mesh_ap: fblipke-core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this specifies the device where the mesh interface is. in your case this should be fblipke-ap01
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pleake make adding the model file a new commit with commit message model: add nanostation_m2_xw
or similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to point it out, as this is a private setup: In the current version this will install all the community ssh keys present in /group_vars/all/ssh-keys.yml
onto your router. If it is properly isolated from your network and this is fine you can keep it that way and add your own SSH key by merging it in (
bbb-configs/locations/kotti.yml
Lines 90 to 92 in cad7136
location__ssh_keys__to_merge: | |
- comment: Kian | |
key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC/tkIsr6x/qTnNcn5mJP+ucu4dreueQDNvr51AcMXvVMXy9ZqyUFC3WyAJAALfGv08lA/hWKvaBLeqI1JWrWutaGl3m8oI8jjDeA8WnBNYOpGluL0b1EkIAnB09pPehvIowP6PqgPO/m1Iv+FfOrxe3QoCGI4zvlwrC+Pu2SO4PAItr6ksqhRl5UaXrE3vHITxMCDPSa0xGxD1uq7PEg+OaMEVWtOJrcbIlQFlZSLodtrt6tnEDZJoyxfsjSbbjJD73mBnR4VGIsT1+RUmr4NemFtLJ3wDPUYZmJS5nprxnlAmFX8mDdoGeVw5OrSbCAltAXhXdzTb3uOo/kIxoMuiJajep4ZmB73Jsa8YW9CnQhZ4aHBLkhn80QI3OLrm/EWQevzmQejV4ztPCLkZCDklQJxhglzwr+Cj7JeUfQMdI1baMIQG7Z5oOHZqsVnc+HKoYnnZReUDtQH3oQETECoSIL5uEHujaqeMdVqx8NqiZX+093YLftNzyV+GA5TTxRU= [email protected] |
bbb-configs/locations/w38b.yml
Lines 249 to 252 in cad7136
# SSH Keys | |
ssh_keys: | |
- comment: Noki | |
key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPjIgJKflHEYOIdskwalr83PflhPmFkrAebP2bUkOE11 Noki |
ipv6_subprefix: 0 | ||
inbound_filtering: true | ||
enforce_client_isolation: true | ||
no_corerouter_dns_record: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the main dhcp_network for the router, therefore this setting should not be added.
@@ -0,0 +1,29 @@ | |||
--- | |||
override_target: "ubnt_nanostation-m" | |||
target: ath79/tiny |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be ath79/generic (https://firmware-selector.openwrt.org/?version=23.05.4&target=ath79%2Fgeneric&id=ubnt_nanostation-m-xw)
This Pull Requests adds the Location and device "ubnt nsm2_xw"