No subnet declaration; Can't open /var/lib/dhcp/dhcpd.leases for append
A
publicface at bak.rr.com
Sun Jan 28 00:52:55 UTC 2018
On 01/27/2018 04:22 PM, Bill Shirley wrote:
> I don't know if it is affecting anything but you still have the bridge
> defined
> in /etc/network/interfaces. Also, you still have wlp2s0 on
> 10.1.1.0/24. Do
> you want to define the wireless?
Yes. I just finished responding to your prior email. I need to run out
for a few minutes before it gets dark. Back in 30.
>
> So 'blue' is to use 'yellow' to get to the internet. Do you have
> iptables on
> 'yellow' set up to masquerade for 10.1.1.0/24
This is what I have at the moment so far. I see an error with FOUR.
Back in 30.
-A PREROUTING -i enp6s0 -p tcp -m multiport --dports 80,443 -j DNAT
--to-destination 10.1.1.1
-A FORWARD -i enp6s0 -o wlp2s0 -m conntrack --ctstate
RELATED,ESTABLISHED -m comment --comment THREE -j ACCEPT
-A FORWARD -d 10.1.1.0/32 -i enp4s5 -o enp6s0 -m comment --comment FOUR
-j ACCEPT
-A FORWARD ! -d 10.1.1.0/32 -o enp6s0 -m comment --comment SEVEN -j ACCEPT
-A FORWARD -d 10.1.1.0/32 -o br0 -m conntrack --ctstate
RELATED,ESTABLISHED -m comment --comment EIGHT -j ACCEPT
>
> Bill
>
> On 1/27/2018 7:10 PM, A wrote:
>>
>> I meant to include the current /etc/network/interfaces. Below.
>> However, in the meantime I'm getting different results. Perhaps due
>> to the fact that I changed "static" to "manuel". I also *deleted*
>> the bridge. Now, both machines can ping each other on the wired
>> interface, and yellow can still ping the 'Net. Blue cannot ping the
>> Internet.
>>
>> It's unclear if the bridge-utils is truly out of the picture, despite
>> the tools reporting so. I suspect this may still be an issue that
>> will come back later when I retry.
>>
>> PING blue (10.1.1.14) 56(84) bytes of data.
>> 64 bytes from blue (10.1.1.14): icmp_seq=1 ttl=64 time=0.353 ms
>>
>> ping google.com
>> PING google.com (172.217.11.78) 56(84) bytes of data.
>> 64 bytes from lax17s34-in-f14.1e100.net (172.217.11.78): icmp_seq=1
>> ttl=56 time=23.4 ms
>>
>> # ping yellow
>> PING yellow (127.0.1.1) 56(84) bytes of data.
>> 64 bytes from yellow (127.0.1.1): icmp_seq=1 ttl=64 time=0.088 ms
>> ^C
>> --- yellow ping statistics ---
>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>> rtt min/avg/max/mdev = 0.088/0.088/0.088/0.000 ms
>>
>> # ping router
>> PING yellow (10.1.1.1) 56(84) bytes of data.
>> 64 bytes from yellow (10.1.1.1): icmp_seq=1 ttl=64 time=0.077 ms
>> ^C
>> --- yellow ping statistics ---
>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>> rtt min/avg/max/mdev = 0.077/0.077/0.077/0.000 ms
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
>>
>> /etc/network/interfaces:
>>
>>
>> auto lo
>> iface lo inet loopback
>> dns-nameservers 10.1.1.1 8.8.8.8 8.8.4.4 50.23.197.95
>> dns-search FQDN
>>
>> auto enp6s0
>>
>> iface enp6s0 inet dhcp
>> dns-nameservers 10.1.1.1 8.8.8.8 8.8.4.4 50.23.197.95
>> dns-search FQDN
>>
>>
>> auto enp4s5
>> allow-hotplug enp4s5
>> iface enp4s5 inet manuel
>> gateway 10.1.1.1
>> network 10.1.1.0
>> netmask 255.255.255.0
>> broadcast 10.1.1.255
>>
>> # Before we can change the address we have to bring the face down
>> pre-up ip link set enp4s5 down
>>
>> # I don't know if I can use two ups. I don't know the right way to
>> do this.
>> up ip address 0.0.0.0 dev enp4s5
>> up ip link set enp4s5 up
>> down ip link set enp4s5 down
>>
>>
>> allow-hotplug wlp2s0
>> iface wlp2s0 inet manuel
>> gateway 10.1.1.1
>> network 10.1.1.0
>> netmask 255.255.255.0
>> broadcast 10.1.1.255
>>
>> # I don't know if I can use two pre-ups. I don't know the right way
>> to do this.
>> pre-up ip link set wlp2s0 down
>> pre-up ip address 0.0.0.0 dev wlp2s0
>> up ip link set wlp2s0 up
>> down ip link set wlp2s0 down
>>
>> wireless-mode master
>> wireless-essid XXXXXXXXXXXXXX
>> wireless-channel 1
>> wpa-ssid XXXXXXXXXXXXXX
>> wpa-psk
>> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>> gateway 10.1.1.1
>>
>>
>>
>> auto br0
>> iface br0 inet static
>> address 10.1.1.1
>> network 10.1.1.0
>> netmask 255.255.255.0
>> broadcast 10.1.1.255
>> bridge-ports enp4s5 wlp2s0
>>
>>
>>
>>
>> On 01/27/2018 03:20 PM, A wrote:
>>>
>>>
>>>
>>> On 01/27/2018 01:28 PM, Simon Hobson wrote:
>>>> A <publicface at bak.rr.com <mailto:publicface at bak.rr.com>> wrote:
>>>>
>>>>> I did originally have two separate subnets with a /28 CIDR, but I
>>>>> was unable to reach the Internet from blue and someone suggested I
>>>>> have one subnet in order to act as a typical home router. So I
>>>>> reconfigured everything and it's now borked worse than it was.
>>>>> Said person disappeared shortly after of course.
>>>>>
>>>>> There is no commercial router. Yellow is the router, gateway,
>>>>> access point, dhcp server, dns server, firewall (iptables) and more.
>>>>
>>>> OK, so this box is your gateway, AP, etc, etc. In that case I
>>>> believe that your setup is fundamentally broken - you have TWO
>>>> SEPARATE networks (one wired, one wireless) running the same subnet.
>>>
>>> Yes, that's how I was told to set it up by a helpful individual. I
>>> was told since it was one subnet, no routing would be needed. The
>>> wireless & wired interfaces would be bridged. Seemed reasonable.
>>> It sounds like you are suggesting exactly the same thing so
>>> "fundamentally broken" seems a bit harsh.
>>>
>>>> Thus devices on the wired network cannot talk to devices on the
>>>> WiFi and vice-verca.
>>>>
>>>> Bear in mind that I've not used WiFi in this manner (I'm used to
>>>> using external APs), so I am unsure of some of the details. If you
>>>> want to run a single unified network then you will need to create a
>>>> bridge, and put the wired and wireless adapters into that bridge -
>>>> and put your address 10.1.1.1/24 onto the bridge. You will then
>>>> have one network, and the bridge software will pass packets between
>>>> them, as well as keeping track of which clients are in which
>>>> network segment.
>>>
>>> I removed the bridge because I was unable to reach the Internet from
>>> yellow (nor blue). And that is how things stand now. Bridge up,
>>> Internet down. Bridge down, Internet up.
>>>
>>>
>>>>
>>>> As far as (almost) all software on your box is concerned, you just
>>>> deal with one interface (the bridge, eg br0). What I am unsure
>>>> about is how dhcpd behaves in this case - hopefully someone who's
>>>> run this setup can comment ? I would hope that it would use the
>>>> bridge interface in the same manner as it would use a "real" one,
>>>> but there can be some subtle differences.
>>>
>>> I had it working with the bridge at one point - each box could ping
>>> the other on both wired & wireless, but blue couldn't reach the
>>> Internet. Lets see if we can put it back.
>>>
>>> .... blue now receives an IP of .14; neither machine can ping the
>>> other, though each can ping its own assigned IP.
>>>
>>> # brctl show
>>> bridge name bridge id STP enabled interfaces
>>> br0 8000.7085c23b1324 no enp4s5
>>> enp6s0
>>>
>>>
>>> $ ip a
>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>> group default qlen 1000
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>> inet 127.0.0.1/8 scope host lo
>>> valid_lft forever preferred_lft forever
>>> inet6 ::1/128 scope host
>>> valid_lft forever preferred_lft forever
>>> 2: enp4s5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>>> pfifo_fast master br0 state UP group default qlen 1000
>>> link/ether c8:3a:35:da:42:72 brd ff:ff:ff:ff:ff:ff
>>> inet 10.1.1.1/24 brd 10.1.1.255 scope global enp4s5
>>> valid_lft forever preferred_lft forever
>>> 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>>> pfifo_fast master br0 state UP group default qlen 1000
>>> link/ether 70:85:c2:3b:13:24 brd ff:ff:ff:ff:ff:ff
>>> inet [xx.xx.xx.xx]/20 brd 255.255.255.255 scope global enp6s0
>>> valid_lft forever preferred_lft forever
>>> inet6 fe80::7285:c2ff:fe3b:1324/64 scope link
>>> valid_lft forever preferred_lft forever
>>> 4: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>>> noqueue state DOWN group default qlen 1000
>>> link/ether f0:7d:68:c1:b4:13 brd ff:ff:ff:ff:ff:ff
>>> inet 10.1.1.10/24 brd 10.1.1.255 scope global wlp2s0
>>> valid_lft forever preferred_lft forever
>>> 5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
>>> state UP group default qlen 1000
>>> link/ether 70:85:c2:3b:13:24 brd ff:ff:ff:ff:ff:ff
>>> inet 10.1.1.1/24 brd 10.1.1.255 scope global br0
>>> valid_lft forever preferred_lft forever
>>> inet6 fe80::7285:c2ff:fe3b:1324/64 scope link
>>> valid_lft forever preferred_lft forever
>>>
>>> # ip route
>>> default via 174.xx.yy.1 dev enp6s0
>>> 10.1.1.0/24 dev enp4s5 proto kernel scope link src 10.1.1.1
>>> 174.xx.yy.0/20 dev enp6s0 proto kernel scope link src 174.xx.bb.zz
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20180127/3cd11031/attachment-0001.html>
More information about the dhcp-users
mailing list