***: dmr104 has joined #arpnetworks
dmr104 has quit IRC (Ping timeout: 240 seconds)
dmr104 has joined #arpnetworks
dmr104 has quit IRC (Ping timeout: 240 seconds)
todd has quit IRC (Ping timeout: 240 seconds)
todd has joined #arpnetworks
todd has quit IRC (Ping timeout: 240 seconds)
todd has joined #arpnetworks
todd has quit IRC (Remote host closed the connection)
todd has joined #arpnetworks
dmr104 has joined #arpnetworks dmr104: i am still trying to create a bridge on my machine which will allow the passage of dhcp broadcast and other messages from one interface to another. If i enable the hostapd service on wlan4 will this allow multiple Machine access codes to wlan4? so far the results have have gotten have be via the use of iw. See https://termbin.com/lixu
It seems to me that hostapd waits for a client to join to its service. this is not what i want. i require the client dhcp to be running on wlan4 accessing the router elsewhere, and a bridge between wlan4 and enp4s0 florz: that's why you need the WDS link dmr104: but i don't have wds capabilities on my home router. is there any work-around to this?
can i run dhcpd on wlan4 and still have a client from wlan4 with a lease to the router?
i am using iwd to connect but it connects briefly, then disconnects, then reconnects in station mode. i suppose i have not tried networkmanager with hostapd running yet. florz: my guess would be that your home router thingy doesn't support four-address frames, in which case there is no way to bridge anything to it on the client side
your next best option probably would be proxy ARP with some sort of DHCP proxy setup or something, could be tricky ... well, or (double) NAT, of course
or you replace your home router's AP with an AP that does support WDS
possibly you can even just install some OpenWRT or something on it that possibly supports WDS on the existing hardware? dmr104: thanks. i think i will try the proxy ARP with DHCP setup. to ask a question which shows my ignorance, why won't a proxy ARP automatically pass the DCHP packets, which i presume are TCP? florz: no, it won't, and no, they aren't
also, I guess I would encourage you to read some book or something on the basics, that should save you a lot of headaches dmr104: I did read Richard Stevens many years ago. i haven't read RFC or anything since 2017 so i have forgotten it all. so either ICMP of UDP, but i could google or look at the wiki page. florz: well, just re-read it, then? ;-) dmr104: I don't have it to hand, and the book is somewhat dated florz: well, it doesn't cover IPv6, yeah, but IPv4/ARP/UDP/TCP haven't fundamentally changed in quite a while ... ***: dmr104 has quit IRC (Quit: leaving)