3rd party router and voice

[skyster55]

Hi,

Im currently using a SR203 and have the sky voip package.  I'm looking at replacing this with either the tplink modem or a vigor 130 and setting up a pfSense box for routing needs, adding a AP aswell.

I'm aware that the Sky hub is needed for voice, is it possible to connect a downstream pfSense LAN port to a LAN port on the SR203 , with everything turned off, nothing else connected to the LAN ports but leave the phone plugged in? 

Thanks,

[jamesn123]

@skyster55 
For use of Sky voice the hub must be the first connected router (directly to the line). You can certainly connect your TP-Link/Vigor router & pfSense box downstream of the Sky hub but you'll still run into double NAT issues if you run any applications on your network which would suffer from that. 

[skyster55]

Ah OK,  there is so much contradicting info. re double nat and DMZ +port forwarding, and DMZ + port forwarding on BOTH sky and 3rd party router.

I can avoid most issues as ive a reverse proxy setup on my unraid box, but I do have certain ports for online games, would port f orwarding on both routers fix any issues that double NAT causes?

[mae-3]

@skyster55 

If you set pfSense as a transparent bridge then the Sky router I believe will work with Sky's VoIP solution.

[skyster55]

@mae-3   If its connected via LAN, downstream from the pfSense box you mean?  Im installing it on VM at the moment to have a bit of play around, as im waiting for the hardware to turn up,  so i could try it 

[mae-3]

@skyster55 

Yes, the Sky router would be connected to 1 of the LAN ports as a transparent bridge where other LAN ports could be routed.

[mae-3]

@skyster55 

And take a look at OPNsense which is a better and easier firewall IMHO to administrate.

[skyster55]

@mae-3 thanks, I've been looking at both and trying to decide!

I've got a tp link td-w9970 today and am just trying to set that up, initially just with the sky router. 

I expected it to have a modem bridge mode, but it says dsl kodem router mode, along with a 3g/4g mode and the 'normal' wireless router mode.   Is this just what they call it? Should I use 'Dsl modem router mode' it threw me abit as if still says router, and appears to let you have WiFi , dhcp etc turned on aswell. I expected those options to be greyed out or something?

[mae-3]

@skyster55 

We should be able to bridge the TP-Link TD-W9970 with the right revision as that DSL router has a few revisions. A document on the TP-Link site explains the process of putting it into bridge mode.

[skyster55]

Ah got it, do i need to set the VLAN to 101?

I assume i then delete the existing Dynamic IP connection?

With this setup I also assume the dhcp opt 61 identifier details are then required in the router (opnsense/pfsense)?

Thanks in advance.

[mae-3 · Accepted solution]

@skyster55 

One needs to set VLAN to 101 for the BT Openreach network. The pfSense or OPNsense firewall does the DHCP Option 61 with the TP-Link in the VDSL2 ethernet bridge.

[skyster55]

Just trying to do innital pfsense config, as i already had that downloaded and on a my memory stick! .

Im trying to enter the DHCP cllient identifier in the DHCP client configuration, DHCP hostname section in the, what i thought was correct standard format :   abc123@skydsl|abc123   But get a invlaid DHCP hostname error,   should it have a different seperator? ive manually entered it using the pipe, shifted backslash and also tried cutting and pasting from another thread on these boards but am not getting anyway?  Any suggestions on what im doing wrong?

Thanks,

[jamesn123]

@skyster55 

I don't have experience with pfsense but that is the correct format for any router I have seen so far when connecting to a Sky line. 

[mae-3]

@skyster55 

The static DHCP hostname is not the same as the DHCP Option 61 client identifier.

[skyster55]

@mae-3 

The pfsense config the Hostname says the field is 'sent as the DHCP client identifier and hostname when requesting a DHCP lease. Some ISPs may require this (for client identification).'     

DHCP option 61 *is* the client identifier unless i'm mistaken?