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.


Topics - huub

Pages: [1]
1
Installation / SOLVED DNS/DHCP problems
« on: January 17, 2016, 12:57:15 PM »
I think I ran into some DHCP problems.

My router looks like:
LAN vr0 192.168.10.1
WAN vlan on vr2 DHCP
OPT1 vlan on vr1 192.168.20.1 (DWZ)
OPT2 vlan on vr1 192.168.30.1

The DHCP server is active on LAN and OPT2.
On the LAN most pc's run with a fixed IP-address.
In the DMZ I have a DNS.
On OPT2 however it seems the pc's does cannot find the DNS, I suspect a wrong route (gw 192.168.10.1 instead of 192.168.30.1).

Do you have any suggestions how I can check if the router supplied is correct?
For my phone I have a hard time using fixed IP-settings.

I would rather check this in the router since it saves me the trouble of searching through different interfaces for each device.

PS the dirty workaround is using NAT on the Wifi router at the OPT2 network. Currently it works, but 2x NAT is not optimal. However it proves the problem is in the DHCP data.

2
Installation / SOLVED Problems with embedded installation
« on: December 07, 2015, 07:05:32 PM »
I used m0n0wall for years and earlier this year switched to t1n1wall.
What I am missing is an installation manual.

I used the m0n0wall recipe, but that got me only so far.
The recipe I refer to:
Quote
Installation on an embedded PC requires the following steps:

    download the raw CF image (generic-pc-serial)
    write the image to a CF card (>= 32 MB), either with dd under FreeBSD/Linux or under Windows with physdiskwrite
        FreeBSD:
        gzcat generic-pc-serial-xxx.img | dd of=/dev/rad[n] bs=16k
        where n = the ad device number of your CF card (check dmesg)
        (ignore the warning about trailing garbage - it's because of the digital signature)
        Linux:
        gunzip -c generic-pc-serial-xxx.img | dd of=/dev/hdX bs=16k
        where X = the IDE device name of your CF card (check with hdparm -i /dev/hdX) - some adapters, particularly USB, may show up under SCSI emulation as /dev/sdX
        (ignore the warning about trailing garbage - it's because of the digital signature)
        Mac OS X:
        gzcat generic-pc-serial-xxx.img | sudo dd of=/dev/rdisk[n] bs=64k
        where n = the disk device number of your CF card (check Disk Utility)
        (ignore the warning about trailing garbage - it's because of the digital signature)
        Windows:
        physdiskwrite generic-pc-serial-xxx.img
    plug the CF card into the board
    plug the box into the network (LAN/WAN/...)
    power it up
    make sure that your console speed matches the setting in the BIOS; m0n0wall will use the same speed as the BIOS
    assign functions (LAN/WAN/OPT) to your interfaces
    change the LAN IP address over the serial console, or use the default (192.168.1.1; m0n0wall acts as a DHCP server by default)
    access the webGUI (user: 'admin', default password: 'mono')
    make the necessary changes to the default configuration
With the 1.8 version this mostly works, until I try to change the webgui to HTTPS with a diffferent port number. Then I get locked out.
This means that a restore of my old backup does not work. It's a nagging problem but I can work around it.

I ran into problems with the VPN as well, elsewhere on this forum I found that that problem could be caused by the 1.8.x firmware. By switching to 1.10bX I should be able to get a working VPN. Here the trouble begins.

After a clean install I get a prompt on the serial console for 1.8, but not for 1.10. Is there a fix for that behaviour?
Editing the image is unfortunately not an option since I don't have a native FreeBSD system. Therefore I can't change the configuration on the image.
I use an old PC Engines ALIX system (embedded pc, with a serial console for installation).

Pages: [1]