Messages

1

23.7 Legacy Series / Re: [Solved] Problem with Virtual IPs and PPPoE

« on: January 11, 2024, 01:15:41 am »

Well, well – same boat, same errors. Only I'm still on 23.1.11_2

Situation: PPPoE with fixed IPv4 and an additional /29 Subnet routed via it.
The Virtual IPs have been setup with the correct Gateway from the beginning on.

Code: [Select]

/usr/local/opnsense/scripts/interfaces/reconfigure_vips.php: The command '/sbin/ifconfig 'pppoe0' inet 'x.x.x.x'/'32' alias ' returned exit code '1', the output was 'ifconfig: ioctl (SIOCAIFADDR): Destination address required'

Everything i wanted worked (alas everything of that has a NAT rule associated to it), except for pings, but why?

I can ping every WAN interface with a simple rule allowing the ICMP protocol, no NAT needed – if the Virtual IPs are associated to that Interface, there shouldn't be a NAT rule necessary, no? Else what traffic could be a also a victim of not getting recognized correctly?

2

15.7 Legacy Series / Re: [CALL FOR TESTING] 15.7.11 complete firewall section rework

« on: September 02, 2015, 05:43:21 pm »

hi all!

just wanted to gain a quick look at that firewall-section overhaul, but... somethings missing here.

took a vm, installed latest 15.7.11, configured. checked working state (ping to wan, etc. all good).
then issued in shell the provided command "pkg install -y opnsense-devel" – that downloaded stuff and returned shell prompt. exited and did a reboot.

logged in, went to the firewall section and have seen nothing, nothing new to my eye. what went wrong?

checked system information and saw this:
OPNsense 15.7_824-amd64   
FreeBSD 10.1-RELEASE-p18   
OpenSSL 1.0.2d 9 Jul 2015

ok, what to do?

cheers,
Blacky

3

15.7 Legacy Series / Re: Binding an internal machines traffic to a specific external IP

« on: July 29, 2015, 01:03:40 pm »

alright, i could get it working 

in my scenario needed a virtual ip, else the first useable ip of the 8 address block would have been used. still not sure, if i've it optimized to best values, cause it needed several tries and then suddenly it work.

thx. for the tip.

4

15.7 Legacy Series / Re: Binding an internal machines traffic to a specific external IP

« on: July 28, 2015, 11:38:11 am »

ok, i'll check out tonight. but probably i need then the virtual ip, to be able to bind the server traffic to that exact ip.
on the other hand, OPNsense knows all about these 8 IPs anyway, because of the subnet mask. well, we'll see, i'll try first without, then with virtual ip.

5

15.7 Legacy Series / Re: Binding an internal machines traffic to a specific external IP

« on: July 28, 2015, 10:06:34 am »

one question, did you have to setup a virtual ip (for the one IP used by the server facing to the internet) for it to work?

thanks alot chrisch1974.

ps: sorry for having changed the wording of my initial post. i thought it might get clearer.

6

15.7 Legacy Series / [SOLVED] Binding an internal machines traffic to a specific external IP

« on: July 27, 2015, 06:06:43 pm »

Hello everbody!

My name is Oliver and i'm new here and new to the OPNsense platform.

I used alot of different routers over the years, but had settled for one of the bigger players. They use all closed software on their hardware platform, but i've to admit, these was extremely optimized/responsive.

I want to change! And maybe you could help.

My setup uses the latest updates (15.7.4) on APU1D4 board (AMD, 64 bit).
All basic stuff does work so far. Establishing an internet connection, using NAT rules, etc. But i've encountered one problem with my Multi-WAN Setup. This is my setup right now:
LAN (re0): 192.168.0.x (IP v4, DHCP is provided by Server)
WAN1 (re1): ADSL / PPPoE (IP v4, DHCP from Provider) = default gateway
WAN2 (re2): SDSL / Static (IP v4, 8 addresses IP block)

Several different machines on the LAN all use the WAN1 (default) interface for internet connection. One machine is a server for a very small hosting environment. This server should use the WAN2 interface for it's traffic.

Traffic originating from the Internet and targeting the server (via one dedicated IP out of the pool) works fine via NAT rule:
Internet -> SDSL/IP -> OPNsense (via WAN2) -> NAT -> Server (LAN) = OK

But vice versa doesn't work and looks right now like this:
Server (LAN) -> NAT -> OPNsense (via WAN1) -> Internet = WRONG

I tried alot of possible configurations, but couldn't get it to work properly. Found several how-to's with hints like using a Virtual IP and also setting up outbound NAT rule generation in specific ways, but it didn't work out. I'm sure, OPNsense can do that, maybe someone can point me in the right direction.


Anybody did a setup like this? And likes to share how it needs to be set up?

Thanks alot.

7

15.7 Legacy Series / Re: DNS server list (192.168.1.1 comes from nowhere?)

« on: July 27, 2015, 05:15:29 pm »

well, WAN uses PPPoE and has to be set to DHCP 
just can't remember if i setup the WAN first and then changed the LAN subnet, or not.

delete the entry out of /etc/resolv.conf but it reverts back to it.

but it seems to me, that (latest) after a change in interfaces OPNsense should parse it's dns-entries and update/correct it's list of dns-servers.

8

15.7 Legacy Series / Re: DNS server list (192.168.1.1 comes from nowhere?)

« on: July 27, 2015, 12:06:54 pm »

hey there.

have the exact same situation. i guess it came, when i changed the ip-subnet from default (after fresh installation) 192.168.1.x to 192.168.0.x

not quite sure, if i had dual wan setup already then.