Junos OS

Hello everyone,

root# run show version
Model: firefly-perimeter
JUNOS Software Release [12.1X47-D10.4]

So, we've got this little setup here where we're hosting virtual machines at a hosting company.

This hosting company provides us with failover IP addresses which can be routed like so:

- Assign FO IP to your virtualized host : 1.2.3.4/32

- Assign a default gateway which resides in a different network : 5.6.7.8

- Create a static route to reach the gateway : 5.6.7.8/32 via <interface>

On FreeBSD, this translates to :

ifconfig_vtnet0_name="wan"

ifconfig_wan="inet 1.2.3.4/32 -rxcsum -txcsum -rxcsum6 -txcsum6 -tso -tso6 -vlanhwtso -vlanhwcsum -vlanhwtag up"
static_routes="rlocal rdefault"
route_rlocal="-host 5.6.7.8 -iface wan"
route_rdefault="default 5.6.7.8"

On linux, it's written a bit differently :

auto eth0
iface eth0 inet static
address 1.2.3.4
netmask 255.255.255.255
gateway 5.6.7.8
pointopoint 5.6.7.8

I am trying to mimic this behaviour on Firefly Perimeter like so :

set interfaces ge-0/0/0 unit 0 family inet address 1.2.3.4/32

set routing-options static route 0.0.0.0/0 next-hop 5.6.7.8
set routing-options static route 5.6.7.8/32 next-hop ge-0/0/0.0
set routing-options forwarding-table indirect-next-hop

However when trying to commit I get the following error :

root# commit check
[edit routing-options static route 5.6.7.8/32]
'next-hop ge-0/0/0.0'
RT: bad next-hop ge-0/0/0.0 -- next-hop ge-0/0/0.0 is not point-to-point 

error: configuration check-out failed

The documentation [1] however, clearly states that `By default, all interfaces are assumed to be point-to-point connections.'

Anyone got any idea how I may achieve this ?

[1] http://www.juniper.net/documentation/en_US/junos12.1/topics/usage-guidelines/interfaces-configuring-a-point-to-point-connection.html

Hello,

I haven't got a Firefly Perimeter to try but in regular JUNOS p2p Ethernet subinterface is configured as below:

set interfaces lo0.0 family inet address 198.18.1.1/32
set interfaces ge-0/0/0 unit 0 family inet unnumbered-address lo0.0 
set routing-options static route 0.0.0.0/0 next-hop 198.51.100.1 resolve
set routing-options static route 198.51.100.1/32 qualified-next-hop ge-0/0/0.0

 You don't need "routing-options indirect-next-hop" because it (a) works only for BGP routes received over loopback peerings and (b) does not have anything in common with p2p interfaces.

As for documentation link, please raise a JTAC case to have it clarified.

HTH

Thanks

Alex

Hello Alex and thanks for your response,

Your configuration does indeed bring a welcome measure of progress wherein I can try to ping the gateway and :

a/ not get a "no route to host" error

b/ get ARP resolution

root> show arp
MAC Address Address Name Interface Flags
d2:c2:c9:81:f1:9e 192.168.66.254 192.168.66.254 ge-0/0/1.0 none
00:25:45:f6:94:7f 195.154.237.1 195.154.237.1 ge-0/0/0.0 none
Total entries: 2

I'm still not getting icmp echo replies, I'll have to dig some more on the Host side as well, I suppose.

Solved problem with hosting provider, no additional changes required on the Firefly guest.

Thanks Alex.