Welcome, Guest. Please login or register.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Qinn

Pages: [1]
1
General Questions / Re: Bug Status-Interfaces-WAN interface
« on: July 26, 2016, 08:26:40 AM »
Hi Lee, the generic-pc-1.10.2b102 and it's with DSL (PPPoE)

2
General Questions / Bug Status-Interfaces-WAN interface
« on: July 04, 2016, 04:27:58 PM »
Hi Andy thanks for all the good work!

After you use the Disconnect on the WAN interface on the Status-Interfaces page, there is no (Re)connect and you'll have to go Interfaces-WAN and save the settings on the WAN interface to get it up again.

3
Firewall/NAT / Re: Manually add/change firewall rulles
« on: July 04, 2016, 02:56:00 PM »
Stupid me, in pfsense when you go to hybrid mode the default NAT rule for all interfaces is maintained in t1n1wall I had to create one for every interface

so I had to add for LAN

Interface= WAN
Source= 192.168.1.0/24
Destination=*
Target=*

It would be nice if you could select the source like the type in the firewall and not have to type ip's  ;)

4
Firewall/NAT / Re: Manually add/change firewall rulles
« on: July 04, 2016, 12:05:40 PM »
I've experimented with pfsense and got it right. In pfsense there is the option "Hybrid Outbound NAT rule generation (Automatic Outbound NAT + rules below)" and I added the Rule as below:

Interface= WLAN
protocol= any
Source= any
Destination= network
Destination network for outbound NAT mapping= 192.168.5.71/32
Translation address= Interface address
Destination port= *

I tried the outbound settings in T1n1wall, but can't seem to get it right. Do I miss something?


5
Firewall/NAT / Re: Manually add/change firewall rulles
« on: May 06, 2016, 02:27:07 PM »
Ofcourse, I want to access an ipcam (192.168.5.71) from a machine (192.168.1.100) that resides in another private subnet. In t1n1wall both subnets are assigned interfaces (NIC's) with 192.168.1.1/24 and 192.168.5.1/24 (so no VLAN's). The DHCP server on both interfaces only respond to reserved clients listed.

As said in my previous post by default the ipcam seems to block all access from any different subnet and as the webserver from the ipcam has no option to edit the firewall settings/rules and there is no Telnet/SSH port to access the OS of the ipcam, only IP masquerade (my 2 cents ;) ) came into mind as a possible solution. Hope this helps, thanks for your time.


6
Firewall/NAT / Manually add/change firewall rulles
« on: March 29, 2016, 01:45:07 PM »
Hi there, is it possible to manually add a firewall rule?

Why? Well I my case I need to ping a machine that's on a different (private)subnet. Easy you could say, but this machine blocks requests when they aren't coming from the same subnet. Alas there is no telnet\SSH access, so no way for me to change it's set of firewall rules.

So, I want to try address spoofing with something like "iptables -t nat -A POSTROUTING -p icmp -j SNAT --to-source ipaddress"

and test it with a ping, but then I need to manually add/insert a rule, any help is appreciated.

7
Installation / Re: Possible DHCP error
« on: March 04, 2016, 09:04:43 AM »
OffTopic: I've noticed that with the 1.10 versions, in contrast to 1.8 versions, the IP's from the reservations are now in the Diagnostics: DHCP leases, which is rather nice.

8
Installation / Re: Possible DHCP error
« on: March 04, 2016, 08:34:12 AM »
Tested generic-pc-1.10.2b99 (i386) it works like a charm dhcp only responds to the reserved clients, sorry for my useless remark  :-[ about the #dhcp-ignore=tag:!known". So now I will move over to the 1.10 builds.

9
Installation / Re: Possible DHCP error
« on: March 04, 2016, 06:34:24 AM »
Just a wild guess looking at line #298 http://fossies.org/linux/dnsmasq/dnsmasq.conf.example, could a "#dhcp-ignore=tag:!known" maybe be an idea?

10
Installation / Re: Possible DHCP error
« on: March 03, 2016, 02:34:13 PM »
Thanks for the quick reply for now I will stay on generic-pc-1.8.2b78, but if you'll come up with something I will gladly test it.

11
Installation / Re: Possible DHCP error
« on: March 03, 2016, 01:31:20 PM »
In  generic-pc-1.10.2b97(i386) I added the checkmark at Deny unknown clients and instantly the DHCP error occured in the log. I then uploaded firmware  generic-pc-1.10.2b98(i386) and then the error was gone and ip addresses were assigned on mac address, so all looked well. I had a quick look at the status.php and everything looked fine "dhcp-range=set:opt2,192.168.5.10,192.168.5.20,static,255.255.255.0", the static is in there and the subnet mask is added. B.t.w. nice that you added dnsmasq to the statusline line instead of only dhcpd.conf.

I further tested generic-pc-1.10.2b98(i386)  by removing the mac address of a machine from the list of reservations. After I renewed the IP of this machine it got an IP address in the available range. So preliminary conclusion must be that the DHCP error is gone, but Deny unknown clients is not working. yet. If you want more testing let me know!

12
Installation / Re: Possible DHCP error
« on: March 02, 2016, 07:04:16 PM »
Looks promising,thanks for the hard work Andy!

13
Installation / Re: Possible DHCP error
« on: March 02, 2016, 04:23:45 PM »
Thanks for the quick reply!
Not to be bugging you ;) its just a minor cosmetic bug, but in the status.php there is a "cat / var/ etc / dhcpd.conf: No such file or directory" (of course without the spaces ;) )
This just confused me a bit, as at first I overlooked the error log which does mention the right path / var / etc / dnsmasq / dhcpd.conf (see my first post)

14
Installation / Possible DHCP error
« on: March 02, 2016, 09:14:04 AM »
Hi Andy thanks for the great work creating a fork!

I just upgraded from generic-pc-1.8.2b78 to generic-pc-1.10.2b97(i386) and noticed that dhcp was failing. The log gave the following error:

dnsmasq[86]: Failed to start up
dnsmasq[86]: bad dhcp-range at line 11 of -var-etc-dnsmasq-dhcpd.conf

(offtopic: strange but when I use a slash forward instead of an - this post here in the forum won't save and I get an error...)

I downloaded the dhcpd.conf using the exec.php and had a look at line 11

dhcp-range=set:opt2,192.168.5.10,192.168.5.20,static

The word static seemed out of place. When I removed the checkmark at Deny unknown clients (Opt2 Services: DHCP server) in the GUI, the error (after a reboot) was gone and DHCP worked fine.

Then I downloaded the dhcpd.conf again and the word static was gone, so my preliminary conclusion is that they might be related.

I hope it's not a bug and it's just my configuration, if not I hope this post helps  ;)

Best Qinn



Pages: [1]